Handbook
Extreme Programming (XP) → ceremony foundation
**Purpose:** Map **XP practices** that behave like **recurring collaboration** to methodology-neutral **intent types** in [`ceremony-foundation.md`](ceremony-foundation.md).
Extreme Programming (XP) → ceremony foundation
Purpose: Map XP practices that behave like recurring collaboration to methodology-neutral intent types in Ceremony foundation (methodology-neutral).
Canonical narrative: https://forgesdlc.com/methodology-xp.html
XP emphasizes values and technical practices; some map cleanly to ceremony intents, others are habits rather than meetings.
Practices × intent types
| XP practice / ritual | Foundation intents (primary → secondary) | Notes |
|---|---|---|
| Planning game | C1 Align → C2 Commit | Customer and developers negotiate scope for a small horizon. |
| Small releases | C4 Inspect → C6 Assure | Frequent feedback from real use; CI and TDD embed C6 continuously. |
| Stand-up (if team uses one) | C3 Sync | Not uniquely “XP”—often borrowed with Scrum/Kanban cadence. |
| Retrospective (if adopted) | C5 Improve | Common blend with Scrum-style process. |
| Pair programming / ensemble | C3 Sync (micro) + C6 (continuous review) | Review in the moment; not a calendar ceremony but satisfies coordination and quality intent. |
| On-site customer | C1 + C4 (ongoing) | Demand archetype embedded—reduces need for heavy periodic C4 batches. |
C6 is strongly embedded in TDD, CI, and collective ownership—see https://forgesdlc.com/methodology-xp.html.
Suggestions (XP-specific)
| Practice / area | Suggestions |
|---|---|
| Planning game | Keep slices small enough that C2 is frequent; if planning drifts long, you’ve smuggled in C1 without time-box. |
| On-site customer | Use continuous C1/C4; still schedule explicit checkpoints if the customer is part-time or a proxy. |
| Pairing / ensemble | Treat as live C3 + C6 for the shared task; ensure cross-pair sync exists for system integration. |
| Small releases | Each release is a C4 opportunity; if releases are too small for stakeholders, batch demos but not integration. |
| Retro / coach | If you skip formal C5, get improvement signal from metrics (CI, defects) and pair rotation feedback. |
Vocabulary crosswalk: Methodology bridge — foundation intents ↔ named ceremonies.
Canonical source
Edit https://github.com/autowww/blueprints/blob/main/sdlc/methodologies/ceremonies/xp.md first; regenerate with docs/build-handbook.py.