tamm: initial commit
[ti-agile-manual/ti-agile-manual.git] / introduction.tex
1 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2 %%                                                                       %%
3 %% Copyright (C) 2013 Texas Instruments Incorporated - http://www.ti.com %%
4 %%                                                                       %%
5 %% Author: Felipe Balbi <balbi@ti.com>                                   %%
6 %%                                                                       %%
7 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
9 \chapter{Introduction}
11 \paragraph{}
12 Texas Instrument's \textit{Linux Core Product Development} team has recently
13 decided to implement
14 \href{http://en.wikipedia.org/wiki/Scrum\_(development)}{Scrum} for Linux
15 Kernel development.
17 \paragraph{}
18 It's uncommon for Linux Kernel engineers to implement any Software Development
19 Methodology at all, however the enterprise development environment needs
20 visibility on feature readiness and Agile Methodologies seem to impose the least
21 amount of process overhead to engineers.
23 \paragraph{}
24 This document aims at setting up a few foundations for the team in order to
25 have a general agreement on the deployment of
26 \href{http://en.wikipedia.org/wiki/Scrum\_(development)}{Scrum} to decrease
27 the amount of rework when developing features for customers and the mainline
28 Linux Kernel tree.