CSM Scrum Events Practice Question
At the Sprint Review, an important stakeholder expresses dissatisfaction with a core feature delivered by the Development Team, stating it does not solve their current business workflow. How should this feedback be handled?
⚠ Common exam trap
Candidates often assume the disgruntled stakeholder can immediately rewrite the current Increment or force changes mid-Sprint, forgetting that all new work must go through the Product Owner for backlog prioritization.
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
✓
Capture the stakeholder feedback as new items in the Product Backlog for the Product Owner to prioritize.
The Sprint Review is a working session designed to inspect the Increment and adapt the Product Backlog based on stakeholder feedback. Discontent from stakeholders indicates a shift in understanding or requirements, which the Product Owner must capture and incorporate into the Product Backlog as new items. This feedback loop validates the empirical nature of Scrum, ensuring the product evolves to meet real market needs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ignore the feedback because the Development Team strictly followed the requirements provided in the initial backlog.
Why it's wrong here
Ignoring stakeholder feedback violates the core agile tenet of responding to change over following a plan. The Sprint Review exists precisely to gather this feedback and adapt the product direction based on real usage and inspection.
- ✗
Scold the Development Team for failing to understand the business needs during Sprint Planning.
Why it's wrong here
Feedback at the Sprint Review is inspected and adapted by the Scrum Team; blaming the Developers misdirects the response and breaches Scrum's respect value. Scolding fits nowhere in Scrum, whereas the Product Owner would instead reorder the Product Backlog to address the workflow gap.
- ✓
Capture the stakeholder feedback as new items in the Product Backlog for the Product Owner to prioritize.
Why this is correct
Feedback at the Sprint Review is not a change request to action immediately; it is new information. Logging it in the Product Backlog lets the Product Owner weigh it against other items and re-prioritise, preserving the team's sprint commitment and the Product Owner's sole authority over backlog ordering.
- ✗
Suspend the release pipeline and force the team to rewrite the entire feature before leaving the room.
Why it's wrong here
Halting delivery and demanding a full rewrite discards the inspected Increment and ignores the Product Owner's authority to order the Product Backlog; the Sprint Review exists to inspect and adapt, not to authorise emergency rework. It is tempting because it appears decisive, and would be correct only if the stakeholder held Product Owner authority and the backlog genuinely required reprioritisation.
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.