Try 10 focused CAPM questions on Agile Frameworks/Methodologies, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | CAPM |
| Topic area | Agile Frameworks/Methodologies |
| Blueprint weight | 20% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Agile Frameworks/Methodologies for CAPM. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 20% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Agile Frameworks/Methodologies
An agile team is planning the next 2-week iteration. Based on past performance, the team’s capacity is 30 story points. The team also agreed to a WIP limit of 2 items in the “In Progress” column.
One item is mandatory this iteration: SEC-1.
Exhibit: Top of product backlog
| ID | Story points | Business value |
|---|---|---|
| SEC-1 Security vulnerability fix (mandatory) | 8 | 80 |
| AUTH-2 Single sign-on (SSO) | 13 | 100 |
| SRCH-3 Advanced search filters | 8 | 70 |
| RPT-4 Export report to CSV | 5 | 25 |
| TECH-5 Refactor notification service | 13 | 35 |
| UI-6 Mobile UI polish | 3 | 15 |
Which iteration plan best maximizes delivered value while respecting capacity and the WIP limit?
Best answer: D
What this tests: Agile Frameworks/Methodologies
Explanation: Iteration selection should maximize value while staying within the team’s capacity and honoring the WIP limit. Choosing SEC-1, AUTH-2, and SRCH-3 totals 29 story points and delivers the highest combined business value among the feasible choices. The WIP limit is satisfied by pulling work so no more than two items are in progress at once.
In adaptive planning, the team selects a set of backlog items that it can realistically finish in the iteration (capacity) and then manages flow during execution by limiting how many items are started at once (WIP). Here, SEC-1 is mandatory, and the capacity is 30 story points.
A value-optimizing, constraint-respecting selection is:
SEC-1 (8) + AUTH-2 (13) + SRCH-3 (8) = 29 points and maximizes delivered value while still allowing execution within a two-item WIP policy.
This set includes the mandatory item, fits within 30 points, and delivers the highest value while managing flow with a two-item WIP limit.
Topic: Agile Frameworks/Methodologies
A project team is delivering a new customer portal using an agile approach. During each iteration review, a key customer representative attends, gives feedback on the working product increment, and the team immediately reorders the backlog to incorporate the most valuable changes—even when this alters the original plan.
Which agile principle is BEST demonstrated by this practice?
Best answer: A
What this tests: Agile Frameworks/Methodologies
Explanation: The scenario emphasizes continuous involvement of a customer representative and using feedback on a working increment to reprioritize work. This directly reflects agile’s focus on close customer collaboration and adapting plans when new information emerges. Changing the backlog based on feedback is a practical example of responding to change.
Agile promotes delivering value through frequent feedback and adjustment rather than trying to lock in a plan early. In the scenario, the customer representative actively participates in iteration reviews, and the team uses what they learn from the working increment to reorder the backlog. That behavior demonstrates two core agile principles: collaborating with the customer to refine what “value” means, and responding to change by adapting priorities and plans as new insights arise. The key indicator is that change is treated as expected and beneficial when it improves value, not as a failure to follow the original plan.
Frequent stakeholder feedback and backlog reprioritization reflect collaboration and adapting the plan based on new information.
Topic: Agile Frameworks/Methodologies
A Scrum Team is midway through a 2-week sprint on a new mobile app feature. Several developers track work in personal notes, and the task board has not been updated for days. The product owner says stakeholders are asking for “daily status” because progress is unclear, and the team debates what “done” means for testing.
What is the best next step for the Scrum Master?
Best answer: A
What this tests: Agile Frameworks/Methodologies
Explanation: The immediate problem is lack of transparency and inconsistent expectations for completion. The Scrum Master should enable the team to agree on how work status and “done” will be communicated and then make that information easy to see through an information radiator. This creates a single, trusted view of progress without adding extra reporting overhead.
Information radiators (like an updated task board and burndown) make progress and blockers visible to everyone, while working agreements define how the team will work and keep information current (for example, update frequency, what columns mean, and what qualifies as “done,” often aligned with a Definition of Done). In this scenario, stakeholders are asking for more status because the existing artifacts are not trustworthy and the team has mismatched expectations about completion.
A good next step is to facilitate the team to:
Escalation, extra email reporting, or rebaselining does not fix the root cause: insufficient transparency and unclear shared agreements.
A shared agreement (including update cadence and “done”) plus an information radiator restores transparency and enables consistent progress communication.
Topic: Agile Frameworks/Methodologies
A Scrum team is trying to improve flow and quality. In each retrospective, they choose one process change (for example, adding a peer-review step or updating a testing checklist) and apply it for the next sprint.
After three sprints, cycle time still varies widely and production defects have not decreased. The product owner says priorities stayed stable during these sprints, and the team confirms they did not track any baseline or target measures (for example, cycle time, throughput, escaped defects) to evaluate whether each change helped.
What is the most likely underlying cause of the team’s lack of improvement?
Best answer: C
What this tests: Agile Frameworks/Methodologies
Explanation: Continuous improvement in agile works best when treated as small experiments with measurable outcomes. Because the team did not establish baseline and target flow/quality measures, they cannot tell whether each change improved cycle time variability or reduced escaped defects. The primary issue is the missing measurement and validation loop, not the changes themselves.
The core concept is validating continuous improvement with data. In agile, retrospectives often generate process changes, but those changes should be framed as small experiments with a clear hypothesis and a way to verify impact on flow or quality.
In this scenario, the team is making changes but not tracking baseline and target metrics (such as cycle time, throughput, WIP, or escaped defects). Without those measures, they can’t determine whether a change improved results, caused regressions, or had no meaningful effect.
Key takeaway: define how you will measure “better” before implementing an improvement, then inspect the metrics after the change.
Without baseline and target flow/quality metrics, the team cannot verify whether changes improved cycle time or defects.
Topic: Agile Frameworks/Methodologies
A company is starting Scrum for a new mobile app. In the first sprint planning meeting, a marketing manager and the technical lead give conflicting directions about which features must be done next. You have been asked to help the team decide whose input should drive the sprint backlog.
What should you ask FIRST?
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: In Scrum, the Product Owner is accountable for maximizing value and ordering the product backlog. When stakeholders provide conflicting priorities, the first step is to confirm who is serving as Product Owner so there is a single voice for priority decisions. Only then can the team select work for the sprint based on that ordering.
Agile roles clarify decision rights. In Scrum, the Product Owner represents stakeholder interests and is accountable for ordering the product backlog to maximize value. The Scrum Master is a servant leader who facilitates events and helps remove impediments but does not set product priorities. The Developers decide how much work to take and how to build it.
Because the situation is underspecified (two people are trying to set priorities), the first thing to verify is who has the Product Owner accountability and authority to make backlog ordering decisions. Once that is clear, the team can translate the top-ordered items into a sprint backlog during sprint planning.
Backlog priority and value decisions belong to the Product Owner, so you must first identify who holds that role.
Topic: Agile Frameworks/Methodologies
A team is developing a new customer self-service portal. Stakeholders are unsure which features will drive adoption, and the project sponsor is concerned about building the “wrong” solution.
Which TWO actions best demonstrate iterative and incremental delivery to reduce risk through early feedback? (Select TWO)
Correct answers: B, C
What this tests: Agile Frameworks/Methodologies
Explanation: Iterative and incremental delivery reduces risk by producing usable slices of the product early and repeatedly, then adjusting based on real stakeholder and user feedback. Short, timeboxed iterations with regular reviews help expose misunderstandings and low-value features sooner, when changes are cheaper.
Iterative and incremental delivery means building the product in small, usable increments and learning from feedback each cycle. In the portal scenario, the main risk is uncertainty about what users will value, so the team should deliver a minimal but end-to-end capability early (incremental) and use frequent reviews to inspect and adapt plans (iterative). This creates a tight feedback loop that surfaces incorrect assumptions, usability issues, and priority changes sooner.
Practical ways this reduces risk include:
The key takeaway is to optimize for fast learning with small, usable deliveries rather than relying on late-stage validation.
Early, usable increments validate assumptions quickly and reduce the risk of building the wrong product.
Frequent iteration reviews create fast feedback loops that guide incremental adjustments and lower uncertainty.
Topic: Agile Frameworks/Methodologies
A Scrum team is in day 6 of a 10-day sprint. Three stories cannot be tested because the staging environment certificate expired. Renewing it requires the IT security group to update a corporate-managed vault, which the team cannot access. The team has discussed the blocker in daily scrum for four days and tried workarounds, but no one has contacted IT security or management. The sprint goal is now at risk.
What is the most likely underlying issue?
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: The key clue is that the team cannot renew the certificate themselves because it requires IT security access. Since the impediment exceeds team authority and is threatening the sprint goal, it should be escalated promptly through the appropriate channels. Continuing to discuss it without escalation is the primary breakdown.
In adaptive projects, the team should remove impediments quickly to protect iteration objectives. When a blocker is outside the team’s authority (for example, requires another department’s access, approvals, or policy-controlled changes), the appropriate next step is escalation—typically facilitated by the Scrum Master or project lead—to the group that can act.
Here, the symptoms (multiple stories blocked and the sprint goal at risk) are driven by an external dependency: IT security must renew the certificate. The root cause is not “low velocity” or “unclear done”; it’s that the team is treating an external impediment as if they can resolve it internally instead of escalating it with urgency.
Key takeaway: escalate impediments that exceed team authority before they jeopardize iteration outcomes.
The blocker requires action from another group, and failure to escalate is what is keeping the sprint goal at risk.
Topic: Agile Frameworks/Methodologies
A company is adopting SAFe and is preparing for its first Agile Release Train (ART) event. The project coordinator is asked to brief new stakeholders on what a Program Increment (PI) is and what happens in PI planning.
Which TWO statements should be included? (Select TWO.)
Correct answers: B, D
What this tests: Agile Frameworks/Methodologies
Explanation: In SAFe, a Program Increment (PI) is a fixed timebox in which an Agile Release Train delivers a set of integrated value increments. PI planning is the recurring ART-wide event where teams and key stakeholders align on the vision, surface dependencies and risks, and agree on PI objectives and a plan for the upcoming iterations.
SAFe uses a cadence-and-synchronization model to help multiple agile teams deliver together. The Program Increment (PI) is the primary planning and delivery timebox for an Agile Release Train—commonly about 8–12 weeks—containing multiple iterations in which teams build and integrate value.
PI planning is the ART’s regular planning event that brings teams and key stakeholders together (in person or virtually) to:
Key takeaway: PI planning creates ART-level alignment and shared objectives; it does not replace team-level iteration planning or produce predictive WBS baselines.
In SAFe, a Program Increment is a fixed cadence timebox used to deliver value through multiple iterations.
PI planning is the ART-wide planning event focused on alignment and committing to shared PI objectives and an iteration plan.
Topic: Agile Frameworks/Methodologies
Midway through a 2-week sprint, the team cannot complete the sprint goal because a required API access approval is owned by an external security group. The team has already tried the agreed contact path and cannot influence the approval timeline. The Scrum Master plans to escalate the impediment to management.
Which metric or artifact best validates that the impediment exceeds team authority and threatens the iteration objective?
Best answer: C
What this tests: Agile Frameworks/Methodologies
Explanation: Escalation is appropriate when an impediment is outside the team’s control and is likely to prevent meeting the sprint goal. The strongest validation is objective progress evidence that the iteration outcome is at risk. A sprint burndown trend paired with a completion forecast clearly shows stalled progress and likely spillover caused by the external dependency.
In agile, the team manages what it can control, but impediments owned outside the team’s authority should be escalated when they jeopardize the sprint/iteration objective. To justify escalation, use evidence that links the impediment to delivery risk, not just that the team is “busy.” A sprint burndown (or similar forecast view) shows whether remaining work is being burned down at a rate consistent with finishing the sprint goal. When the burndown is flat due to blocked items and the forecast indicates incomplete work by sprint end, it provides clear, decision-ready validation that intervention is needed to remove the blocker. Notes or activity counts may describe work, but they do not validate outcome risk.
A burndown trend and completion forecast provide objective evidence the sprint goal is at risk due to blocked work.
Topic: Agile Frameworks/Methodologies
A Scrum team is starting a new product increment and wants to build quality in during each sprint. Which practice should the team AVOID because it does NOT support built-in quality in adaptive delivery?
Best answer: C
What this tests: Agile Frameworks/Methodologies
Explanation: Adaptive teams build quality into the workflow rather than inspecting it in at the end. A shared definition of done, automation (such as CI with automated tests), and peer review create fast feedback and prevent defects from moving forward. Waiting until the end of the sprint to do most testing increases rework and undermines built-in quality.
Built-in quality in adaptive delivery means the team prevents defects and verifies quality continuously as work is done, not after the fact. The definition of done sets the minimum quality criteria (for example, coding complete, reviewed, tested, and integrated) that must be met for work to be considered finished. Automation (such as continuous integration and automated regression tests) provides rapid, repeatable feedback and reduces human error. Peer reviews catch issues early and help ensure standards are followed before changes are integrated.
Making end-of-sprint testing the primary way to find defects is an inspection-late approach; it tends to batch work, delay feedback, and increase rework, which conflicts with the goal of building quality in every iteration.
Deferring quality to a final test phase is an anti-pattern that prevents continuous, built-in quality each iteration.
Use the CAPM Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the CAPM guide on PMExams.com, then return to PM Mastery for timed practice.