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 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
   8
   9 \chapter{The Sprint}
  10 \label{chap:the-sprint}
  11
  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.
  16
  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.
  24
  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} and finally come up with our definition of done in
  29 chapter \ref{chap:definition-of-done}.
  30
  31 \section{Sprint Duration}
  32 \label{sec:sprint-duration}
  33
  34 \paragraph{}
  35 Linux Core Product Development team will use sprint of 2 weeks with no
  36 exceptions.
  37
  38 \section{Scrum Process}
  39 \label{sec:scrum-process}
  40
  41 \paragraph{}
  42 Figure \ref{fig:scrum-process} shows Scrum's process. Note that development is
  43 carried away as a loop.
  44
  45 \begin{figure}[ht]
  46         \centering
  47         \includegraphics[width=0.8\textwidth]{images/scrum-process.png}
  48         \caption{Scrum Process}
  49         \label{fig:scrum-process}
  50 \end{figure}
  51
  52 \section{Sprint Burndown Charts}
  53 \label{sec:sprint-burndown-charts}
  54
  55 \paragraph{}
  56 Figure \ref{fig:example-burndown-chart} shows an example Sprint Burndown Chart.
  57
  58 \begin{figure}[ht]
  59         \centering
  60         \pgfplotsset{width=12cm}
  61         \pgfplotsset{grid style={dashed,lightgray}}
  62         \begin{tikzpicture}
  63                 \begin{axis}[xlabel=Days,ylabel=Effort (hours),grid=both]
  64                         \addplot coordinates {
  65                                 (1, 60)
  66                                 (2, 51)
  67                                 (3, 47)
  68                                 (4, 40)
  69                                 (5, 35)
  70                                 (6, 22)
  71                                 (7, 13)
  72                                 (8, 8)
  73                                 (9, 3)
  74                                 (10, 0)
  75                         };
  76                 \end{axis}
  77         \end{tikzpicture}
  78         \caption{Example Sprint Burndown Chart}
  79         \label{fig:example-burndown-chart}
  80 \end{figure}