# Extreme Programming

Extreme Programming combines rapid customer feedback with disciplined engineering practices such as pairing, testing, refactoring, and continuous integration.

- Type: method
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/extreme-programming/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Describe desired behavior with small stories and select a manageable set for a short planning cycle.
2. Clarify examples with customers and turn important behavior into automated acceptance and developer tests.
3. Implement in small steps using simple design, pair or ensemble collaboration, shared code ownership, and coding standards.
4. Integrate changes frequently, keep the build fast, and refactor continuously while tests protect behavior.
5. Release useful increments, gather feedback, adjust the plan, and maintain a sustainable pace.

## A 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.

## Where 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.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/extreme-programming/#visualization-extreme-programming>)

## Sources

1. [Extreme Programming Practices](<https://extremeprogrammingalliance.com/about-extreme-programming-xp/extreme-programming-xp-practices/>) — Extreme Programming Alliance · Professional practice reference
2. [Agile Glossary: Extreme Programming](<https://agilealliance.org/agile101/agile-glossary/>) — Agile Alliance · Institutional glossary
3. [Five XP Practices for Agile Development](<https://agilealliance.org/resources/sessions/five-xp-practices-for-agile-development/>) — Agile Alliance · Professional conference resource

## Related topics

- [Agile Product Development](<https://wiki.soroush.uk/topic/agile-product-development/>)
- [Feature-Driven Development](<https://wiki.soroush.uk/topic/feature-driven-development/>)
- [Crystal Methods](<https://wiki.soroush.uk/topic/crystal-methods/>)
