CSM Scrum Events Practice Question
A Scrum Team finishes Sprint Planning with a clear Sprint Goal and a set of selected Product Backlog items. Two days into the Sprint, a Developer identifies a better technical approach that would change the composition of the Sprint Backlog while still achieving the Sprint Goal. What should the team do?
⚠ Common exam trap
The trap here is assuming the Sprint Backlog is a fixed commitment that requires Product Owner approval to change, when in fact only the Sprint Goal is fixed during the Sprint.
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
✓
Update the Sprint Backlog to reflect the new approach, since the Sprint Backlog is owned by the Developers and may be adjusted as long as the Sprint Goal is not endangered.
The Sprint Backlog belongs to the Developers and is expected to change as they learn more during the Sprint. Because the Sprint Goal stays viable, the Developers can revise their plan without permission from the Product Owner or Scrum Master. Re-planning via a new Sprint Planning event or canceling the Sprint is unnecessary and not supported by Scrum.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Cancel the Sprint and start a new one so the revised plan can be properly planned and committed to from the beginning.
Why it's wrong here
A Sprint may only be canceled if the Sprint Goal becomes obsolete, and only the Product Owner holds that authority. A superior technical approach does not make the Sprint Goal obsolete. Canceling would waste the work already done and is a disproportionate response to a routine plan adjustment.
- ✓
Update the Sprint Backlog to reflect the new approach, since the Sprint Backlog is owned by the Developers and may be adjusted as long as the Sprint Goal is not endangered.
Why this is correct
The Sprint Backlog is a plan by and for the Developers and is updated throughout the Sprint as more is learned. Because the Sprint Goal remains achievable, the Developers are empowered to change the plan without seeking outside permission, keeping the Sprint Goal as the fixed target.
- ✗
Continue with the original Sprint Backlog unchanged to preserve the Sprint's original forecast and avoid scope churn.
Why it's wrong here
The Sprint Backlog is emergent, not frozen. Insisting on the original plan after learning something better ignores empiricism and may reduce value. Scrum expects the Developers to adapt their plan as they learn, provided the Sprint Goal remains the focus, so refusing to update the Sprint Backlog is contrary to the framework.
- ✗
Call an emergency Sprint Planning session with the Product Owner to formally re-baseline the Sprint Backlog before any work changes.
Why it's wrong here
Sprint Planning is a time-boxed event that occurs once at the start of the Sprint. Re-running it mid-Sprint is not prescribed by Scrum and would add unnecessary ceremony. The Developers already hold the authority to adapt their plan, so a formal re-baseline with the Product Owner is not required to change the Sprint Backlog.
About these practice questions
Courseiva writes every CSM question from scratch — 312 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 Scrum Alliance exam blueprint
This CSM practice question is part of Courseiva's free Scrum Alliance 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 CSM exam.