Agile on the CAPM: The 20% Domain in Depth

The Agile Frameworks domain is 20% of the current CAPM exam, or about 30 of the 150 questions. Most candidates either overestimate what it tests (and spend weeks on Scrum Master certification-level depth) or underestimate it (and lose every agile question on test day).

The reality is narrower. The domain tests the fundamentals of agile frameworks, how to recognize which framework fits a situation, and when to choose agile over predictive. It does not test Scrum Master-level facilitation, coaching patterns, or scaling-framework specifics.

This post covers what the domain actually asks.

What the domain covers

The CAPM Agile Frameworks domain covers:

• Core agile concepts: iterative delivery, incremental value, adaptive planning, continuous improvement.
• Scrum roles, ceremonies, and artifacts.
• Kanban basics: WIP limits, flow, pull systems.
• Extreme Programming (XP) practices: pair programming, test-driven development, continuous integration, refactoring.
• Hybrid approaches that combine predictive and adaptive elements.
• When to choose agile over predictive, and vice versa.

Anything outside that list (SAFe specifics, LeSS, Nexus, Scrum-of-Scrums patterns) is not on the CAPM.

Scrum, in the depth the exam expects

The three roles:

• Product Owner. Owns the product backlog. Prioritizes items. Defines what “done” means for each item. Represents the stakeholder voice on the team.
• Scrum Master. Facilitates the team’s process. Removes impediments. Protects the team from scope creep and external interruptions. Is not the team’s manager.
• Development Team. Cross-functional group that does the work. Self-organizing. Typically three to nine people. Decides how to deliver committed backlog items within the sprint.

The four ceremonies (events inside a sprint):

• Sprint Planning. The team selects items from the product backlog for the upcoming sprint and creates a sprint backlog. Time-boxed to about two hours per week of sprint length (so four hours for a two-week sprint).
• Daily Standup (Daily Scrum). 15 minutes, same time each day. The team synchronizes on what they did yesterday, what they’ll do today, and what’s blocking them.
• Sprint Review. At the end of the sprint. The team demonstrates what was built to stakeholders and gathers feedback. Time-boxed to roughly one hour per week of sprint length.
• Sprint Retrospective. After the review. The team discusses what went well, what didn’t, and what to change next sprint. Time-boxed to roughly 45 minutes per week of sprint length.

The three artifacts:

• Product Backlog. An ordered list of everything the team might build. Maintained by the Product Owner.
• Sprint Backlog. The subset committed to for the current sprint, plus the plan for delivering it.
• Increment. The sum of all completed product backlog items as of the end of the sprint. Must meet the team’s definition of done.

Scenario questions typically combine these in realistic situations. “A Product Owner adds a high-priority item mid-sprint” is a ceremony-boundary question. “The Scrum Master facilitates a retrospective where one team member blames another for missed work” is a role-and-facilitation question.

Kanban, Extreme Programming, and hybrid

The exam treats these at a lighter depth than Scrum, but still expects recognition.

Kanban. A pull-based system with visual work boards, explicit WIP (work in progress) limits, and continuous flow. No fixed-length iterations. Teams pull the next item when they have capacity. Well-suited to operations and support work where new items arrive unpredictably.

Extreme Programming (XP). A software-development-specific agile framework with strong technical practices: pair programming, test-driven development, continuous integration, refactoring, small frequent releases. The CAPM may ask about any of these by name.

Hybrid. Combines predictive and adaptive elements. Common in regulated industries where predictive planning is required upstream (for compliance) but execution benefits from agile sprints. Scenario questions often describe mixed environments and ask which elements to keep predictive and which to make adaptive.

Choosing agile over predictive

Most agile scenario questions reduce to a choice: agile, predictive, or hybrid. The stems usually signal which by describing:

• The environment. Rapidly changing requirements, exploratory work, or emergent scope push toward agile. Stable requirements, regulated industries, and fixed-price contracts push toward predictive.
• The stakeholders. Stakeholders who want to inspect progress and adapt push toward agile. Stakeholders who want commitments locked early push toward predictive.
• The deliverable. Software, digital products, and service iterations suit agile. Construction, heavy manufacturing, and infrastructure projects suit predictive.
• The team. Co-located, cross-functional, self-organizing teams suit agile. Distributed, specialist-heavy, command-and-control environments struggle with it.

When a question describes a scenario that looks mixed, “hybrid” is often the intended answer.

Common question patterns

Four patterns cover most CAPM agile questions.

Role confusion. A team member does something that properly belongs to another role. The right answer is usually the role-appropriate action. A Scrum Master does not reprioritize the backlog; a Product Owner does not assign work to developers.

Ceremony misuse. A ceremony is proposed for a purpose it doesn’t serve. A retrospective is not for stakeholder demos. A sprint review is not for team process improvement. The right answer fixes the mismatch.

Artifact scope. A question asks what lives in the product backlog versus the sprint backlog, or what meets the definition of done.

Framework selection. A scenario describes a project and asks whether to use Scrum, Kanban, XP, hybrid, or predictive. The environmental signals above are how you pick.

What to skip

The CAPM does not test:

• SAFe, LeSS, Nexus, or any scaling framework beyond basic acknowledgment that they exist.
• Coaching or facilitation techniques at Scrum Master certification depth.
• Specific agile metrics beyond velocity, burndown, and cumulative flow.
• Detailed estimation techniques (planning poker, story points) at ceremony-facilitation depth.

If your study material spends a full chapter on SAFe, it’s over-preparing you for the CAPM.

Our CAPM Study Guide and Exam Prep 2026 covers the agile domain at the depth the current exam tests, not the depth a Scrum Master certification would require.