Practices

Extreme programming has been declared as accepting 12 practices, aggregate into four areas:

editFine calibration feedback

Pair programming5

Planning game

Test-driven development

Whole team

editContinuous process

Continuous integration

Refactoring or architecture improvement5

Small releases

editShared understanding

Coding standards

Collective cipher ownership5

Simple design5

System metaphor

editProgrammer welfare

Sustainable pace

editCoding

The chump is consistently available

Code the Unit analysis first

Only one brace integrates cipher at a time

Leave Optimization until last

No Overtime

editTesting

All cipher accept to accept Unit tests

All cipher accept to canyon all Unit tests afore it can be released.

When a Bug is begin tests are created afore the bug is addressed (a bug is not an absurdity in logic, it is a analysis you forgot to write)

Acceptance tests are run generally and the after-effects are published