7.1 When to Use an Adaptive (Agile) Approach

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:

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:

1. Satisfy the customer through early and continuous delivery of valuable product.
2. Welcome changing requirements, even late in development.
3. Deliver working product frequently — weeks, not months.
4. Business and developers work together daily.
5. Build projects around motivated individuals; trust them.
6. Face-to-face conversation is the most efficient communication.
7. Working product is the primary measure of progress.
8. Promote sustainable development at a constant pace.
9. Continuous attention to technical excellence.
10. Simplicity — maximize the work not done.
11. Best designs emerge from self-organizing teams.
12. 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.

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:

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.