Extreme Programming Installed

Chapter 15. Releasing Changes

Using collective code ownership and comprehensive unit tests, an XP team releases changes rapidly and reliably.

An XP team practices collective code ownership: every class and method belongs to the team, and any team member can improve anything that needs it. Collective code ownership lets the team make faster progress because no one has to wait until someone else gets around to fixing something. The code stays cleaner because programmers aren't forced to work around a deficiency in one object by hacking up another.

One of the most important parts of making collective code ownership work is the process of releasing ...