Extreme Programming
Extreme Programming combines rapid customer feedback with disciplined engineering practices such as pairing, testing, refactoring, and continuous integration.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/extreme-programming/
01What it means
Extreme Programming (XP) is an Agile software-development method that takes beneficial practices—testing, review, integration, simple design, and customer feedback—and applies them frequently and consistently. It joins planning and collaboration practices with a demanding technical discipline intended to keep software changeable.[1][2][3]
- 01Customer priorityValuable behavior expressed through shared examples
- 02Small design stepSimplest change that supports the current need
- 03Test + pairRapid feedback while code is being shaped
- 04Continuous integrationMerge verified changes frequently
- 05Small releaseWorking software creates real customer evidence
- 06RefactorImprove structure while preserving behavior
Customer and code feedback guide the next small change
XP practices work as a mutually supporting system; copying isolated ceremonies without testing, integration, collaboration, and sustainable pace weakens the feedback loop.
02Why it matters
Short iterations alone do not make code safe to change. XP addresses that gap with fast automated feedback, shared ownership, close collaboration, and incremental design. The practices reinforce one another: tests support refactoring, continuous integration exposes conflicts, pairing spreads knowledge, and small releases bring real feedback sooner.
03When to use it
Use XP when software requirements evolve, the team can collaborate closely with informed customers, and frequent delivery matters. It is especially useful where defects and technical debt are slowing change. Adopt practices deliberately and strengthen the test and deployment environment rather than copying visible rituals only.
04How it works
- Describe desired behavior with small stories and select a manageable set for a short planning cycle.
- Clarify examples with customers and turn important behavior into automated acceptance and developer tests.
- Implement in small steps using simple design, pair or ensemble collaboration, shared code ownership, and coding standards.
- Integrate changes frequently, keep the build fast, and refactor continuously while tests protect behavior.
- Release useful increments, gather feedback, adjust the plan, and maintain a sustainable pace.
05A practical example
A payments team must change fee rules weekly. A product specialist provides concrete examples, developers write tests before each rule, and pairs integrate small changes throughout the day. When duplication appears, they refactor behind the test suite. A feature flag supports an early release to internal accounts, producing feedback before general rollout.
06Where it breaks
XP requires substantial engineering skill, automated-test investment, and frequent customer access. Pairing can be imposed badly or become exhausting without team choice and rotation. Legacy systems may have slow feedback loops, and regulated environments still need appropriate documentation and evidence. Selecting isolated practices may lose the risk-reducing effect of the full system.
Common mistakes
- Calling iterations XP while omitting automated tests, refactoring, and continuous integration.
- Treating simple design as permission to ignore foreseeable quality and architecture concerns.
- Using pair programming as surveillance rather than collaborative problem solving.
07Sources
- Extreme Programming PracticesExtreme Programming Alliance · Professional practice referenceExtreme Programming Practices
- Agile Glossary: Extreme ProgrammingAgile Alliance · Institutional glossaryAgile Glossary: Extreme Programming
- Five XP Practices for Agile DevelopmentAgile Alliance · Professional conference resourceFive XP Practices for Agile Development