Sprint Review
Instead of presenting charts, reports, or slides, the Scrum Team demonstrates what was done. If the Product Backlog Items are in user story format, the team could opt to form a narrative so that the flow will be logical and easy to follow. Typically the developer that completed the work would demonstrate the functionality. The Product Owner should facilitate the Sprint Review since this is a meeting that will involve key stakeholders.
The Sprint Review is for the Scrum Team to get user feedback and openly discuss what can be done to improve the product. Although feedback is welcome, the Product Owner is not obliged to accept every change request, especially if it doesn’t fit their Product Vision. Nevertheless, inputs from the Sprint Review can add Product Backlog Items for future Sprints.
Developing and Testing Product Backlog Item’s
Because the Sprint Review is for demonstrating the product and getting feedback, it’s important to note that Product Backlog Items should have been developed and tested prior to the ceremony. Testing Product Backlog Item’s during the Sprint Review can use up a lot of time as well as look unprofessional to customers and users present at the meeting.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: