Post

Scrum - Sprint Review

Let’s take a closer look at the Sprint Review ceremony inorder to better understand what happens, who’s involved, and what the expected outcomes are.

1. What’s a sprint review?

The sprint review is a meeting held at the end of a sprint where the scrum team presents the completed work to stakeholders and gathers feedback. It focuses on reviewing the increment (the potentially shippable product) and discussing what to build next.

2. When does it occur?

The sprint review occurs at the end of the sprint (typically the last day of the sprint), before the sprint retrospective.

3. Who is involved?

Sprint review meeting has the biggest audience as far as scrum ceremonies go. This meeting involves the scrum team and stakeholders

  • 👉 Product owner:
    • confirm the sprint goal was met
    • provide business context
    • update the product backlog based on feecback
  • 👉Scrum master:
    • facilitate the meeting keep the discussions focused
    • ensure transparency and collaboration
  • 👉 Developement team:
    • demo the completed work
    • answer technical questions
    • bring up any development challenges
  • 👉 Stakeholders:
    • provide feedback on the product increment
    • validate if product meets business need
    • discuss concerns (market or customer expectations) that may impact future work.
  • 👉 End-Users (optional):
    • test and provide direct usability feedback
    • suggest improvements based on real-world usage.

4. How long is this meeting

The sprint review meeting is usually 1-2 hours for a two-week sprint, but it can be longer for bigger sprints.

5. What’s the expected outcome of this meeting

By the end of this meeting, both the Scrum Team and stakeholders should have a shared understanding of the completed work and align on the next steps. Here’re more details:

  • ✅ Demonstrated work: the team showcases completed user stories
  • ✅ Stakeholder feedback: gather inputs for future improvements
  • ✅ Updated product backlog: product owner will adjusted the product backlog based on review discussions.
  • ✅ Alignment for next setps: scrum team and stakeholders align on priorities for upcoming sprints
This post is licensed under CC BY 4.0 by the author.