True. The Sprint Review is the event where stakeholders see the outcome of the Sprint and give feedback that shapes the Product Backlog.
Exam Question
True or False: Sprint Reviews are an opportunity to collect stakeholder feedback.
A. True
B. False
Correct Answer
A. True
Why This Is the Correct Answer
The Scrum Guide says the purpose of the Sprint Review is “to inspect the outcome of the Sprint and determine future adaptations.” During the event, “The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.” Stakeholders react to the Increment, share what has changed in their environment, and help decide what to do next. That feedback may lead the Product Owner to adjust the Product Backlog. The Guide also warns against reducing the event to a presentation, which is why two-way feedback matters so much here.
Why the Other Options Are Wrong
B. False Collecting stakeholder feedback is a central reason for holding the Sprint Review. Saying false would turn it into a one-way demo or a sign-off.
Exam Tip
For True/False questions about an event’s purpose, recall the event’s inspect-and-adapt target. For the Sprint Review it is the Increment and the Product Backlog, with stakeholders involved.
Key Takeaways
- The Sprint Review inspects the outcome of the Sprint.
- Stakeholder feedback can change the Product Backlog.
- It is a working session, not just a demo.
Get ready for the official PSPO I exam
320 PSPO I practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 80 random questions in 60 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSPO I exam fee ($200) is paid separately to Scrum.org.
More PSPO I exam questions
- True or False: Dependencies could influence how the Product Owner orders Product Backlog items.
- In the middle of the Sprint, the customer decides that there are 2 new features she wants. The Product Owner could:
- A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountable for Product Backlog. However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog?
- Who is accountable for releasing the most valuable product possible?
- How much time must a Product Owner spend with the Developers?” (PSPO I)