diff --git a/introduction.tex b/introduction.tex
index 022b71a9ec0560bbe50ce32382283bec1f7755bb..57fdb9756c9ecceb6e9212e7476ec547d3564dce 100644 (file)
--- a/introduction.tex
+++ b/introduction.tex
\chapter{Introduction}
\label{chap:introduction}
-\section{Welcome}
-\label{sec:welcome}
-
\paragraph{}
Welcome to \textit{Linux Core Product Development}'s Agile Methodology Manual.
Here you will find enough information to get acquainted with our development
visibility on feature readiness. The Agile Methodologies seem to impose the
least amount of process overhead to engineers, which gives the team maximum
amount of engineering hours and decreases the amount of time wasted in phone
-calls and meetings.
+calls and meetings. An additional advantage of Scrum is that developers
+are given focused time within each Sprint to accomplish their tasks without
+being re-assigned or re-prioritized. Customer support efforts are prioritized
+as part of the common backlog and not as interrupts. The Sprint concept is
+discussed more in chapter \ref{chap:the-sprint}.
\paragraph{}
This document aims at setting up a few foundations for the team in order to
the amount of rework when developing features for customers and the mainline
Linux Kernel tree.
-\section{Document Organization}
-\label{sec:document-organization}
+\paragraph{}
+This book is organized as follows. In chapter \ref{chap:scrumterminology} we
+will go through a few terms that we want everybody to understand the same way
+we do.
+
+\paragraph{}
+Later in chapter \ref{chap:scope} we will define the scope of this document.
+Why is it needed and who's going to use it.
\paragraph{}
-In chapter \ref{chap:scope} we will define the scope of this document. Why is
-it needed and who's going to use it.
+An in-depth description of Scrum is available on chapter \ref{chap:scrum}. We
+will look at traditional Scrum practices, what Scrum is, the daily scrum, etc.
+Note, however, that Scrum is a management process and it needs a companion
+engineering process such as Continuous Integration, Test-Driven Development,
+and many, many others.
\paragraph{}
-Chapter \ref{chap:roles-in-scrum} will discuss about the three roles within a
+Chapter \ref{chap:roles} will discuss about the three roles within a
Scrum Team. What they are, what are their responsibilities, how they should
communicate with each other.
\paragraph{}
-A thorough discussion about the Sprint will be carried out throughout chapter
+On chapter \ref{chap:meetings} we will take a look at Scrum meetings. How many
+are there, how they should be used, how long do they take. All such questions
+will be answered on that chapter.
+
+\paragraph{}
+A thorough discussion about the Sprint will be carried throughout chapter
\ref{chap:the-sprint}. We will look at sprint duration, process, artifacts and
more.
\paragraph{}
-A discussion about how to break tasks into small pieces will be exposed in
-chapter \ref{chap:breaking-tasks-up}. We will learn tricks which will help us
-understand how to break e.g. \textit{Development of QSPI driver} into smaller,
-bite-sized pieces which can done in the course of one sprint.
+A discussion about how to break tasks into small pieces will be
+exposed in chapter \ref{chap:work-breakdown}. We will learn tricks
+which will help us understand how to break work items
+(eg. \textit{Implement an error management system} into smaller,
+bite-sized pieces that can be done in the course of one sprint.
\paragraph{}
After being able to break tasks into small pieces, we need to come up with
\paragraph{}
We hope our readers have lots of fun while reading this manual and implementing
-it on daily job.
+it in their daily job.