SkarpChapter 3 of 20
Project Life Cycles and Approaches: Predictive, Adaptive, and Hybrid
Trace a project’s journey from start to finish and see how different life cycle choices—predictive, adaptive, or hybrid—change what you plan, when you plan it, and how you respond to uncertainty. This is where the exam’s language about life cycles finally becomes concrete.
Big Picture: Where Life Cycles Fit in Your CAPM Map
Why Life Cycles Matter on CAPM
You must recognize which life cycle a scenario is using and why that choice makes sense. The exam rarely just asks for a definition; it wraps life cycles inside short stories.
From Projects to Life Cycles
A project is "A temporary endeavor undertaken to create a unique product, service, or result." The project life cycle is the series of phases from start to closure that this project passes through.
Scenario Clues
Exam stems like "all requirements are planned upfront" or "customer reviews increments every two weeks" are clues. They usually point to predictive, adaptive, or hybrid life cycles.
Modern PMI Language
Recent PMI standards emphasize predictive vs adaptive vs hybrid more than the old "waterfall vs agile" debate. This module uses that up‑to‑date language throughout.
Project Life Cycle vs Product Life Cycle
Two Different Life Cycles
Project life cycle is about phases of doing the project work. Product life cycle is about phases of the product in the market: intro, growth, maturity, decline.
Many Projects, One Product
A single product can have many projects. A banking app may have separate projects for its first release, a redesign, regulatory updates, and final migration.
Finite vs Long-Lived
A project life cycle is finite and ends at closure. A product life cycle can last years or decades, spanning many projects and releases.
Exam Signal Words
Words like "sales", "market share", "retirement" signal product life cycle. Words like "planning", "executing", "closing" signal project life cycle.
Predictive Life Cycle: Definition and Core Pattern
Predictive: PMI Definition
predictive life cycle: "A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle." Memorize this wording.
Upfront Planning
Predictive projects invest early in defining scope, schedule, and budget, often using a work breakdown structure and estimating each work package.
Sequential and Controlled
Work flows through sequential phases with formal handoffs. Changes are tightly controlled through change control to preserve predictability.
When Predictive Fits
Best when requirements are stable, tech is familiar, stakeholders want fixed scope/schedule, and late changes are very costly (e.g., construction).
Predictive in Practice: A Hospital Wing Project
Hospital Wing Context
New hospital wing: strict regulations, detailed blueprints, and a board that wants a fixed budget before construction starts.
Predictive Pattern
Months of upfront planning, detailed WBS, estimates for each work package, then sequential phases: site prep, structure, interior, systems, inspection.
Change is Costly
Requests like "add two more operating rooms" are major scope changes and go through formal change control, often needing more time or money.
Why Predictive Fits
Physical construction has costly late changes, safety rules, and stakeholders who demand predictability, all aligning with a predictive life cycle.
Adaptive Life Cycle: Definition and Core Pattern
Adaptive: PMI Definition
adaptive life cycle: "A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration."
Iterations and Backlog
Work is done in short, fixed-length iterations. A product backlog is an ordered list of needed product items, managed by the product owner.
Feedback and Change
Stakeholders see working increments frequently. Feedback updates the backlog. Change is expected between iterations, not fought.
When Adaptive Fits
Best when requirements are unclear or changing, tech or markets evolve quickly, and stakeholders refine needs by seeing working product.
Adaptive in Practice: A Mobile App Startup
Startup Context
A new social fitness app: fuzzy vision, fast-changing market, and a cross‑functional team able to ship working software every two weeks.
Using the Backlog
The product owner manages a product backlog with items like sign‑up, tracking, and challenges, constantly reordering based on learning.
Sprints and Demos
In each two‑week sprint, the team commits to specific items. At sprint end, they demo to users and feed that learning into future backlog changes.
Why Adaptive Fits
Unclear requirements, need for rapid feedback, and shifting competition all favor an adaptive life cycle over a fixed upfront plan.
Hybrid Life Cycles: Mixing Predictive and Adaptive
What is Hybrid?
A hybrid life cycle deliberately combines predictive and adaptive elements so each part of the project uses the most suitable approach.
Hybrid Patterns
Common patterns: phase‑based (predictive then adaptive), component‑based (hardware predictive, software adaptive), or governance hybrid (agile teams, predictive reporting).
Exam Scenarios
Hybrid clues: fixed deadline and budget but flexible scope details, or regulated components plus iterated user‑facing features.
Not a Random Mix
Hybrid is intentional: analyze which work is stable vs uncertain, then choose predictive for the stable parts and adaptive for the uncertain ones.
Thought Exercise: Match Project to Life Cycle
Work through these scenarios and decide which life cycle best fits: predictive, adaptive, or hybrid. Think about requirements stability, stakeholder involvement, and cost of change.
- City Road Resurfacing Project
- The city plans to resurface 10 km of existing roads.
- Standards and materials are well known.
- The public mainly cares that it finishes on time with minimal disruption.
- Question: Which life cycle would you choose and why?
- Internal Analytics Dashboard for Sales
- Sales leaders know they want "better visibility" but are unclear on exact charts.
- They want to see early versions and adjust frequently.
- IT has a fixed annual budget but some flexibility in scope.
- Question: Would you use predictive, adaptive, or a hybrid? What would be predictive vs adaptive?
- Smart Device with Embedded Software
- Your company is creating a new smart thermostat.
- Hardware design (electronics, casing) must be frozen early for manufacturing.
- The mobile app and cloud services will likely evolve based on user feedback.
- Question: What life cycle combination makes sense for hardware vs software?
Pause and write down your answers in brief bullet points. Then compare them to the suggested reasoning in the next explanation step.
When to Use Predictive vs Adaptive vs Hybrid
Road Resurfacing
Stable standards and methods, low requirement uncertainty. Best fit: predictive life cycle with early scope, time, and cost determination.
Sales Dashboard
Fuzzy needs, frequent stakeholder input, but a fixed budget. Best fit: hybrid with predictive governance and adaptive feature development.
Smart Thermostat
Hardware must be frozen early; software can iterate. Best fit: hybrid: predictive for hardware, adaptive for app and cloud services.
Rule of Thumb
Stable + costly change → predictive. Uncertain + evolving needs → adaptive. Mixed stability across components → hybrid.
Quick Check: Predictive vs Adaptive Definition
Test your recall of PMI's exact definitions.
Which option correctly states PMI's definition of an adaptive life cycle?
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- A development life cycle that combines predictive and adaptive phases to optimize cost and schedule.
- A development life cycle in which the product backlog is fully defined at the beginning of the project.
Show Answer
Answer: B) A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
PMI defines **adaptive life cycle** as "A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration." Option A is the definition of a **predictive life cycle**. Option C describes hybrid conceptually but is not the PMI definition. Option D adds a condition (backlog fully defined at the beginning) that is not part of the definition and is incorrect for adaptive.
Scenario Quiz: Choose the Best Life Cycle
Apply what you know to a realistic scenario.
Your organization is upgrading its core payroll system. Legal rules and calculation logic are tightly regulated and stable, but the self-service web portal's design is unclear and will depend on employee feedback. Which approach is MOST appropriate?
- Pure predictive life cycle for the entire project.
- Pure adaptive life cycle for the entire project.
- Hybrid: predictive for core payroll engine, adaptive for self-service portal.
- Hybrid: adaptive for core payroll engine, predictive for self-service portal.
Show Answer
Answer: C) Hybrid: predictive for core payroll engine, adaptive for self-service portal.
The **core payroll engine** has stable, regulated requirements, ideal for a **predictive** approach. The **self-service portal** has uncertain, user-driven requirements, ideal for an **adaptive** approach. That makes a **hybrid** life cycle with predictive for the engine and adaptive for the portal the best choice. Using pure predictive or pure adaptive for everything would misalign methods with uncertainty. Option D reverses the logic and is not appropriate.
Flashcards: Key Life Cycle Terms
Use these cards to reinforce critical definitions and distinctions. Try to say the answer before flipping each card.
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- work breakdown structure
- A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
- work package
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- Project life cycle vs product life cycle
- Project life cycle: phases a project passes through from start to closure. Product life cycle: phases a product passes through in the market (introduction, growth, maturity, decline). A product can span many projects.
- One clue that a predictive approach is appropriate
- Requirements are stable and well understood, and the cost of late changes is very high (e.g., construction, regulated infrastructure).
- One clue that an adaptive approach is appropriate
- Requirements are uncertain or rapidly changing, and stakeholders need frequent feedback on working increments to refine what they want.
- Hybrid life cycle (concept)
- An approach where some parts of the project use predictive practices and other parts use adaptive practices, chosen intentionally based on the level of uncertainty and need for flexibility.
Exam-Focused Wrap-Up and Next Steps in Your Study Path
Core Exam Targets
Know the exact PMI definitions of predictive and adaptive life cycles, and clearly distinguish project life cycle from product life cycle.
Scenario Recognition
Practice spotting clues: stable vs changing requirements, stakeholder feedback frequency, and cost of change to choose predictive, adaptive, or hybrid.
Watch the Traps
Do not confuse product with project life cycle, or assume "agile" always means purely adaptive; many realistic scenarios are actually hybrid.
Integrate With Your Study Path
Upcoming diagnostics and mock exams will pressure‑test life cycle choices. Spaced review will resurface any weak areas until they are solid.
Key Terms
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- work package
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- hybrid life cycle
- An approach that deliberately combines predictive and adaptive elements in different parts or phases of the same project, based on the level of uncertainty and need for flexibility.
- product life cycle
- The series of phases a product goes through in the market, typically including introduction, growth, maturity, and decline.
- project life cycle
- The series of phases that a project goes through from its start to its closure.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- work breakdown structure
- A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.