Fine scale feedback

• Test Driven Development via Programmer Tests (Unit Tests) and Customer Tests (Acceptance Tests)
• Planning Game to determine which features (User Stories) will be implemented in each release / iteration to maximize the business value
• Whole Team - customer is part of the project team, not a third party. One representative is immediately available to the developers for queries
• Pair Programming - two developers work on the same code

Continuous process rather than batch

• Continuous Integration of codebase
• Design Improvements by Refactoring the code continuously
• Small Releases

Shared understanding

• Simple Design of the solution and no big design upfront
• System Metaphor as a collective dictionary of project terms
• Collective Code Ownership - any developer can change any code
• Coding Standards are strictly adhered

Programmer welfare

• Sustainable Pace - do not stretch the limits of working hours without real need