- 1. What Is the Scrum Methodology?
- 2. Guide to Scrum Sprints
- 3. Scrum Sprint Planning
- 4. The Complete Guide to Scrum Ceremonies
- 5. The Ultimate Guide to Sprint Retrospectives
- 6. Daily Scrum Meetings
- 7. Scrum of Scrums Meeting
- 8. Introduction to Scrum Team and Roles
- 9. What Is a Scrum Product Owner?
- 10. What Is a Scrum Master?
- 11. Best Scrum Software and Tools for 2023
- 12. A Complete Guide to Scrum Boards
- 13. Scrum Glossary
- 14. FAQs
- 1. What Is the Scrum Methodology?
- 2. Guide to Scrum Sprints
- 3. Scrum Sprint Planning
- 4. The Complete Guide to Scrum Ceremonies
- 5. The Ultimate Guide to Sprint Retrospectives
- 6. Daily Scrum Meetings
- 7. Scrum of Scrums Meeting
- 8. Introduction to Scrum Team and Roles
- 9. What Is a Scrum Product Owner?
- 10. What Is a Scrum Master?
- 11. Best Scrum Software and Tools for 2023
- 12. A Complete Guide to Scrum Boards
- 13. Scrum Glossary
- 14. FAQs
What Is the Goal of the Sprint Review Meeting?
To quote the official Scrum Guide, the purpose of sprint review “is to inspect the outcome of the Sprint and determine future adaptations.”
On a practical level, certain items on a sprint review checklist need to be addressed in order to assess whether the criteria for achieving the sprint goal have been met.
- Product demonstration: To showcase completed functionality to the team, stakeholders, and gather feedback
- Closure of completed user stories: Learning from the process and celebrating achievements
- Review and re-prioritization of incomplete user stories: They can be added back to the product backlog or tackled in the next sprint
- Update of the product backlog: In preparation for planning the next sprint
The goal of a sprint review meeting
Once tasks have been completed the sprint review’s goal is achieved: the product increment is inspected and the product backlog is adapted. This also means that, from a product perspective, the sprint is closed off and everything is ready to start the next one.
Sprint review meetings should also note processes-related points to address in the sprint retrospective meeting.
What happens if sprint goals are not achieved?
Typical scenarios include:
- The increment is not quite ready or presentable
- Not everyone can participate
- The sprint goal has not been achieved
This is not uncommon and often sprint reviews are postponed until goals are achieved.
Alex Zhezherau
Alex is Wrike’s Product Director, with over 10 years of expertise in product management and business development. Known for his hands-on approach and strategic vision, he is well versed in various project management methodologies — including Agile, Scrum, and Kanban — and how Wrike’s features complement them. Alex is passionate about entrepreneurship and turning complex challenges into opportunities.