Along with demonstrating the scrum team’s finished work, an agile sprint review meeting enables stakeholders to provide feedback on that work. This cycle of feedback repeats throughout the agile project:
Each day, development team members work together in a collaborative environment that encourages feedback through peer reviews and informal communication.
Throughout each sprint, as the development team completes each requirement, the product owner provides feedback by reviewing the working functionality for acceptance.
At the end of each sprint, project stakeholders provide feedback about completed functionality in the sprint review meeting.
With each release, customers who use the product provide feedback about new working functionality.
The feedback loops look something like this:
Gathering feedback during the sprint review is an informal process. The product owner or scrum master can take notes on behalf of the development team, as team members are often engaged in the presentation and resulting conversation.
New user stories may come out of the sprint review. The new user stories may be new features altogether, or they may be changes to the existing product or code.
The product owner has several tasks to complete after the review:
Add any new user stories to the product backlog and put them in priority order.
Add stories that were scheduled for the current sprint but weren’t completed back into the product backlog and reorder those stories based on the most recent priorities.
Complete updates to the product backlog in time for the next sprint planning meeting.