Appendix - The Original 12 XP Practices (Reference)

For reference, Kent Beck's original twelve Extreme Programming practices, unmodified:

1. Planning Game - customer and developers jointly determine scope of releases and iterations
2. Small Releases - release working software frequently, in small increments
3. Metaphor - a shared story/conceptual model guiding system design and naming
4. Simple Design - build the simplest thing that could possibly work; avoid speculative complexity
5. Testing - write tests first (unit tests especially); code isn't done until it passes them
6. Refactoring - continuously restructure code without changing behavior, to keep design clean
7. Pair Programming - all production code written by two people at one machine
8. Collective Ownership - anyone can change any code anywhere in the system at any time
9. Continuous Integration - integrate and test changes frequently, at least daily
10. 40-Hour Week - sustainable pace; overtime is a symptom of a deeper problem, not a solution
11. On-Site Customer - a real customer, available full-time, to answer questions and set priority
12. Coding Standards - team-wide conventions so code looks like it was written by one person