7.1 When to Use an Adaptive (Agile) 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

7.1 When to Use an Adaptive (Agile) Approach

Key Takeaways Explain This Topic AI

Agile Frameworks is Domain 3 of the CAPM Exam Content Outline and carries 20% of the 150 scored-and-pretest questions — roughly 30 questions

The Agile Manifesto (2001) states four value pairs and the items on the LEFT are valued more, but the items on the right still have value

The 12 Agile Principles operationalize the Manifesto: early/continuous delivery, welcoming change, frequent working product, and self-organizing teams

Choose adaptive when requirements are uncertain and feedback is frequent; choose predictive when scope is stable, well understood, and change is costly

Hybrid combines both — predictive governance/regulatory documentation around adaptive build cycles; it is now a first-class CAPM topic

Last updated: June 2026

Where Domain 3 Sits on the Exam

The Certified Associate in Project Management (CAPM) exam delivers 150 questions in 180 minutes (135 scored + 15 unscored pretest items) with one 10-minute break after question 75. The Project Management Institute (PMI) Exam Content Outline splits the test into four domains: Project Management Fundamentals (36%), Predictive Methodologies (17%), Agile Frameworks/Methodologies (20%) , and Business Analysis (27%). Twenty percent of the test means roughly 30 questions ride on this chapter, so an adaptive-versus-predictive decision is high-value real estate.

Domain 3, Task 1 asks you to explain when an adaptive approach is appropriate.

The Agile Manifesto (2001)

The Agile Manifesto was authored by 17 practitioners at Snowbird, Utah, in February 2001. It states four value pairs:

We Value... Over...

Individuals and interactions Processes and tools
Working software Comprehensive documentation
Customer collaboration Contract negotiation
Responding to change Following a plan

Exam trap: The Manifesto says, "While there is value in the items on the right, we value the items on the left more." An answer claiming agile teams abandon documentation, contracts, or plans is WRONG. They simply weight the left-hand items higher. CAPM loves to test this nuance with absolute words like "never" or "eliminate."

The 12 Agile Principles

The principles turn the four values into behavior. Memorize the high-frequency ones:

Satisfy the customer through early and continuous delivery of valuable product.

Welcome changing requirements , even late in development.

Deliver working product frequently — weeks, not months.

Business and developers work together daily .

Build projects around motivated individuals ; trust them.

Face-to-face conversation is the most efficient communication.

Working product is the primary measure of progress.

Promote sustainable development at a constant pace.

Continuous attention to technical excellence .

Simplicity — maximize the work not done.

Best designs emerge from self-organizing teams .

Reflect and adjust at regular intervals.

Principles 1, 2, 3, 7, and 11 generate the most exam items. Note Principle 10's wording: agile maximizes work not done , not work done.

When Adaptive Beats Predictive

The Stacey complexity model logic underlies the exam answer: high agreement on requirements + high certainty about technology favors predictive ; low agreement or low certainty favors adaptive .

Factor Lean Adaptive When... Lean Predictive When...

Requirements Volatile, emerging, exploratory Fixed, well understood, contractual
Customer availability Frequent feedback possible Engaged only at gates/sign-off
Change cost Low and expected High and disruptive
Delivery value Incremental value adds up Value realized only at the end
Risk/uncertainty High technical or market risk Low, repeatable, proven solution
Worked scenario

A bank must reissue 2 million cards on a fixed compliance deadline using a proven, fully specified card-print process. Requirements are stable, the process is repeatable, and the deadline is regulatory — this is a predictive project. Now change it to a startup building a never-built mobile budgeting feature with weekly user testing : uncertain requirements and constant feedback make it adaptive . CAPM scenario items reward matching the driver (uncertainty vs. stability) to the approach.

Hybrid Approaches

Hybrid blends predictive and adaptive elements and is now explicitly examined.

Predictive front/back, adaptive middle: stage-gate funding and a fixed go-live wrap iterative build sprints.

Feature-based split: stable features predictive; uncertain features iterative.

Water-Scrum-Fall: upfront requirements/planning, Scrum delivery, predictive release.

Use hybrid when part of the work is stable and part is uncertain, when regulators demand documentation while engineering benefits from iteration, or when an organization is mid-transition to agile.

Organizational Enablers

Agile is an organizational commitment, not a team trick:

Enabler Why It Matters
Executive support Funds the change and protects the team
Empowered, cross-functional team Decides how , owns all needed skills
Dedicated product owner Prioritizes and gives fast feedback
Psychological safety Enables experimentation and learning from failure
Collaboration tooling/co-location Sustains daily, close interaction

If the question describes a rigid, command-and-control culture with no customer access, the safest answer is that the environment is not yet ready for pure agile — recommend hybrid or culture change rather than forcing Scrum.

Predictive, Iterative, Incremental, and Adaptive

The exam distinguishes four life cycle types, and mixing them up is a classic mistake. A predictive (waterfall) life cycle fixes scope, schedule, and cost early and delivers once at the end. An iterative life cycle repeats cycles to refine a single deliverable through successive approximation — think of redrawing a design until it is right. An incremental life cycle delivers finished, usable pieces one at a time, each adding to the whole. An adaptive (agile) life cycle is both iterative and incremental and embraces changing requirements throughout.

CAPM may show a scenario and ask which life cycle it describes: "deliver a working slice every two weeks and refine based on feedback" is adaptive; "build the entire system, then deliver once" is predictive.

The Cost and Schedule of Change

A core reason to choose adaptive is the cost-of-change curve . In predictive projects the cost to change a requirement rises steeply the later it is discovered, because downstream design, build, and test work must be reworked. Agile flattens that curve by keeping increments small, integrating continuously, and re-deciding priorities every Sprint, so a late change costs roughly the same as an early one. When a scenario stresses frequent, unavoidable change , the lower cost-of-change of adaptive approaches is the deciding factor the exam wants you to cite.

Conversely, when change is genuinely rare and expensive to accommodate, predictive planning protects the budget and timeline better.