CSM Scrum Events Practice Question
A Scrum Team is preparing for the Sprint Review. The Product Owner wants to know who is required to attend and what the event's primary output should be. Which statement correctly describes the Sprint Review?
⚠ Common exam trap
The trap here is treating the Sprint Review as a formal sign-off or demo rather than a collaborative working session that adapts 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
✓
It is a working session where the Scrum Team and stakeholders inspect the Increment and collaborate on what to do next, resulting in an adapted Product Backlog.
The Sprint Review is a collaborative working session in which the Scrum Team and stakeholders inspect the Increment and progress toward the Product Goal, then adapt the Product Backlog. It is not a formal approval gate, not a status presentation, and not an internal-only meeting. Its output is an updated Product Backlog that shapes what comes next.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It is a formal sign-off meeting where stakeholders approve or reject the Increment before it can be released.
Why it's wrong here
The Sprint Review is not a gate or approval meeting. Scrum does not require stakeholder sign-off for an Increment to be released; the Product Owner decides on release timing. Framing the event as formal approval undermines the collaborative inspection and can delay value delivery. The focus should be on inspecting the Increment and adapting the Product Backlog.
- ✗
It is a presentation by the Developers to stakeholders, ending with a report of completed Story Points and velocity.
Why it's wrong here
The Sprint Review is a working session, not a one-way presentation. Reading off Story Points and velocity turns it into a status report and misses the purpose of inspecting the Increment and collaborating on next steps. Story Points are internal estimates for the Developers, not a performance metric to present to stakeholders.
- ✓
It is a working session where the Scrum Team and stakeholders inspect the Increment and collaborate on what to do next, resulting in an adapted Product Backlog.
Why this is correct
The Sprint Review is an informal working session, not a formal presentation. The Scrum Team and stakeholders inspect the Increment and discuss progress toward the Product Goal, and the outcome is an adapted Product Backlog that informs the next Sprint. This collaborative inspection is exactly what makes the event valuable and distinguishes it from a status report or demo.
- ✗
It is an internal meeting for the Scrum Team only, where the Developers decide which items to carry into the next Sprint.
Why it's wrong here
The Sprint Review explicitly includes stakeholders and is not an internal-only meeting. Deciding what to carry forward is part of Sprint Planning, not the Review. Excluding stakeholders removes the collaborative inspection that gives the Review its value and makes it harder for the Product Owner to adapt the Product Backlog based on feedback.
About these practice questions
This CSM question is part of Courseiva's 312-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 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.