All the code belongs to all the programmers. This lets the team go at full speed, because when something needs changing, it can be changed without delay. XP teams integrate and build the software system multiple times per day. This keeps all the programmers on the same page, and enables very rapid progress. Perhaps surprisingly, integrating more frequently tends to eliminate integration problems that plague teams who integrate less often.
Tired programmers make more mistakes.
XP teams do not work excessive overtime, keeping themselves fresh, healthy, and effective. An XP project is steered by a dedicated individual who is empowered to determine requirements, set priorities, and answer questions as the programmers have them. For a team to work effectively in pairs, and to share ownership of all the code, all the programmers need to write the code in the same way, with rules that make sure the code communicates clearly. XP Magazine includes various articles discussing aspects of XP, from practical, philosophical, and whimsical viewpoints. If you have a question you would like to have addressed, please write the editor .