Study guide
2.2 Project Life Cycle Phases
CAPM Certified Associate in Project Management Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & CAPM Exam Overview
1.1 About the CAPM Exam 1.2 PMBOK 7th Edition Overview 1.3 Exam Content Outline (ECO) 1.4 CAPM vs. PMP: Understanding the Differences
2 Chapter 2: Project Life Cycles and Processes (Domain 1, Tasks 1-2)
2.1 Projects, Programs, and Portfolios 2.2 Project Life Cycle Phases 2.3 The Five Process Groups 2.4 The Ten Knowledge Areas
3 Chapter 3: Project Management Planning (Domain 1, Task 2)
3.1 The Project Management Plan 3.2 Scope Management and the WBS 3.3 Schedule Management 3.4 Cost Management and Earned Value 3.5 Quality Management
4 Chapter 4: Project Roles, Responsibilities, and Ethics (Domain 1, Tasks 3-4)
4.1 Project Roles and Responsibilities 4.2 Leadership and Emotional Intelligence 4.3 Risk Management Fundamentals 4.4 PMI Code of Ethics and Professional Conduct 4.5 Problem-Solving Tools and Techniques
5 Chapter 5: Resource, Communication, and Stakeholder Management (Domain 1, Tasks 2-3)
5.1 Resource Management 5.2 Communications Management 5.3 Stakeholder Management 5.4 Procurement Management 5.5 Issues, Risks, Assumptions, and Constraints
6 Chapter 6: Predictive, Plan-Based Methodologies (Domain 2)
6.1 When to Use a Predictive Approach 6.2 WBS, Work Packages, and Activity Definition 6.3 Predictive Project Controls and Artifacts 6.4 Critical Path and Schedule Calculations
7 Chapter 7: Agile Frameworks and Methodologies (Domain 3, Tasks 1-3)
7.1 When to Use an Adaptive (Agile) Approach 7.2 The Scrum Framework 7.3 Kanban, XP, and SAFe 7.4 Agile Planning, Estimation, and Metrics 7.5 Agile Project Controls and Artifacts
8 Chapter 8: Business Analysis Roles and Stakeholder Communication (Domain 4, Tasks 1-2)
8.1 Business Analysis Roles and Responsibilities 8.2 Stakeholder Communication in Business Analysis 8.3 Business Case and Needs Assessment
9 Chapter 9: Requirements Gathering and Product Roadmaps (Domain 4, Tasks 3-4)
9.1 Requirements Gathering Approaches 9.2 Requirements Traceability Matrix 9.3 Product Roadmaps
10 Chapter 10: BA Methodologies and Requirements Validation (Domain 4, Tasks 5-6)
10.1 Business Analysis in Predictive and Agile Approaches 10.2 Acceptance Criteria and Requirements Validation 10.3 Business Analysis Tools and Techniques Summary
2.2 Project Life Cycle Phases
Key Takeaways Explain This Topic AI
A project life cycle is the series of phases a project passes through; phase relationships can be sequential, overlapping (fast-tracking), or iterative
Cost and staffing start low, peak during execution, and fall sharply during closing — a bell-shaped curve
Risk/uncertainty and stakeholder influence are HIGHEST at the start and decrease over time; the cost of changes is LOWEST at the start and rises steeply
A phase gate is an end-of-phase review producing a go / go-with-modifications / hold / kill decision
Predictive (waterfall) life cycles plan in detail up front; adaptive (agile) life cycles use short iterations and welcome change
Last updated: June 2026
The Project Life Cycle
A project life cycle is the series of phases a project passes through from start to finish. Phases give structure: each has a focus, deliverables, and usually a review before the next begins. While industries differ, PMI describes a generic four-phase pattern you should recognize on the exam.
- Generic phase Primary work Key deliverables
- Starting the project Establish purpose, feasibility, high-level scope Project charter, stakeholder register
- Organizing and preparing Build detailed plans and team Project management plan, WBS, baselines
- Carrying out the work Execute the plan, produce deliverables Deliverables, work performance data
- Ending the project Verify, hand off, archive Final product, lessons learned, sign-off
- Phase Relationships
Sequential — a phase starts only after the prior phase finishes. Lowest risk, longest duration. Example: regulatory design fully approved before construction begins.
Overlapping (fast-tracking) — a later phase starts before the prior one finishes to compress the schedule. This raises risk and rework because later work proceeds on incomplete information.
Iterative/incremental — phases repeat in cycles, each refining the deliverable; common in adaptive (agile) work.
Trap: Fast-tracking (overlapping phases or activities) is often confused with crashing (adding resources to shorten duration). Fast-tracking adds risk , not cost; crashing adds cost , not necessarily risk.
Phase Gates
A phase gate is a review held at the end of a phase to decide whether the project should proceed. PMI also calls these stage gates, kill points, decision points, phase reviews, or toll gates. The reviewer (often a sponsor or governance board) chooses one of these outcomes:
- Decision Meaning
- Go Proceed to the next phase as planned
- Go with modifications Proceed after adjusting scope, budget, or schedule
- Hold Stay in the current phase for more analysis or rework
- Kill / terminate End the project; sunk costs are not a reason to continue
- How Project Variables Change Over the Life Cycle
This is the most heavily tested life-cycle concept. Commit the four curves to memory:
Cost and staffing — start low, build through planning, peak during execution , then drop sharply in closing (a bell curve).
Risk and uncertainty — highest at the start (most unknowns) and decline as decisions are locked in and work is completed.
Stakeholder influence over the product — highest at the start , declining as decisions are made and become costly to reverse.
Cost of making changes — lowest at the start , rising steeply as work is built; a change in execution costs far more than the same change in planning.
Critical relationship: Stakeholder influence and the cost of changes are inversely related . Early on, stakeholders have maximum influence and changes are cheap; late in the project, changes are expensive and influence is low. CAPM questions love this inverse pairing.
A quick worked scenario: a sponsor wants to add a feature. If the team is still in planning, scope is updated at low cost. If the team is mid-build, the change triggers rework, retesting, and schedule impact — sometimes 10x the planning-stage cost. The principle (cost of change rises over time) is what the exam is testing, not a specific multiplier.
Predictive vs. Adaptive Life Cycles
The CAPM allocates 17% to Predictive Methodologies and 20% to Agile Frameworks, so this contrast is essential. A predictive (waterfall) life cycle defines scope, schedule, and cost early and controls change formally. An adaptive (agile) life cycle delivers in short iterations, refining requirements continuously and welcoming change. A hybrid blends both.
- Characteristic Predictive Adaptive (Agile)
- Planning Detailed up front Progressive, just-in-time
- Requirements Fixed early, stable Evolving, refined each iteration
- Delivery Single delivery near the end Incremental, frequent
- Change Controlled via formal change process Expected and welcomed
- Feedback At phase gates Continuous, each iteration
- Best for Well-understood, low-change work High-uncertainty, evolving needs
Rule of thumb for scenario items: stable, well-defined requirements → predictive; high uncertainty or rapidly changing needs → adaptive.
The Development Approach Continuum
The CAPM tests a spectrum of development approaches, not a binary. From most plan-driven to most change-driven:
- Approach Requirements Delivery cadence When to use
- Predictive Fixed early One delivery at the end Requirements clear and stable
Iterative Refined through repeated cycles One delivery, improved each cycle Requirements known but solution unclear
- Incremental Defined in slices Many usable increments Value needed early and often
- Adaptive (Agile) Evolve continuously Frequent increments + iteration High change and uncertainty
- Hybrid Mix of fixed and evolving Mix Different components need different handling
Iterative improves one deliverable through repeated passes (refining a prototype); incremental builds the deliverable in usable pieces (ship feature 1, then 2). Agile combines both.
Phases vs. the Life Cycle vs. Cadence
Keep three terms distinct on the exam. A phase is a collection of logically related activities ending in one or more deliverables. The life cycle is the full series of phases. Delivery cadence is how often you release value (single, multiple, or periodic). A predictive life cycle usually has phases like requirements, design, build, test, deploy — with a single delivery cadence. An adaptive life cycle has short repeating iterations with a periodic delivery cadence. CAPM scenario items frequently combine these terms, so read carefully whether a question asks about phase structure, the overall life cycle, or how often value ships.
Trap: "Predictive" is not a synonym for "sequential phases." A predictive project can still overlap phases via fast-tracking. The predictive/adaptive distinction is about how requirements and change are handled, while the sequential/overlapping/iterative distinction is about how phases relate in time. Do not collapse the two axes.