tamm: almost complete 'the sprint'
authorFelipe Balbi <balbi@ti.com>
Mon, 8 Apr 2013 11:44:24 +0000 (14:44 +0300)
committerFelipe Balbi <balbi@ti.com>
Mon, 8 Apr 2013 11:55:07 +0000 (14:55 +0300)
Also add a necessary picture.

Signed-off-by: Felipe Balbi <balbi@ti.com>
images/scrum-process.png [new file with mode: 0644]
the-sprint.tex

diff --git a/images/scrum-process.png b/images/scrum-process.png
new file mode 100644 (file)
index 0000000..14e7733
Binary files /dev/null and b/images/scrum-process.png differ
index e60e88eef058ed395998079883ee4afd5d38426c..ff9491fd8f9d6a2f1bbb5f9cd51d75d2b6dfc0a4 100644 (file)
@@ -7,3 +7,74 @@
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 \chapter{The Sprint}
+\label{chap:the-sprint}
+
+\paragraph{}
+The \textit{basic unit of development in Scrum}\cite{wikipediascrum} whose
+duration is pre-defined in advance. All sprints have the same duration and,
+usually, is defined to last between one week and one month.
+
+\paragraph{}
+In section \ref{sec:sprint-duration} we shall discuss about Sprint Duration and
+what is Linux Core Product Development's accepted duration. In the following
+section \ref{sec:scrum-process} we shall expose Scrum's development process and
+discuss how to handle an iterative development model while development Linux
+Kernel code. Lastly, on section \ref{sec:sprint-burndown-charts} we will expose
+the idea of Sprint Burndown Charts; what they are and how to use them.
+
+\paragraph{}
+By the end of this chapter, we should have enough grounds to discuss about how
+to successfully break backlog entries into bite-sized pieces in chapter
+\ref{chap:breaking-tasks-up} and finally come up with our definition of done in
+chapter \ref{chap:definition-of-done}.
+
+\section{Sprint Duration}
+\label{sec:sprint-duration}
+
+\paragraph{}
+Linux Core Product Development team will use sprint of 2 weeks with no
+exceptions.
+
+\section{Scrum Process}
+\label{sec:scrum-process}
+
+\paragraph{}
+Figure \ref{fig:scrum-process} shows Scrum's process. Note that development is
+carried away as a loop.
+
+\begin{figure}[ht]
+       \centering
+       \includegraphics[width=0.8\textwidth]{images/scrum-process.png}
+       \caption{Scrum Process}
+       \label{fig:scrum-process}
+\end{figure}
+
+\section{Sprint Burndown Charts}
+\label{sec:sprint-burndown-charts}
+
+\paragraph{}
+Figure \ref{fig:example-burndown-chart} shows an example Sprint Burndown Chart.
+
+\begin{figure}[ht]
+       \centering
+       \pgfplotsset{width=12cm}
+       \pgfplotsset{grid style={dashed,lightgray}}
+       \begin{tikzpicture}
+               \begin{axis}[xlabel=Days,ylabel=Effort (hours),grid=both]
+                       \addplot coordinates {
+                               (1, 60)
+                               (2, 51)
+                               (3, 47)
+                               (4, 40)
+                               (5, 35)
+                               (6, 22)
+                               (7, 13)
+                               (8, 8)
+                               (9, 3)
+                               (10, 0)
+                       };
+               \end{axis}
+       \end{tikzpicture}
+       \caption{Example Sprint Burndown Chart}
+       \label{fig:example-burndown-chart}
+\end{figure}