SkarpChapter 3 of 20
Project Life Cycles, Development Approaches, and Governance
Trace how a project moves from concept to closure, and see how different development life cycles—predictive and adaptive—shape planning, control, and governance.
From Concept to Closure: The Project Life Cycle
What Is a Project Life Cycle?
A project life cycle is the series of phases a project passes through from start to finish, from the first idea to formal closure.
Typical Phases
Common high-level phases: Concept/Initiation, Planning, Execution with Monitoring and Controlling, and Closure. Names vary, logic is similar.
Focus of Each Phase
Concept: feasibility and go/no-go. Planning: refine scope, schedule, cost. Execution: do the work and control performance. Closure: handover and lessons.
Exam Trap: Life Cycles
Do not confuse project life cycle (how you manage the project) with development life cycle (how you build) or product life cycle (market stages).
Project Life Cycle vs Product Life Cycle
Two Different Life Cycles
Project life cycle: start to end of a project. Product life cycle: idea to retirement of a product in the market.
Smartphone Example
One phone model has a long product life. Multiple shorter projects support it: design, software updates, successor models, decommissioning.
Key Differences
Duration: product > project. Focus: market performance vs project objectives. Ownership: product manager vs project manager.
Exam Angle
If a product continues after project closure, that is normal. The project life cycle ends; the product life cycle continues.
Development Life Cycles: Predictive, Adaptive, and Hybrid
What Is a Development Life Cycle?
It is how you structure the work to build the solution inside the project life cycle: predictive, adaptive, or hybrid.
Predictive Life Cycle
Definition: 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
Definition: A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
Hybrid Approaches
Hybrid mixes predictive and adaptive, such as fixed-scope infrastructure with agile sprints for the user interface.
Exam Reminder
Project life cycle (phases) exists regardless of approach. Predictive vs adaptive is about how you develop the solution.
How Life Cycle Choice Changes Planning and Control
Predictive Portal Project
Detailed requirements, WBS, schedule, and cost baseline are set early. Changes go through a formal change control board.
Adaptive Portal Project
High-level vision plus a product backlog. Detailed planning happens only for the next short iteration. Change flows through backlog priorities.
Hybrid Portal Project
Security and integration use predictive milestones; user-facing features are built in agile sprints with frequent demos.
Exam Pattern
Look for clues: stable vs changing requirements, regulatory constraints, and stakeholder access to choose predictive, adaptive, or hybrid.
Project Governance and Phase/Decision Gates
What Is Project Governance?
Governance is the framework of rules, roles, and decision processes that guide the project and align it with organizational strategy.
Phase / Decision Gates
Phase gates are formal reviews at key points where leaders decide to continue, pause, change direction, or terminate the project.
Who Decides at Gates?
The project manager presents evidence; sponsors or a steering committee typically make the go/no-go decisions.
Gates Across Life Cycles
Predictive: gates at major phases. Adaptive: iteration reviews as mini-gates plus release gates. Hybrid: mix of both styles.
Governance Mechanisms: Steering Committees, CCBs, and Escalation Paths
Steering Committee
A senior group that provides strategic direction and makes high-impact decisions. The sponsor often chairs it; PM escalates major issues here.
Change Control Board (CCB)
A formal group that reviews and approves or rejects change requests that impact baselines or major requirements.
Escalation Paths
Predefined routes to raise unresolved issues, e.g., team → PM → functional manager or sponsor → steering committee.
Life Cycle Influence
Predictive: formal CCBs and escalations. Adaptive: lighter governance via backlog and reviews, but major issues still escalate.
Thought Exercise: Choosing the Right Life Cycle and Governance
Apply what you have learned by classifying these scenarios and sketching appropriate governance. Think them through before checking your reasoning with the explanations.
- National ID System Modernization
- Government agency, strict security and privacy regulations, fixed go-live date set by law, requirements mostly defined in legislation.
- Questions:
- Which development life cycle is most appropriate (predictive, adaptive, hybrid)?
- Which governance mechanisms are critical (phase gates, CCB, steering committee, escalation paths)?
- Campus Event App for a One-Time Festival
- Student-led team, short timeline (3 months), requirements likely to change as sponsors and artists sign up, success depends on user experience.
- Questions:
- Which development life cycle would you choose and why?
- How would you involve stakeholders in governance without slowing them down?
- Hybrid Case: Hospital Patient Portal
- Regulatory constraints on data, but patients and clinicians want to experiment with new features.
- Questions:
- What parts would you treat predictively vs adaptively?
- How would you mix formal phase gates with iteration reviews?
Suggested reasoning (self-check)
- Scenario 1: Predictive with strong phase gates, a formal CCB, and a steering committee including legal/compliance.
- Scenario 2: Adaptive (agile), with frequent demos, product backlog, and lightweight governance; major scope or funding issues might go to a small steering group.
- Scenario 3: Hybrid: predictive for core data and security, adaptive for user-facing features; formal gates for compliance milestones plus regular iteration reviews.
Quiz 1: Life Cycles and Governance Basics
Test your understanding of key distinctions.
A project to build a safety-critical railway control system has stable, fully documented requirements and strict regulatory oversight. Which combination best fits this situation?
- Adaptive life cycle with no formal change control, relying on the product backlog only
- Predictive life cycle with formal phase gates and a change control board
- Hybrid life cycle with only informal approvals and no escalation paths
- Adaptive life cycle with daily decisions made solely by the development team
Show Answer
Answer: B) Predictive life cycle with formal phase gates and a change control board
Stable, safety-critical, and heavily regulated work favors a predictive life cycle where scope, time, and cost are determined early. Governance should include formal phase gates and a change control board to review changes affecting baselines. Options A, C, and D under-govern a high-risk, regulated environment.
Quiz 2: Project vs Product Life Cycle and Governance Roles
Another quick check on subtle distinctions.
Which statement is MOST accurate?
- The project life cycle continues as long as the product is in use.
- In adaptive projects, there is no need for governance because the team self-organizes.
- A steering committee provides strategic decisions and can act as the body that approves passing major phase gates.
- The product life cycle always ends when the project manager hands over the deliverables.
Show Answer
Answer: C) A steering committee provides strategic decisions and can act as the body that approves passing major phase gates.
A steering committee (or project board) provides strategic oversight and often owns go/no-go decisions at major gates. The project life cycle ends when the project is closed, even if the product continues in use. Adaptive projects still require governance, and product life cycles can extend beyond any single project.
Key Term Flashcards: Life Cycles and Governance
Use these flashcards to reinforce core definitions and concepts you must recall quickly on the CAPM exam.
- Project life cycle
- The series of phases that a project goes through from start to finish, typically including concept/initiation, planning, execution with monitoring and controlling, and closure.
- Product life cycle
- The stages a product passes through from initial idea and introduction to the market, through growth and maturity, until its retirement.
- Predictive life cycle (definition)
- 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 (definition)
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- Hybrid life cycle
- A development approach that combines elements of predictive and adaptive life cycles, using each where it fits best.
- Phase gate / stage gate
- A governance point at the end of a phase or major milestone where decision makers review progress and decide to continue, change, pause, or terminate the project.
- Steering committee
- A group of senior stakeholders that provides strategic direction, resolves major issues, and often owns go/no-go decisions at key gates.
- Change control board (CCB)
- A formally chartered group that reviews, approves, defers, or rejects change requests that affect project baselines or major requirements.
- Escalation path
- A predefined route for raising issues or risks that cannot be resolved at the current level of authority.
- Governance in adaptive projects
- Relies on frequent reviews, product owner decisions, and visible backlogs; may still use higher-level gates and steering committees for major decisions.
Putting It All Together: Integration Across the Life Cycle
Integration Across the Life Cycle
The project manager coordinates scope, schedule, cost, quality, resources, and stakeholders across all phases to achieve objectives.
Integration by Approach
Predictive: maintain baselines with formal control. Adaptive: align backlog, iterations, and feedback. Hybrid: balance both styles.
Governance Supports Integration
Phase gates, steering committees, CCBs, and escalation paths provide decision points and support to keep the project aligned with strategy.
CAPM Focus
Be ready to pick the right life cycle, explain its impact on planning and control, and choose appropriate governance mechanisms for a scenario.
Key Terms
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- phase gate
- A governance point at the end of a phase or major milestone where decision makers review progress and decide whether to continue, change, pause, or terminate the project.
- escalation path
- A predefined route for raising issues or risks that cannot be resolved at the current level of authority.
- hybrid life cycle
- A development approach that combines elements of predictive and adaptive life cycles, using each where it is most appropriate.
- product life cycle
- The stages a product passes through from initial idea and introduction to the market, through growth and maturity, until its retirement.
- project governance
- The framework of rules, roles, and decision-making processes that guide project management activities and ensure the project supports organizational strategy.
- project life cycle
- The series of phases that a project goes through from start to finish, typically including concept/initiation, planning, execution with monitoring and controlling, and closure.
- steering committee
- A group of senior stakeholders that provides strategic direction, resolves major issues, and often owns go/no-go decisions at key project gates.
- 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.
- change control board
- A formally chartered group that reviews, approves, defers, or rejects change requests that affect project baselines or major requirements.
- 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.