6.1 When to Use a Predictive Approach

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

6.1 When to Use a Predictive Approach

Key Takeaways Explain This Topic AI

Predictive (waterfall) approaches fit best when requirements are well-defined, stable, and unlikely to change, and the technology is proven

Domain 2 (Predictive, Plan-Based Methodologies) is 17% of the 150-question CAPM exam, so roughly 23-26 scored items test this material

High regulatory, compliance, and fixed-price-contract environments favor predictive because scope must be defined and documented up front

The Stacey Complexity Model maps requirements certainty against technology certainty to recommend predictive, hybrid, or adaptive approaches

Predictive trades flexibility for predictability: clear milestones and easy cost/schedule estimation, but late feedback and inflexibility to change

Last updated: June 2026

Where This Fits on the Exam

The CAPM exam, updated in July 2023, is built on a four-domain Exam Content Outline (ECO) : Project Management Fundamentals (36%), Predictive, Plan-Based Methodologies (17%) , Agile Frameworks/Methodologies (20%), and Business Analysis Frameworks (27%). You sit 150 questions (135 scored plus 15 unscored pretest items) in 3 hours, split into two 75-question sections by a scheduled ~10-minute break (you cannot revisit the first 75 once you pass it).

Because Domain 2 is 17% of scored content, expect roughly 23 questions drawn from this chapter — so judgment about when predictive fits, plus the schedule mechanics later in the chapter, are high-value.

The predictive approach — also called waterfall or traditional — moves through largely sequential phases, each substantially complete before the next begins, with formal phase-gate reviews between them: Requirements -> Design -> Build -> Test -> Deploy -> Close

When Predictive Works Best

Predictive is the right call when you can define what you are building before you start building it. The exam frames this through stable requirements, low uncertainty, and a need for documentation.

Factor Predictive is appropriate when...

Requirements Well-defined, documented, and stable from the start
Scope Fixed and unlikely to change significantly
Technology Proven, well-understood, low technical risk
Uncertainty Low — few unknowns about what or how
Regulations High compliance demands extensive documentation and traceability
Contracts Fixed-price, where scope must be defined and priced up front
Stakeholders Prefer defined milestones, deliverables, and a single final handover
When predictive is the wrong fit
Requirements are unclear, evolving, or expected to change frequently
The product has never been built before (high innovation/discovery)
Technology is new or unproven, creating high technical uncertainty
Early and continuous customer feedback is essential to success
Time-to-market is critical and incremental delivery adds value sooner

Common trap: Candidates pick "predictive" simply because a project is large or expensive. Size is not the deciding factor — stability of requirements and certainty of technology are. A large, well-understood construction project is predictive; a large, exploratory R&D project is not.

The Stacey Complexity Model

The Stacey Complexity Model (Stacey Matrix) helps choose an approach by plotting how clear the requirements are against how certain the technology/how is.

Requirements CLEAR Requirements UNCLEAR
Technology CERTAIN Simple -> Predictive Complicated -> Hybrid
Technology UNCERTAIN Complicated -> Hybrid Complex/Chaotic -> Adaptive (Agile)
Simple (clear + certain): use predictive
Complicated (uncertainty in one dimension): often hybrid
Complex (uncertainty in both): use adaptive , embracing change through iteration
Chaotic (extreme uncertainty): adaptive with rapid experimentation
Organizational Structure Fit

Predictive aligns naturally with hierarchical, plan-driven cultures.

Structure Fit Why
Functional High Hierarchical control, specialized resource pools
Weak matrix Moderate-High Functional managers keep authority
Balanced/Strong matrix Moderate Shared or PM authority works in structured work
Projectized Moderate Full PM control, but less needed when scope is stable
Advantages vs. Limitations

Advantages Limitations
Clear structure and defined milestones Inflexible once baselines are set
Cost and schedule are easier to estimate Issues surface late (testing is near the end)
Comprehensive documentation for compliance Customer sees the product only at delivery
Works well with fixed-price contracts Assumes requirements are complete and correct
Straightforward progress measurement Long cycles before value is realized

Worked scenario: A bank must rebuild a regulatory reporting system to a published government specification by a hard statutory deadline, under a fixed-price vendor contract. Requirements are dictated by regulation (clear) and the reporting technology is mature (certain). On the Stacey Matrix this is simple , so the exam-correct answer is a predictive approach with strong documentation and change control — not agile experimentation.

Development Life Cycles to Recognize

The CAPM distinguishes several life cycles, and Domain 2 questions often ask you to name the predictive end of the spectrum versus its neighbors.

Life cycle Scope Delivery Change
Predictive Fixed early Once, at the end Restricted, via change control
Iterative Dynamic Refines in repeated cycles Expected between iterations
Incremental Dynamic Delivers usable pieces over time Expected each increment
Adaptive (agile) Dynamic Frequent small increments Embraced continuously
Hybrid Mixed Combines predictive + adaptive Phase-dependent

A predictive life cycle determines scope, time, and cost in the early phases, which is exactly why it depends on requirements being knowable up front. If the exam describes a project that delivers its full product in a single release after sequential phases, that is the predictive (waterfall) life cycle. If it describes building and shipping usable slices over time, that is incremental — a frequent distractor.