Phased delivery — major processes & flow maps

Overlap stages where policy allows; gates sit on arrows.

Guide · Updated · Source

1. Classic stage sequence (simplified)

Classic phased stage sequence

How phased delivery advances through governed stages, producing baselines consumed by the next stage.

  1. StartThe program enters the phased lifecycle with an approved charter or mandate.
  2. Core steps (see walkthrough below)Each stage executes work and proves exit criteria at transition gates.
  3. OutcomeThe sequence closes with released capability and recorded learnings.

Overlap stages where policy allows; gates sit on arrows.

2. Gate decision

Phase gate decision

How a checkpoint decides whether the program continues, refines, or escalates based on exit criteria.

  1. Current stateThe phase under review with its artifacts and open risks visible.
  2. Checkpoint / gateSponsors evaluate exit criteria packs for quality, risk, and readiness.
  3. refine or escalateCriteria not met triggers rework, deferral, or steering escalation.
  4. Continue flowApproved criteria commit spend and authorize the next baseline.

3. Change control path (scope)

Scope change control path

How governed change requests protect schedule, cost, risk, and traceability baselines.

  1. StartA proposed scope change enters the formal control path.
  2. Core steps (see walkthrough below)Impact analysis feeds steering with schedule, cost, risk, and traceability effects.
  3. OutcomeSteering approves a re-baselined artifact set or rejects the request.

4. Traceability thread

Requirements traceability thread

How requirement identifiers thread through design, test, and release for auditable coverage.

  1. StartA governed requirement ID anchors the traceability chain.
  2. Core steps (see walkthrough below)Links propagate from design through test cases to release notes.
  3. OutcomeThe thread yields reviewable evidence of end-to-end coverage.

5. Phases A–F (typical mapping)

Blueprint phase Typical phased locus
A Shape Initiate; charter; high-level requirements
B Plan Planning; WBS; schedule baseline
C Build Design and implementation per baseline
D Verify Test phases; inspections; exit evidence
E Release UAT; deployment; handover
F Learn Operate; warranty; benefits realization

6. Flow details (walkthrough)

Stage sequence — The linear diagram is pedagogical; real programs may overlap stages where policy allows. Gates sit on transitions; each stage produces baselines the next consumes. Map org stage names to blueprint A–F for one language across RAID, audits, and agents.

Gate decision — Gate packs prove exit criteria (quality, risk, readiness). Failed criteria mean hold and corrective actions, not silent waivers. Sponsor or steering approval commits spend and the next baseline; defer, kill, or replan are valid.

Change control — Change requests and impact analysis (schedule, cost, risk, traceability) feed steering decisions: re-baseline with versioned artifacts, or reject/queue. Ad-hoc scope without this path breaks audit trails.

Traceability — Requirement ID → design → test case → release note supports impact analysis and demonstrates coverage to auditors.

7. Authoritative sources & further reading

PMI — Standards & guides is listed in External reference URLs (methodology guides) for practitioner depth (some networks block automated fetches to pmi.org).