Suggest an editImprove this articleRefine the answer for “What happens at a Sprint Review?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)A **Sprint Review** is a meeting held at the end of every sprint, where the team shows the results of its work and gets feedback from stakeholders. **Key point:** it is not just a demo - it is a working session where the team discusses what was done, what changed in the product, and how to move forward.Shown above the full answer for quick recall.Answer (EN)ImageA **Sprint Review** is a meeting held **at the end of every sprint**, where the team shows the results of its work and gets feedback from stakeholders. It is not just a demo - it is a **working session** where the team discusses what was done, what changed in the product, and how to move forward. --- ### Purpose The main purpose of a Sprint Review is to **assess the increment (the finished part of the product)** and **adjust the Product Backlog** based on new data, ideas, and priorities. The team and the client decide together what makes sense to do in upcoming sprints so the product stays valuable and relevant. --- ### What happens at the meeting 1. The **Product Owner** explains: - which items from the backlog were planned; - which were completed and which were not; - whether there are changes in priorities or requirements. 2. The **development team** demonstrates the sprint result - working functionality (the increment), not a prototype or a draft. This can be a new feature, an improvement, or a fix. Anything that is "done" according to the **Definition of Done**. 3. **Stakeholders** - clients, users, managers - give feedback. They assess how well the result matches expectations and business goals. 4. **Discussion of the product's future.** The team and the Product Owner update the **Product Backlog**: adding new ideas, clarifying requirements, changing priorities based on the feedback received. --- ### Participants - **Development team** - demonstrates the result; - **Product Owner** - explains what was planned and what was done; - **Scrum Master** - facilitates the meeting; - **Stakeholders** - business representatives, clients, users. --- ### Format and duration The meeting is held at the end of every sprint and lasts **up to 4 hours** for a month-long sprint (or less for shorter iterations). It happens in an informal, open format: no presentations or reports - just the working product and dialogue. --- ### Conclusion The **Sprint Review** is the feedback point between the team and the business. Here the value of what was done is assessed, new possibilities are discussed, and an up-to-date direction for product development is formed. The result of the meeting is an updated Product Backlog and a shared understanding of where to go next.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.