Step 3
Development Approaches & Project Lifecycles — Illustrated Study Guide
Project lifecycles, phases and phase gates, how risk and cost of change shift over time, and the Predictive / Adaptive / Hybrid spectrum — full notes, an illustration for every topic, and a 100-question practice quiz.
Lifecycle Project Lifecycle & Phase Gates
- A project lifecycle is the path a project follows from start to closure.
- It applies to Predictive, Agile, Hybrid, or any other development approach.
- It includes the major activities and phases needed to complete the project.
Generic lifecycle flow
1
Project Start & Gathering Requirements
2
Design (UI)
3
Development (Build)
✓
Phase Gate
A review point to decide: move forward, change direction, repeat work, pause, or stop.
4
Testing & Launch
5
Project Closure
Project phases
- A project is broken into multiple phases to make the work easier.
- A phase is a group of related activities that produce a deliverable or outcome.
- Phases can be sequential, overlapping, transitional, or a combination, depending on the project.
What is a phase gate?
- A review point used to decide whether a project should move forward, change direction, repeat work, pause, or stop.
- Can happen at the end of a phase, or before a phase starts, to confirm alignment, resources, planning, and risks before continuing.
Visual recap
Lifecycle Project Phases Over Time
Risk & Uncertainty
- Usually highest at the start of a project.
- Decreases as decisions are made and deliverables are accepted.
- Stakeholder influence on change is strongest early, when changes are easier and less costly.
Cost of Changes
- Usually low at the start and increases as the project moves forward.
- Cost and staffing follow a similar pattern: low at the start, rising during the work, dropping quickly near the end.
- Regular stakeholder feedback helps identify risk earlier and confirms the project is delivering value.
Key takeaways
- Projects are made up of different phases.
- At the beginning of a project: high uncertainty, but changes are easy to make.
- Do phase-gate reviews throughout the project.
- As you approach the end of the project, risk and uncertainty reduce — but changes get expensive.
Visual recap
Development Approaches
Approaches Development Approaches — Overview
- A development approach is a method used to create and evolve a product, service, or result during the project.
- Different from a project's development phases — the approach explains how the project will be managed and executed.
- Usually chosen by the project manager, with input from the project management team.
- The choice depends on scope, timeline, goals, risks, technology, complexity, stakeholder involvement, and organizational needs.
The spectrum
Predictive
- Requirements are clear and stable.
- No incremental or iterative work.
- Scope, schedule & cost baselines planned upfront together (integrated baseline).
Hybrid
- Midpoint of the spectrum.
- Combines Predictive and Adaptive/Agile methods.
Adaptive
- Best when requirements are unclear, complex, or uncertain.
- Work reviewed in short timeboxes; feedback adjusts the work and evolves the baseline.
Moving from Predictive toward Adaptive/Agile, the amount of iterative and incremental work increases.
Triple constraint by approach
Predictive Project
- Scope is fixed; budget and schedule are variable.
Adaptive Project
- Budget and schedule are fixed; scope is variable.
- The list of requirements is the product backlog — items get added as the project goes.
Visual recap
Approaches Predictive Project Management (Waterfall / Traditional)
Flow (waterfall / staircase)
1
Feasibility
2
Design
3
Build
4
Check
5
Transfer
6
Close
- Works best when project scope can be clearly defined and stabilized early.
- Useful for large projects, major investments, or regulated environments needing strong change control.
- Scope, schedule, cost, resources, quality requirements, and risks are planned early and expected to stay mostly stable.
- Often uses phase gates to review progress before moving on to the next phase.
Visual recap
Approaches Adaptive / Agile Approach
- A repetitive cycle, also known as change-driven.
- Useful when project requirements and technical solutions are uncertain or likely to change.
- A clear project vision is set early, but detailed requirements are refined, changed, or replaced through feedback.
- Can be iterative (work improved through repeated cycles) and/or incremental (product delivered in small, usable pieces that build on each other).
- Agile methods often use short iterations, usually 1 to 4 weeks, where the team plans, builds, reviews, and adjusts the work.
Adaptive lifecycle
1
Define Project & Product Visions
2
Repetitive cycle: Iteration 1 → Iteration 2 → Iteration 3 → ...
Each iteration draws from a shared Feedback / Backlog / Motivation pool, and feedback flows back in to keep the cycle going.
Increment vs. Iterative
Increment
- Delivering the product piece by piece as time progresses.
- Example: developing a website by delivering the homepage first, then other pages, sharing each for review as it's developed.
Iterative
- Build the entire scope at a basic level, then refine through repeated feedback.
- Example: developing a phone by delivering for feedback, getting feedback, changing the spec, then delivering again.
Visual recap
Approaches Hybrid Approach
- A combination of Predictive and Agile/Adaptive methods.
- Works well when part of the project is clear and stable while other parts are uncertain or risky.
- Some deliverables can be modularized or handled by different teams.
- Gives the project flexibility for changing work while still keeping control over the work that's stable.
- Can use one main approach overall, while using a different approach for certain phases.
Visual recap
Practice Time
Recall Recall Quiz
Straight recall — lifecycle, phases, phase gates, phases over time, and the development-approach spectrum, straight from the notes above.
Scenario Case Study Quiz
Short, standalone situational questions — apply the concepts above to one scenario at a time.
New Format Long Case Studies
Matches the newer PMI exam format: one longer scenario, several linked questions. 6 case studies, 5 questions each — one per Step 3 topic.
Advanced Step 1 + Step 2 + Step 3 Mix
The toughest round — integration questions blending Step 1 fundamentals, Step 2 principles & leadership, and Step 3 lifecycles & development approaches.