CAPM Agile Frameworks: Scrum, XP, SAFe, Kanban and the Rest of the 20% Domain

Agile Frameworks/Methodologies is Domain III of the CAPM and carries 20% of the exam, about 27 of the 135 scored questions by Passy's arithmetic. It came in with the 2023 Exam Update, which PMI's 2023 FAQ says expanded the exam to predictive, agile and business analysis principles. PMI's CAPM Examination Content Outline names four methodologies outright, Scrum, Extreme Programming (XP), the Scaled Agile Framework (SAFe) and Kanban, and asks you to tell their components apart, decide when an adaptive approach fits, and plan and track work in iterations.

The five agile tasks in PMI's CAPM outline

The task names are shortened from PMI's outline. The outline also says adaptive approaches appear "throughout the four domain areas," so agile thinking isn't confined to this 20%. A Fundamentals question about a meeting, or a Business Analysis question about requirements, can be set in an agile team. PMI's CAPM Exam Prep page lists the Agile Practice Guide (2017) among its study materials, and it is on the outline's reference list as well.

Adaptive or predictive: the trade-offs the CAPM compares

The outline asks for pros and cons but doesn't list them. This comparison is Passy's summary of how the references generally describe the two:

Organizational process assets are the organization's own policies, templates, historical records and lessons learned. Enterprise environmental factors are the conditions around the project, such as culture, structure, regulations, tools and where people work. Examples that help an adaptive approach, in Passy's words: leaders who accept incremental funding and decisions, policies that allow scope to be managed through a backlog, collaboration tools for a distributed team, retrospective records the team can reuse, and a business representative who can be available often. A policy that requires full requirements sign-off before any build pulls the other way.

Planning CAPM iterations: from a WBS to working increments

A few units come up again and again. An iteration (a sprint, in Scrum) is a fixed-length cycle in which the team delivers a working piece of the product. A release puts one or more increments in users' hands, and it can follow one iteration or several. Scrum even allows an increment to reach stakeholders before the sprint ends. Short iterations bring faster feedback but more planning overhead, and they leave less room for large items. Longer ones reduce overhead but slow feedback down. That is the trade-off behind "interpret the pros and cons of the iteration."

"Translate this WBS to an adaptive iteration" means taking deliverables from a breakdown and turning them into backlog items that can be ordered and delivered in slices. A fictional example, an online course portal:

Iteration 1 already gives users something they can use: sign in and find a course. Each later iteration adds value on top, and feedback from the first release can reorder what comes next. Inputs for scope in adaptive work typically include the product vision, the roadmap, the product backlog, stakeholder feedback, the definition of done and the team's capacity.

Tracking changes with the approach. Plan-based tracking measures progress against a baseline, using variances and percent complete. Adaptive tracking counts finished, working increments, so work that is 90% done counts as not done yet. Velocity, the amount of work a team completes per iteration, then feeds forecasts: remaining work divided by average velocity, best given as a range. That math is quick to drill, and step-by-step velocity math is planned for full CAPM prep along with critical path and variances.

Scrum, XP, SAFe and Kanban: how CAPM questions tell them apart

The outline names the four but doesn't describe them. The summaries below are Passy's plain-language descriptions, checked against each framework's own material: the Scrum Guide (2020), The Kanban Guide (May 2025), the Scaled Agile Framework's Planning Interval page, and Don Wells's ExtremeProgramming.org rules for XP. Check details against those sources if your course differs.

Two contrasts are worth knowing cold. Scrum fixes the timebox and lets the developers pull a sprint's worth of work into it, while Kanban controls how many items are in progress at once, often with a limit per column, and lets work flow. And XP is the one defined by technical practices: if a stem talks about pairs at one keyboard or tests written before code, it points to XP. The outline's "etc." leaves room for others, but these four are the ones it names.

Adaptive artifacts and controls on the CAPM

Task 3 asks you to identify adaptive artifacts. The list and one-line purposes are Passy's:

The difference between acceptance criteria and the definition of done is a classic pair. The CAPM business analysis guide works through it with a release-readiness example.

Success criteria and prioritizing tasks in adaptive work

Task 5 asks you to interpret success criteria and prioritize. An adaptive task succeeds when it meets its acceptance criteria and the team's definition of done, not when the hours run out. For ordering, the usual factors are business value, dependencies, risk and the cost of waiting. Techniques you may see include MoSCoW (must, should, could, won't), simple value-versus-effort comparisons, and, in SAFe, weighted shortest job first.

A fictional backlog for a food bank's volunteer app shows how the factors interact:

A sensible order is sign-up, shift booking, reminders, then badges. Shift booking is worth the most, but it can't work until people can sign up, so the dependency decides the first slot. After that, value takes over.

Original Passy practice: four agile questions

Written by Passy for practice, not PMI items.

1. Midway through a two-week sprint, a stakeholder asks the team to build an urgent new feature. What should happen?

• A. The developers add it to the current sprint right away
• B. The request goes to the product owner, who orders it in the product backlog while the current sprint's goal stays protected
• C. The project manager submits it to the change control board
• D. The team cancels the sprint and starts a new one

Key: B. The product owner orders the backlog, and new work normally waits for a future sprint unless the product owner and team agree it can be absorbed without endangering the sprint goal. A bypasses the product owner, C is the predictive route, and D is a drastic step for an ordinary request. In Scrum, only the product owner can cancel a sprint, and the Scrum Guide ties that to the sprint goal becoming obsolete.

2. Five teams building one product meet every ten weeks for a two-day planning event to align their work for the next several iterations. Which framework does this describe?

• A. Kanban
• B. Extreme Programming
• C. Scaled Agile Framework
• D. Scrum with a single team

Key: C. Several teams on one product, aligned at a large planning event each interval, is SAFe's signature. Kanban has no required iterations, XP is defined by engineering practices, and single-team Scrum doesn't coordinate five teams.

3. A team's chart shows completed work climbing each iteration, while the line for total scope stepped up twice after stakeholders added features. Which chart is it?

• A. Burndown chart
• B. Burnup chart
• C. Gantt chart
• D. Risk register

Key: B. A burnup chart tracks completed work against a separate scope line, so added scope shows as a step up. A burndown shows only remaining work, a Gantt chart is a predictive schedule view, and a risk register isn't a chart.

4. Which condition most supports choosing an adaptive approach?

• A. A policy requiring full requirements sign-off before any work begins
• B. A business representative who can join the team often to clarify and order work
• C. A fixed-price contract with a detailed specification
• D. Funding released only after the complete design is approved

Key: B. Adaptive work depends on frequent input from someone who can decide priorities. A, C and D all assume scope is fixed up front, which favors a plan-based approach.

Framework clues become automatic through repetition on new stems, and practicing agile on its own before mixing it into the 150-question timed mock is how full CAPM prep is planned.

A two-week CAPM agile study block

The CAPM study time guide gives this domain about 13 hours of a 64-hour plan:

The CAPM predictive domain guide is the natural pair for days 9 and 10, because many questions turn on which approach a team is using. Passy's 20 free CAPM practice questions include four agile items, on velocity, Kanban, Scrum events and XP, each with an explanation. For volume later, 440 agile questions and 108 flashcards are planned for full CAPM prep, and checkout isn't open yet.