tamm: add matt porter as an author
[ti-agile-manual/ti-agile-manual.git] / the-sprint.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{The Sprint}
10 \label{chap:the-sprint}
12 \paragraph{}
13 The \textit{basic unit of development in Scrum}\cite{wikipediascrum} whose
14 duration is pre-defined in advance. All sprints have the same duration and,
15 usually, is defined to last between one week and one month.
17 \paragraph{}
18 In section \ref{sec:sprint-duration} we shall discuss about Sprint Duration and
19 what is Linux Core Product Development's accepted duration. In the following
20 section \ref{sec:scrum-process} we shall expose Scrum's development process and
21 discuss how to handle an iterative development model while development Linux
22 Kernel code. Lastly, on section \ref{sec:sprint-burndown-charts} we will expose
23 the idea of Sprint Burndown Charts; what they are and how to use them.
25 \paragraph{}
26 By the end of this chapter, we should have enough grounds to discuss about how
27 to successfully break backlog entries into bite-sized pieces in chapter
28 \ref{chap:breaking-tasks-up}, how to come up with proper estimations in chapter
29 \ref{chap:estimating} and finally come up with our definition of done in
30 chapter \ref{chap:definition-of-done}.
32 \section{Sprint Duration}
33 \label{sec:sprint-duration}
35 \paragraph{}
36 Linux Core Product Development team will use sprint of 2 weeks with no
37 exceptions.
39 \section{Scrum Process}
40 \label{sec:scrum-process}
42 \paragraph{}
43 Figure \ref{fig:scrum-process} shows Scrum's process. Note that development is
44 carried away as a loop.
46 \begin{figure}[ht]
47         \centering
48         \includegraphics[width=0.8\textwidth]{images/scrum-process.png}
49         \caption{Scrum Process}
50         \label{fig:scrum-process}
51 \end{figure}
53 \section{Sprint Burndown Charts}
54 \label{sec:sprint-burndown-charts}
56 \paragraph{}
57 Figure \ref{fig:example-burndown-chart} shows an example Sprint Burndown Chart.
59 \begin{figure}[ht]
60         \centering
61         \pgfplotsset{width=12cm}
62         \pgfplotsset{grid style={dashed,lightgray}}
63         \begin{tikzpicture}
64                 \begin{axis}[xlabel=Days,ylabel=Effort (hours),grid=both]
65                         \addplot coordinates {
66                                 (1, 60)
67                                 (2, 51)
68                                 (3, 47)
69                                 (4, 40)
70                                 (5, 35)
71                                 (6, 22)
72                                 (7, 13)
73                                 (8, 8)
74                                 (9, 3)
75                                 (10, 0)
76                         };
77                 \end{axis}
78         \end{tikzpicture}
79         \caption{Example Sprint Burndown Chart}
80         \label{fig:example-burndown-chart}
81 \end{figure}