One of the key concepts defined in the book is empirical process control This is used as the foundation of the justification for the Scrum process. His claim is that in the "real world" of software development most projects that build or improve a product are breaking new ground and cannot use defined process control, as might be used in truly repetitive projects. Empirical process control relies on recently observed data to affect the project and change its execution. The iterative nature of Scrum, like other agile processes, allows for adjustments to the process ad scope every cycle (30 days) allowing it to adapt to the current situation (based on empirical data). Strict configuration control is maintained in each cycle.

The book presumes very little knowledge of Scrum and agile processes; although the later is beneficial in understanding the bigger picture of agile and how Scrum fits in. The book is applicable to software development. The appendix supplies a variety of background data that might be needed by the novice. It is relatively short and easy to read.

Buy it now!