The Sprint Review is a meeting held at the end of the sprint to review the completed work and present it to stakeholders.

What happens during the Sprint Review?

• The team presents a demo of the work completed during the sprint.

  • Only User Stories that meet the Acceptance Criteria and are done are demonstrated.

• Review of the Sprint Goal

  • Was the goal achieved? Why or why not?

• Collect feedback and comments from:

  • Business team

  • Product Owner

  • Other stakeholders attending

• Discuss any requested changes or new ideas.

• Update the Product Backlog based on feedback.

Important rules

• The demo must be of working software, not mockups or incomplete work.

• The meeting focuses on the product, not on individual performance or blame.

• Any incomplete work is returned to the backlog and not marked as done.

Meeting duration

• For a two-week sprint, the meeting typically lasts 1 to 2 hours max.

Why is the Sprint Review important?

• Allows the business to see real progress.

• Ensures the team is on the right track.

• Supports informed decision-making based on actual work.

• Strengthens communication between the team and stakeholders.