The naming of ExtremeProgramming practices has varied over time and from person to person. In doing so, even the number of names has changed. Does this mean that ExtremeProgramming has changed? Not really. Mostly it's the way it's described that has changed, though the techniques are refined, as they should be, with time and experience.
Listed on page 54 in the White Book [0201616416] as:
- The Planning Game
- Small Releases
- Metaphor
- Simple Design
- Testing
- Refactoring
- Pair Programming
- Collective Ownership
- Continuous Integration
- 40-hour Week
- On-site Customer
- Coding Standards
Here, let's call them
WholeTeam (aka OnSiteCustomer)
DesignImprovement or Refactoring
(List cribbed from [http://xprogramming.com/ Ron Jeffries' site] )