CAPM Practice: Determine how to plan project iterations
Question 11 of 61 in Determine how to plan project iterations
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: Place the story in the product backlog for consideration in the next sprint planning
Explanation
Once a sprint begins, the sprint backlog is protected from scope additions by the PO. New items belong in the product backlog for prioritization and selection in the next sprint. This sprint protection is essential for team focus and predictability. If the new story is truly urgent and makes the current sprint goal obsolete, the product owner could cancel the sprint — but this is rare and disruptive.
**Why not B:** Flatly refusing the request isn't the collaborative Scrum response. The story isn't rejected; it goes to the product backlog, where the PO can prioritize it for an upcoming sprint. Sprint scope can also be clarified and renegotiated with the PO as more is learned, so 'refuse' misstates how sprint scope works.
**Why not C:** The PO owns the product backlog, but the sprint backlog belongs to the developers. Adding work mid-sprint just because the PO asks undermines the sprint commitment, team focus and predictability.
**Why not D:** Stopping and re-planning the sprint is rare and disruptive. It is reserved for cases where the sprint goal becomes obsolete. A single new story doesn't justify throwing away the work already planned and under way.
Key Concept
This question covers Determine how to plan project iterations under Determine how to plan project iterations (Agile Frameworks/Methodologies).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free