CSM Scrum Team Roles and Accountabilities Practice Question
During a Sprint Review, a key stakeholder expresses dissatisfaction with the Increment's functionality and demands that the Developers immediately start working on a new feature that was not in the Sprint Backlog. The Product Owner is present. How should the Scrum Master respond?
⚠ Common exam trap
The trap here is thinking the Scrum Master should either immediately accommodate the stakeholder or act as an approval authority, rather than redirecting the request to the Product Owner for backlog consideration.
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
✓
Explain that the Sprint Review is for gathering feedback, and the Product Owner will consider the new feature for the next Sprint Planning.
The Sprint Review is a working session for inspecting the Increment and adapting the Product Backlog. New requests should be directed to the Product Owner for consideration in future Sprints. The Scrum Master should facilitate this understanding and protect the Developers from mid-Sprint disruptions, ensuring the Sprint Goal remains intact.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Tell the stakeholder that they must submit a formal change request to the Scrum Master for approval.
Why it's wrong here
The Scrum Master does not approve change requests. The Product Owner is the sole point of contact for backlog changes. Introducing a formal approval process by the Scrum Master contradicts Scrum principles and adds unnecessary bureaucracy. The Scrum Master should facilitate collaboration, not act as a gatekeeper.
- ✗
Ignore the stakeholder's demand and continue the Sprint Review as planned without addressing the concern.
Why it's wrong here
Ignoring stakeholder feedback is counterproductive. The Sprint Review is an opportunity to gather input and adapt. The Scrum Master should acknowledge the concern and guide the discussion toward the Product Owner, who can incorporate it into the Product Backlog. Dismissing feedback damages transparency and stakeholder engagement.
- ✓
Explain that the Sprint Review is for gathering feedback, and the Product Owner will consider the new feature for the next Sprint Planning.
Why this is correct
The Scrum Master should clarify the purpose of the Sprint Review and ensure the stakeholder understands that new requests are handled by the Product Owner for future Sprints. This protects the current Sprint and respects the Product Owner's accountability for ordering the Product Backlog. It also keeps the focus on inspecting the Increment and adapting the backlog.
- ✗
Ask the Developers to stop their current work and begin the new feature immediately to satisfy the stakeholder.
Why it's wrong here
Directing the Developers to abandon the Sprint Goal and start new work mid-Sprint undermines Scrum. The Sprint Review is for inspecting the Increment and adapting the Product Backlog, not for changing the current Sprint. The Scrum Master should protect the team from such disruption and facilitate a constructive discussion about future work.
About these practice questions
One of 312 original CSM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.