XP — major processes & flow maps

Iteration loop — Short iterations: plan a small story batch, build with pairing/TDD/CI, acceptance, demo with customer, retrospective; replan with what you learned.

Guide · Updated · Source

1. Iteration loop

XP iteration rhythm

How XP teams plan, build, demonstrate, and replan within short bounded iterations.

  1. Iteration loopFrames one XP iteration as a repeatable delivery and learning cycle.
  2. StartThe team opens the iteration with a bounded story batch from the backlog.
  3. Core steps (see walkthrough below)Pairing, TDD, CI, acceptance, demo, and retrospective execute the planned work.
  4. OutcomeDelivered stories and retrospective learnings feed the next planning cycle.

2. TDD micro-loop (within story)

TDD story micro-loop

How red-green-refactor cycles within a story keep design test-guided and CI-backed.

  1. TDD micro-loop (within story)Frames test-driven development as the default rhythm inside story work.
  2. StartA failing test expresses the next behavior the story requires.
  3. Core steps (see walkthrough below)Red, green, and refactor repeat until the story's tests pass.
  4. OutcomeStory work completes with passing tests and a design CI can re-verify.

3. Story lifecycle

XP story acceptance lifecycle

How agreed acceptance tests define done before implementation and customer acceptance closes the story.

  1. Story lifecycleFrames a story from agreed acceptance through customer-visible completion.
  2. StartCustomer and team agree acceptance tests that define visible done.
  3. Core steps (see walkthrough below)Implementation with unit tests and green CI satisfies the agreed criteria.
  4. OutcomeCustomer acceptance confirms the story meets the agreed criteria.

4. Planning game (priorities vs estimates)

Planning game scope fit

How customer value ordering and team estimates converge on a bounded iteration pull.

  1. Planning game (priorities vs estimates)Separates what the customer values most from what the team can deliver.
  2. Current stateThe customer orders stories by value while the team supplies estimates.
  3. Checkpoint / gateThe team checks whether top-value stories fit the iteration capacity.
  4. refine or escalateOversized top-value work triggers split, deferral, or explicit scope negotiation.
  5. Continue flowAgreed stories enter the iteration as a bounded, value-ordered batch.

5. Phases A–F (XP locus)

Phase Typical XP locus
A Shape Stories with customer; release themes
B Plan Iteration planning; tasks
C Build Pairing, TDD, CI
D Verify Acceptance tests; collective ownership
E Release Small / frequent releases
F Learn Production feedback; retrospective

6. Flow details (walkthrough)

Iteration loop — Short iterations: plan a small story batch, build with pairing/TDD/CI, acceptance, demo with customer, retrospective; replan with what you learned.

TDD — Red (failing test) → Green (minimal code) → Refactor (keep tests green); repeat within the story so design stays test-guided and CI catches regressions.

Story lifecycle — Acceptance tests agreed before implementation define customer-visible done; then implement with unit tests and green CI; customer acceptance closes the story.

Planning game — Customer orders by value; team estimates; pull stories until capacity fits. If top value does not fit, split, defer, or negotiate scope explicitly.

7. Authoritative sources & further reading

Full curated list: External reference URLs (methodology guides).