CAPM Agile Frameworks and Methodologies Practice Question
A Scrum team is halfway through a two-week Sprint when the Product Owner asks them to add a new high-priority feature that was not in the Sprint Backlog. The team believes they can complete it without jeopardizing the Sprint Goal. According to Scrum, what should the team do?
⚠ Common exam trap
The trap here is assuming that the Sprint Backlog is frozen once the Sprint begins, when in fact only the Sprint Goal should remain stable while the backlog can evolve.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add the feature to the Sprint Backlog and continue working toward the Sprint Goal.
The Sprint Backlog is a plan by and for the Developers, and it is updated throughout the Sprint as more is learned. Because the team judges that the new feature can be added without endangering the Sprint Goal, they may incorporate it. The Product Owner may influence priority, but the team decides how to manage its own work within the Sprint.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reject the request because the Sprint Backlog cannot be changed once the Sprint has started.
Why it's wrong here
This is a common misconception. Scrum does not prohibit changes to the Sprint Backlog during a Sprint. The Sprint Goal should remain stable, but the work needed to achieve it can evolve. Rejecting outright ignores the team's own assessment that the feature is feasible without risking the Sprint Goal.
- ✓
Add the feature to the Sprint Backlog and continue working toward the Sprint Goal.
Why this is correct
In Scrum, the Sprint Backlog is owned by the Developers and can be updated as more is learned. Since the team believes the Sprint Goal remains achievable, adding the new feature is acceptable. The Sprint Goal provides focus but does not freeze the scope; the team self-manages its work to maximize value.
- ✗
Cancel the Sprint and start a new one with the updated priorities.
Why it's wrong here
Canceling a Sprint is a drastic action reserved for when the Sprint Goal becomes obsolete, typically due to a major market or business shift. A single new feature request does not invalidate the Sprint Goal. Canceling would waste the work already done and disrupt the team's rhythm unnecessarily.
- ✗
Ask the Project Management Office (PMO) to approve the scope change before proceeding.
Why it's wrong here
Scrum teams are self-managing and do not require PMO approval for Sprint Backlog changes. The Product Owner manages the Product Backlog, and the Developers manage the Sprint Backlog. Involving a PMO contradicts Scrum's empirical approach and adds unnecessary bureaucracy that slows down value delivery.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CAPM question from scratch — 451 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
This CAPM practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CAPM exam.