Extreme Programming Core Practices

The 12 “XP Xtudes” (Xtude is XP means ‘Attitude’) of Extreme Programming (XP) grouped into four categories

1. Fine Scale feedback

XP thrives on providing feedback at smaller intervals with higher frequency. This allows controlling deviation at the right time, since in software or any othe industry for that matter, once deviation starts happening it is dificult to control at the later stages.

• Test Driven Development via Programmer Tests (Unit Tests) and Customer Tests (Acceptance Tests/Automation Tests)
• Planning Game (Definition Iteration Objectives and playfield etc)
• Whole Team (Onsite Customer + Programmer + Quality Team + Customer Team + Scrum Master + Product Owner)
• Pair Programming ( two engineers participate in one development effort at one workstation)

2. Continuous Process rather than Batch

• Continuous Integration (Integrate Continuosly and keep the check using Nightly Builds)
• Design Improvement (Refactor Mercilessly)
• Small Releases (Release Often)

3. Shared understanding

• Simple Design (Do Simple Things, You Arent Gonna Need It, Once And Only Once, Simplify Vigorously)
• System Metaphor (XP way of defining the Architecture)
• Collective Code Ownership (Multiple People working on same code)
• Coding Standard or Coding Conventions (Uhh!! you know what it means, dont you?)

4. Programmer welfare

• Sustainable Pace (original name: Forty Hour Week)