Extreme Programming Installed

Chapter 7
This chapter talks about the importance of releasing functioning products to the customer very often. These builds do not have to be the complete product, however they must have functionality as to allow the user to test certain aspects of the software. This will enable customers test the software in case it is not what they desired; and it allows the developers to tailor the development to meet customer needs.

Chapter 8
In chapter eight the author talks about the steps necessary to make a release. Releases and iterations are composed of three phases: exploration, commitment, and steering. The basics of planning a release consist of writing down the stories, assigning a cost to them, estimating the team velocity, and let the user pick the stories that carry the most business weight for the developers to work on.

Chapter 9
Chapter nine describes the process of iteration planner in which programmers produce tasks out of the user stories selected. The process proceeds as follows:

• The user selects the stories that he or she wants to be implemented for the iteration.
• The programmers brainstorm in order to produce the tasks required to carry out the user story.
• The programmers sign up for certain tasks.

Discussion
Chapters 7-9 describe the process required to carry out a release. It all starts with stressing the importance of releasing early and often, and it ends right before the programmers start carrying out the task necessary to produce a release.