CAPM Agile Frameworks and Methodologies Practice Question
A Scrum team is midway through a two-week Sprint when the Product Owner introduces a new high-priority feature request from a key stakeholder. The team has already completed about 40% of the Sprint Backlog. According to Scrum, what should the team do?
⚠ Common exam trap
The trap here is assuming the Product Owner can unilaterally inject new work into a running Sprint because they own the Product Backlog.
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
✓
Ask the Product Owner to add the new feature to the Product Backlog and let the team address it during the next Sprint Planning.
Scrum shields the Sprint from disruptive scope changes so the team can meet the Sprint Goal. New stakeholder requests belong in the Product Backlog, where the Product Owner orders them by value. The Developers then pull the highest-priority items during the next Sprint Planning, based on capacity. This preserves focus, protects quality, and keeps prioritization in the hands of the Product Owner.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Have the Developers work overtime to complete both the original Sprint work and the new feature within the same Sprint.
Why it's wrong here
Adding unplanned scope and relying on overtime contradicts Scrum's emphasis on sustainable pace and predictable delivery. The team's capacity for the Sprint was already established during Sprint Planning. Overloading the team risks quality, morale, and the Sprint Goal, and it does not address the proper flow of new requests through the Product Backlog.
- ✗
Add the new feature to the current Sprint Backlog and reprioritize, since the Product Owner owns the backlog.
Why it's wrong here
In Scrum, the Sprint Backlog is owned by the Developers, not the Product Owner. Modifying it mid-Sprint to inject new scope undermines the Sprint Goal and the team's self-management. The Product Owner may reorder the Product Backlog, but cannot unilaterally change the Sprint Backlog or force new work into the running Sprint without the team's agreement.
- ✓
Ask the Product Owner to add the new feature to the Product Backlog and let the team address it during the next Sprint Planning.
Why this is correct
Scrum protects the Sprint from scope changes that would endanger the Sprint Goal. New requests are captured in the Product Backlog, where the Product Owner can order them against other items. The Developers then select work during the next Sprint Planning based on value and capacity, preserving the current Sprint's focus and the agreed Sprint Goal.
- ✗
Stop the Sprint, run Sprint Planning again, and start a new Sprint with the revised priorities.
Why it's wrong here
Cancelling a Sprint is reserved for when the Sprint Goal becomes obsolete, and only the Product Owner has the authority to cancel. A single new stakeholder request does not typically make the Sprint Goal obsolete. Restarting the Sprint would waste the completed work and disrupt the team's cadence without valid justification.
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.