Certified Scrum Master Practice Test

How should feedback be treated during the Sprint Review?

1. It should be ignored

2. It should be documented but not acted upon

3. It should be collected and acted upon

4. It should be reviewed in detail after the meeting

The correct answer is: It should be collected and acted upon

During the Sprint Review, feedback should be collected and acted upon because this is a crucial opportunity for the Scrum Team to engage with stakeholders and understand their perspectives on the work completed during the Sprint. The purpose of the Sprint Review is not only to showcase the work but also to gather insights that can help improve future Sprints. By actively collecting feedback, the team can identify areas for improvement, validate their assumptions, and ensure that they are aligning their product development with stakeholder needs and market demands. Acting upon this feedback reinforces the agile principle of responding to change over following a plan, thus fostering a culture of continuous improvement within the team and the broader organization. Collecting and acting on feedback establishes a feedback loop that enhances collaboration, promotes transparency, and ultimately drives better product outcomes. It supports the iterative nature of Scrum, where each Sprint leads to refinements and adjustments based on real insights gained from stakeholders. Consequently, this approach directly contributes to the team's ability to deliver valuable and relevant products incrementally.