* Explains current Extreme Programming practices now that .NET 1.1 has matured; also explains how new features of .NET 2.0 impact Extreme Programming techniques.
* Provides real-world examples of Extreme Programming practice, by examining the complete release of an example project, so developers can learn practical details and principles.
* Shows developers how to use test-first development techniques for web-based applications using the NUnit testing framework within the Visual Studio .NET IDE, plus critical coverage of Nant, Net Mock and CruiseControl.NET.
Release planning has two phases: an exploration phase and a planning game phase. During the exploration phase, analysis is conducted and requirements are gathered in the form of user stories. As each user story is created, developers are asking if the user story is estimatable and testers are asking if the user story is testable. The user stories are also estimated in the exploration phase. If the user story is too big, it is split. If the user story is not estimatable, because the developers dont know how to estimate it, the user story is spiked. During the planning game phase, the customer prioritizes the user stories from 1 to n. The tracker will declare the number of story points that can be completed in the release. The customer will select user stories that do not exceed the number of story points declared by the tracker. If the user stories selected have enough business features to be valuable, then the project continues.A table of contents is not available for this title.
From the reviews:
The purpose of this work is to take experienced software developers and mold them into enthusiastic practitioners of agile-programming in general, and of extreme programming in particular. & this book is recommended reading for developers who may be joining an extreme programming project and for software development projló%