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.

Here, let's call them:
=== Outer Ring ===
The big picture:
 * WholeTeam (aka OnSiteCustomer)

 * PlanningGame
 * SmallReleases
 * CustomerTests
=== Middle Ring ===
Within the development team:
 * ContinuousIntegration
 * CollectiveCodeOwnership
 * CodingStandard

 * SystemMetaphor
 * SustainablePace
=== Inner Ring ===
At the developer level:
 * SimpleDesign
 * PairProgramming
 * TestDrivenDevelopment
 * DesignImprovement or Refactoring


(List cribbed from [[http://xprogramming.com/|Ron Jeffries' site]] where you'll also find his [[http://www.xprogramming.com/images/circles.jpg|diagram of concentric rings]].)

== Original list by Kent Beck ==

As listed on page 54 in the White Book [ISBN: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

The major difference (other than some renaming) is that Testing has been split into Customer Tests (does the software do what the Customer wants?) and Programmer Tests (does the software do what the Programmer intended?).  The concept of Programmer Tests has then been expanded to Test Driven Development, which is incredibly more powerful than testing after the fact.