The sprint review is an informal meeting which the development team, the scrum master, the product owner and the stakeholders will attend. The team gives a demo on the product and will determine what are finished and what aren’t. The purpose of the Sprint Review meeting is for the team to show the customers and stakeholders the work they have accomplished over the sprint and compare it to the commitment given at the beginning of the sprint.
Sprint Review vs Sprint Retrospective
Each sprint ends with a two-part sprint review meeting. Such a meeting starts with a customer review and demonstration and ends with the team retrospective. Both of these components occur on the last day of the sprint.
The Sprint Review focuses on the “inspect” and “adapt” of the increment (Potentially shippable), while the Sprint Retrospective give more focus on the “inspect” and “adapt” of the process of the sprint.
Sprint Increment Review
The Scrum teams will ask customers to review whether the work demonstrated (potentially shippable) meets the definition of done at this point, or sometimes, some customers may want time to use the application for some time prior to the acceptance made. The goal of the meeting is to review transparently and determine the status of the work implemented in the sprint:
has been done
has not been done
work that has been added
And work removed from the sprint
It offers the time to ask questions, make observations or provide feedback and suggestion, and have discussions about how to best move forward in the given current realities.
Best Scrum Software Every Project Needs
A powerful scrum software that supports scrum project management. It features scrum tools like user story map, product backlog management, sprint backlog management, task management, daily scrum meeting, sprint planning tool, sprint review tool, sprint retrospective tool, burndown, impediment, stakeholder and team management.
A sprint review may last up to 4 hours in 4-week-sprints. The general rule is that the sprint review should take no more than one hour per week of sprint duration. The following table illustrates the rule.
Total Sprint Duration
Sprint Review Duration
Sprint Review Meeting Template
There are many ways for conducting a Sprint Review. The sprint review meeting agenda below outlines the activities within a typical Sprint Review meeting:
Start – Sprint Review Meeting starts
Welcome the Stakeholders – Product Owner welcomes the stakeholders to attend the review
Present Review Agenda – Product Owner presents the agenda for the Sprint Review
Present Product Increments – Development Team present the product demo that have been implemented in the Sprint
Get Feedback – Product Owner asks the stakeholders for feedback regarding the product that have been delivered
Present Product Backlog – Product Owner presents the top of the Product Backlog to stakeholder to get feedback for the upcoming Sprint(s) and solicit feedback from the stakeholders related to the backlog
About Visual Paradigm
Visual Paradigm help organizations stay competitive and responsive to change faster and better in today’s fast changing environment. Our award-winning products are trusted by over 320,000 users in companies ranging from small business, consultants, to blue chip organizations, universities and government units across the globe. It enables organizations to improve business and IT agility and foster innovation through popular open standards and process frameworks.Visual Paradigm, a killer Agile feature in 2018, introduced Scrum Process Canvas for automating the way a Scrum team to create, manage and deploy software application that empowers the team to continuously improve their performance at unprecedented speed and scale.
Manage the Entire Scrum Process in One Page
Automate the Scrum Framework in a fun and enjoyable dashboard with eye-catching updated status.
Manage Backlog, Multiple Sprints of different Scrum Roles with a single-page visually executable canvas
Allow instantly access, review and generate scrum artifacts and related documents to be archived in the Shared Cabinet
Automate the Scrum events and related activities with self-explanatory instructions, samples and required document templates.
Turn every software project into a successful one.