Overview
Agile Frameworks and Methodologies is 20% of the CAPM exam, covering the adaptive side of project management, which PMI now weights heavily alongside predictive. It has five tasks. Explaining when to use an adaptive approach covers comparing the pros and cons of adaptive versus predictive, suitability for organizational structures, and the factors that facilitate adaptive approaches. Planning iterations covers logical units of iterations, their pros and cons, translating a work breakdown structure to adaptive iterations, scope inputs, and adaptive versus predictive tracking. Documenting controls covers identifying adaptive artifacts. The components of an adaptive plan cover distinguishing methodologies such as Scrum, Extreme Programming, SAFe and Kanban. Task management covers interpreting success criteria and prioritizing tasks.
The exam rewards knowing when adaptive fits, how iterations and backlogs work, the main agile frameworks and their differences, and how adaptive tracking and prioritization differ from predictive. These agile fundamentals complement Domain 2 and reflect the modern, hybrid reality of project work.
How it's tested
CAPM questions in this domain describe an adaptive project situation and ask when adaptive fits, how iterations work, which framework applies, or how to track and prioritize. CAPM questions test understanding of fundamentals through knowledge and short scenario items, so read for the precise concept or technique being tested and choose the textbook-correct answer.
-
When to use adaptive
A project is described, and you judge whether an adaptive approach fits over predictive.
-
Iterations and artifacts
An adaptive delivery need is described, and you apply iterations, backlogs or adaptive artifacts.
-
Framework and task management
A methodology or task need is described, and you identify the agile framework or prioritize the work.
A product team faces rapidly changing requirements and wants to deliver working features in short cycles, getting customer feedback each cycle to decide what to build next. This favors an adaptive approach, which delivers in iterations and reprioritizes the backlog based on feedback, over a predictive approach that fixes scope upfront. Recognizing that changing requirements and a desire for frequent feedback point to adaptive delivery is the judgment the exam expects.
Domains 5
Official domains from the PMI outline, in outline order.
3.1 Explain when it is appropriate to use an adaptive approachAdaptive versus predictive, suitability, and facilitating factors.
- What it means
- This covers comparing the pros and cons of adaptive and predictive, plan-based projects, identifying the suitability of adaptive approaches for different organizational structures, and identifying the organizational process assets and enterprise environmental factors that facilitate adaptive approaches.
- What to understand
- Adaptive approaches suit projects with uncertain, evolving requirements where early and frequent delivery and feedback add value, trading upfront certainty for flexibility. The organizational culture and support, such as empowered teams, facilitate agile. Knowing when adaptive beats predictive, and what the organization needs to support it, is the core judgment.
- How it shows up
- A project's characteristics are described, and you must judge whether an adaptive approach is appropriate.
- Common confusion
- Choosing adaptive for stable, well-defined requirements where predictive fits better.
3.2 Determine how to plan project iterationsIterations, their pros and cons, scope, and adaptive tracking.
- What it means
- This covers distinguishing the logical units of iterations, interpreting the pros and cons of iterations, translating a work breakdown structure to an adaptive iteration, determining inputs for scope, and explaining the importance of adaptive project tracking versus predictive, plan-based tracking.
- What to understand
- Adaptive work is delivered in iterations (such as sprints), each producing a working increment. Scope comes from a prioritized backlog rather than a fixed plan, and progress is tracked with tools like burndown charts and velocity rather than against a fixed baseline. Understanding how iterations are planned and tracked is central to agile delivery.
- How it shows up
- An iteration planning or tracking need is described, and you must apply iterations, backlog scope, or adaptive tracking.
- Common confusion
- Applying predictive, baseline-based tracking to an adaptive project instead of iteration-based tracking.
3.3 Determine how to document project controls for an adaptive projectAdaptive artifacts.
- What it means
- This covers identifying the artifacts used in adaptive projects, such as product and sprint backlogs, burndown and burnup charts, task boards and increments, which document and control adaptive work.
- What to understand
- Adaptive projects use different artifacts from predictive ones: a product backlog of prioritized work, a sprint backlog for the current iteration, burndown or burnup charts to show progress, and task boards to visualize flow. Knowing the adaptive artifacts and what each shows is the control knowledge expected.
- How it shows up
- An adaptive control or tracking need is described, and you must identify the correct adaptive artifact.
- Common confusion
- Confusing adaptive artifacts such as a product backlog with a sprint backlog, or with predictive baselines.
3.4 Explain the components of an adaptive planDistinguishing Scrum, XP, SAFe and Kanban.
- What it means
- This covers distinguishing between the components of different adaptive methodologies, such as Scrum, Extreme Programming (XP), the Scaled Agile Framework (SAFe) and Kanban, and their characteristics.
- What to understand
- The main agile frameworks differ: Scrum uses fixed-length sprints, defined roles and ceremonies; Extreme Programming emphasizes engineering practices; Kanban focuses on continuous flow and limiting work in progress; and SAFe scales agile across large organizations. Recognizing each framework and its distinguishing components is the expected knowledge.
- How it shows up
- A methodology is described, and you must identify the agile framework by its components.
- Common confusion
- Confusing the frameworks, such as Scrum (sprints and roles) with Kanban (continuous flow and WIP limits).
3.5 Determine how to prepare and execute task management stepsSuccess criteria and prioritizing tasks.
- What it means
- This covers interpreting the success criteria of an adaptive project management task and prioritizing tasks in adaptive project management, typically from a prioritized backlog.
- What to understand
- In adaptive work, tasks are prioritized by value, usually from the top of the backlog, and success criteria define when work is done, such as acceptance criteria or a definition of done. The team pulls the highest-priority work and completes it to the agreed criteria. Understanding prioritization and success criteria is the task-management skill.
- How it shows up
- A task prioritization or completion situation is described, and you must choose how to prioritize or judge success.
- Common confusion
- Prioritizing tasks by order received rather than by value from the backlog.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Adaptive approach
Iterative delivery with feedback.
- Remember
- Suits evolving requirements.
- Tested as
- Approach questions.
- Trap
- Using it for stable scope.
-
Iteration (sprint)
A short cycle producing an increment.
- Remember
- Delivers working value regularly.
- Tested as
- Iteration questions.
- Trap
- Treating it as a mini waterfall.
-
Product backlog
Prioritized list of all work.
- Remember
- Scope comes from the backlog.
- Tested as
- Artifact questions.
- Trap
- Confusing with a sprint backlog.
-
Sprint backlog
Work selected for the current iteration.
- Remember
- A subset of the product backlog.
- Tested as
- Artifact questions.
- Trap
- Confusing with the product backlog.
-
Burndown chart
Shows remaining work over time.
- Remember
- Tracks iteration progress.
- Tested as
- Tracking questions.
- Trap
- Confusing with predictive tracking.
-
Adaptive vs. predictive tracking
Iteration progress versus baseline variance.
- Remember
- Agile tracks differently.
- Tested as
- Tracking questions.
- Trap
- Applying baseline tracking to agile.
-
Scrum
Sprints, roles and ceremonies.
- Remember
- Fixed-length iterations.
- Tested as
- Framework questions.
- Trap
- Confusing with Kanban.
-
Kanban
Continuous flow with WIP limits.
- Remember
- Visualize and limit work.
- Tested as
- Framework questions.
- Trap
- Confusing with Scrum.
-
Extreme Programming
Engineering-practice focused agile.
- Remember
- Emphasizes technical practices.
- Tested as
- Framework questions.
- Trap
- Confusing with Scrum.
-
SAFe
Scales agile across the enterprise.
- Remember
- For large organizations.
- Tested as
- Framework questions.
- Trap
- Confusing with team-level Scrum.
-
Backlog prioritization
Ordering work by value.
- Remember
- Pull the highest-value work first.
- Tested as
- Task questions.
- Trap
- Prioritizing by order received.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Adaptive vs. predictive
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Adaptive | Iterate with feedback | Evolving requirements | Using for stable scope |
| Predictive | Plan upfront | Stable requirements | Using for uncertain work |
Scrum vs. Kanban
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Scrum | Fixed sprints, roles, ceremonies | Time-boxed iterations | Confusing with Kanban |
| Kanban | Continuous flow, WIP limits | No fixed iterations | Confusing with Scrum |
Product vs. sprint backlog
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Product backlog | All prioritized work | The full scope | Confusing with sprint backlog |
| Sprint backlog | Work for one iteration | A selected subset | Confusing with product backlog |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Adaptive for stable scope
- What candidates pick
- Recommend an adaptive approach for a project with fixed, well-defined requirements.
- Why it looks right
- Agile is popular.
- Why it's wrong
- Stable, well-defined requirements suit a predictive approach; adaptive fits evolving, uncertain requirements.
Clue to watch for Requirements are fixed and well understood.
-
Scrum is Kanban
- What candidates pick
- Describe a continuous-flow, WIP-limited method as Scrum.
- Why it looks right
- Both are agile.
- Why it's wrong
- Scrum uses fixed-length sprints with defined roles and ceremonies; Kanban is continuous flow with work-in-progress limits and no fixed iterations.
Clue to watch for The method uses continuous flow versus time-boxed sprints.
-
Baseline tracking in agile
- What candidates pick
- Track an adaptive project against a fixed upfront baseline with variance.
- Why it looks right
- Baselines are familiar.
- Why it's wrong
- Adaptive projects track with iteration tools like burndown charts and velocity, not fixed-baseline variance.
Clue to watch for The project is adaptive and scope evolves.
-
Product backlog is sprint backlog
- What candidates pick
- Treat the product backlog and sprint backlog as the same.
- Why it looks right
- Both are backlogs.
- Why it's wrong
- The product backlog holds all prioritized work; the sprint backlog is the subset selected for the current iteration.
Clue to watch for The need is all work versus one iteration's work.
-
Prioritize by order received
- What candidates pick
- Work tasks in the order they arrived rather than by value.
- Why it looks right
- First come, first served seems fair.
- Why it's wrong
- Adaptive work is prioritized by value from the backlog, delivering the highest-value work first.
Clue to watch for Work should be sequenced by value, not arrival.
Answer framework
For any Domain 3 scenario, use these steps to find the answer the CAPM expects.
- Judge whether the project suits an adaptive approach: evolving, uncertain requirements and a need for frequent feedback favor adaptive over predictive.
- Plan work in iterations, drawing scope from a prioritized backlog and tracking with iteration tools rather than a fixed baseline.
- Use adaptive artifacts such as product and sprint backlogs and burndown charts to document and control the work.
- Identify the agile framework by its components, distinguishing Scrum, Kanban, Extreme Programming and SAFe.
- Prioritize tasks by value from the backlog and complete them to the agreed success criteria or definition of done. Where two options seem to fit, choose the one that most precisely matches the textbook definition the question is testing.
Practice question
Want more like this? The CAPM practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Approach this domain as the adaptive counterpart to predictive, and learn when and how agile applies. Start with judging when adaptive fits: evolving, uncertain requirements and a need for frequent feedback favor adaptive, while stable requirements favor predictive. Then learn how iterations work, with scope from a prioritized backlog and progress tracked by burndown charts and velocity rather than a fixed baseline.
Learn the main agile frameworks and keep them distinct: Scrum (sprints, roles, ceremonies), Kanban (continuous flow, WIP limits), Extreme Programming (engineering practices) and SAFe (scaling). Learn the adaptive artifacts, distinguishing the product backlog from the sprint backlog, and how tasks are prioritized by value with success criteria or a definition of done.
Since the CAPM is a knowledge exam, flashcards on the frameworks and artifacts and practice questions are highly effective. Because the CAPM is a knowledge exam for entry-level candidates, flashcards on the key definitions and plenty of practice questions are highly effective, and reviewing missed questions by domain shows where to focus. Afterwards, move to Domain 4, Business Analysis Frameworks.
FAQ
How much of the CAPM is Domain 3?
Agile Frameworks and Methodologies is 20% of the exam, reflecting how central adaptive approaches now are to project work.
When is an adaptive approach appropriate?
When requirements are uncertain or likely to evolve and the project benefits from delivering working increments early and gathering frequent feedback. Stable, well-defined requirements favor a predictive approach instead.
What is the difference between a product backlog and a sprint backlog?
The product backlog is the full, prioritized list of all work for the product. The sprint backlog is the subset of items the team has selected to complete in the current iteration.
What is the difference between Scrum and Kanban?
Scrum organizes work into fixed-length sprints with defined roles and ceremonies. Kanban uses continuous flow with work-in-progress limits and no fixed iterations, visualizing work on a board.
How is progress tracked in adaptive projects?
With iteration-based tools such as burndown charts (remaining work over time), burnup charts and velocity, rather than variance against a fixed upfront baseline as in predictive projects.
How are tasks prioritized in agile?
By value, usually from the top of the prioritized backlog, so the team delivers the highest-value work first, and each item is completed to its acceptance criteria or the definition of done.
How does Domain 3 connect to the rest of the exam?
It applies the Domain 1 fundamentals to adaptive delivery, contrasts with the predictive methods of Domain 2, and relates to the backlog and requirements concepts in the Domain 4 business analysis content.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- CompTIA Project+ Study guide
- PRINCE2 7 Foundation Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 3 knowledge
You have covered when to use adaptive, iterations, agile frameworks, artifacts and task management. Test whether you can apply agile fundamentals under exam conditions.