| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
|
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].) |
|
| Line 16: | Line 44: |
|
Here, let's call them * WholeTeam (aka OnSiteCustomer) * PlanningGame * SmallReleases * CustomerTests * SimpleDesign * PairProgramming * TestDrivenDevelopment * DesignImprovement or Refactoring * ContinuousIntegration * CollectiveCodeOwnership * CodingStandard * SystemMetaphor * SustainablePace (List cribbed from [http://xprogramming.com/ Ron Jeffries' site] ) |
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:
Middle Ring
Within the development team:
Inner Ring
At the developer level:
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].)
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