DOMAIN 3
PMBOK 7 Performance Domain · Deep Dive
Development Approach & Life Cycle
This domain is about how the work gets done: the development approach (predictive → adaptive), the delivery cadence (when deliverables are released), and the life cycle (the phases the project moves through) — then aligning all three to the product and context. It is where tailoring (Poster 5) lands first.
Visual Map — The Development-Approach Spectrum
Left = certain requirements, change is costly; right = uncertain requirements, change is welcomed. Hybrid blends the two — e.g., an adaptive build inside a predictive governance shell.
Iterative vs Incremental (the classic trap)
Adaptive = iterative + incremental, done in short, change-responsive cycles.
Delivery Cadence — When You Release
- Single
- one delivery at the end (e.g., a building handed over).
- Multiple
- several deliveries, often phased components.
- Periodic
- on a regular schedule (e.g., monthly releases).
- Continuous
- a constant flow of increments to customers (DevOps).
Life Cycle & Phases
- A life cycle = the series of phases from start to completion.
- A phase = a set of logically related activities ending in a deliverable.
- Phase gates = review / go-no-go decision points between phases.
- The development approach drives the number, length & cadence of phases.
Selecting an Approach — What to Weigh
| Lens | Considerations |
|---|---|
| Product / result | innovation, requirements certainty, scope stability, ease of change, delivery options, risk, safety & regulation |
| Project | stakeholders, schedule constraints, funding availability |
| Organisation | structure, culture, capability, team size & distribution |
Aligning the Three
- Keep approach + cadence + life cycle coherent — e.g., adaptive approach → iterative life cycle → periodic/continuous cadence.
- Predictive approach → few sequential phases → single/few deliveries.
- Misalignment = rework, waste & confused governance.
Interactions with Other Domains
- Shapes Planning (how you plan) & Project Work (ways of working).
- Sets the Delivery & Measurement cadence.
- Adaptive approaches absorb Uncertainty; influences Team & Stakeholder engagement rhythm.
Exam Concepts
- Iterative = refine the whole; incremental = add pieces; adaptive = both.
- Cadence types: single · multiple · periodic · continuous.
- Approach drives the life cycle, not the reverse.
- Hybrid blends predictive & adaptive deliberately.
Executive View
- The approach choice is a risk / speed / value trade-off.
- Right cadence = faster value & feedback.
- Don't mandate one approach across all work.
Industry Examples
- Predictive: bridge build — sequential phases, single handover.
- Incremental: building delivered floor-by-floor.
- Adaptive: SaaS with continuous deployment.
- Hybrid: medical device — agile software in a regulated shell.
Measuring Outcomes
- Deliverables produced at the chosen cadence.
- The approach fits the context; the life cycle enables value.
- Minimal rework from a mismatched approach; team can re-tailor as they learn.
Memory Hooks
- "Approach → Cadence → Life Cycle, then ALIGN."
- Iterative = redo to improve · Incremental = add to complete.
- Cadence S-M-P-C: Single · Multiple · Periodic · Continuous.
60-sec Review
Place the 4 approaches on the spectrum
Iterative vs incremental
4 cadence types
Life cycle vs phase vs gate
Why align the three
PMI Visual Wall · Domain Deep-Dive · Development Approach & Life Cycle · original instructional design · A3 landscape