Handbook
Extreme Programming (XP)
**Extreme Programming (XP)** is a discipline of software development based on **values** (communication, simplicity, feedback, courage, respect) and **practices** that emphasize **technical excellence
Extreme Programming (XP)
What it is
Extreme Programming (XP) is a discipline of software development based on values (communication, simplicity, feedback, courage, respect) and practices that emphasize technical excellence: test-driven development, continuous integration, small releases, refactoring, collective ownership, and pair programming (or mob/ensemble). XP is often combined with Scrum (cadence) or Kanban (flow).
Process diagram (handbook)
TDD, CI, pairing, refactoring, and small releases interleave daily; the diagram orders them for readability.
Authoritative sources (external)
| Resource | Executive summary (why it’s linked here) |
|---|---|
| Wikipedia — Extreme programming | Encyclopedia overview of practices and history—stable entry before books or blogs. |
| Agile Alliance — Agile glossary | Searchable terms—find Extreme Programming and related Agile vocabulary. |
| Ron Jeffries — XP | Practitioner site—stories and guidance from a central XP voice. |
| martinfowler.com — XP (Bliki) | Short expert summary on a widely cited blog—quick read. |
Note: Kent Beck’s Extreme Programming Explained is the classic book; purchase or library for full narrative.
Practices (summary)
| Practice | Intent |
|---|---|
| Test-driven development | Red–green–refactor; executable specification. |
| Continuous integration | Integrate often; keep trunk/main green. |
| Refactoring | Improve design without changing behavior. |
| Small releases | Reduce batch size and risk. |
| Pair programming | Knowledge sharing, review in the moment. |
| Collective code ownership | Anyone can improve any module. |
| Coding standard | Shared style reduces friction. |
| Sustainable pace | No heroics as a norm; overtime is an exception signal. |
Mapping to this blueprint’s SDLC
| XP practice | Blueprint touchpoint |
|---|---|
| CI | Software development lifecycle (SDLC) §7, project docs/development/CI-CD.md, handbook cicd.html. |
| Testing | Story DoD, Test plan — [scope]. |
| Small increments | Phase D build; link commits to work-unit IDs. |
Ceremonies: XP practices as intent types — Extreme Programming (XP) → ceremony foundation · foundation.
Roles: how XP merges Assure into Build via practices and keeps Demand close—Roles, archetypes & methodology titles §2, §4, §5 (Methodology tweaks XP).
Agentic SDLC: XP + agents + tracking
XP’s technical bar pairs well with agents if you keep humans in the loop:
| Topic | Guidance |
|---|---|
| TDD | Agents can propose tests and code; human confirms intent and edge cases. |
| Pairing | Human–agent pairing is a common pattern; record Co-authored-by or team norms if attribution matters. |
| CI as safety net | More important when volume of change increases — gates in CI are non-negotiable. |
| Sustainable pace | Agent throughput can mask review debt; watch WIP on review and defect escape rate. |
| Tracking foundation | Quality signals (CI) correlate with commits; they are a parallel stream, not redefined as “contributor” in the foundation model. |
Prescriptive deep dive (teams)
Package Extreme Programming (XP) — deep-dive package (blueprint) — foundation fit, customer/coach/developers, iteration events, TDD/CI loop maps. Handbook: methodologies-xp-foundation.html through methodologies-xp-process.html.
Further reading
- Wiki.c2.com — Extreme Programming Roadmap — Classic wiki index of XP topics; dated but historically influential.
- Companion: Scrum, Kanban, Agentic SDLC
Canonical source
Edit https://github.com/autowww/blueprints/blob/main/sdlc/methodologies/xp.md first; regenerate with docs/build-handbook.py.