Yes, we all have too many let's at least stay organized! → Discover ZipDo

How To Run A Sprint Review Meeting

To run a Sprint Review meeting, provide a comprehensive review of the work completed and not completed, discuss what went well and what could be improved, get feedback from stakeholders, and adjust the backlog for the next sprint.

A Sprint Review Meeting is a key event in the Scrum framework where the development team presents the work completed during the sprint to stakeholders and gathers their feedback. The meeting aims to evaluate the increment of work achieved and ensure it aligns with the product owner’s expectations. This collaborative session allows stakeholders to provide input, ask questions, and suggest any necessary adjustments. Ultimately, the outcome of the Sprint Review Meeting helps the team and the product owner to determine the next steps and plan for the upcoming sprint.

What is the purpose of a Sprint Review Meeting?

Running a sprint review meeting as a leader serves the purpose of showcasing the completed work to stakeholders, gathering feedback, and evaluating progress towards meeting project goals. It provides an opportunity to foster transparency, collaboration, and accountability within the team while ensuring alignment with client expectations and continuous improvement.

How To Run A Sprint Review Meeting: Step-By-Step


Step 1: Preparation

The scrum master or project manager prepares for the sprint review meeting by collecting information on completed tasks, unfinished work, and relevant items from the product backlog. This ensures a comprehensive and productive discussion during the meeting.

Next Step

Step 2: Scheduling

Once a suitable time and date for a meeting has been determined, it is essential to ensure the availability and participation of all key stakeholders. This includes the scrum team, product owner, and any other individuals with a vested interest in the project’s success.

Next Step

Step 3: Setting the Agenda

The agenda is crucial in determining the flow and direction of a meeting. It not only decides the order and priority of topics but also ensures that achievements and progress made during the sprint are discussed and reviewed effectively.


Want to run a better meeting? Try ZipDo, our Meeting Note Software.

  • Connect your Google Calendar
  • Automatically create a note for every meeting
  • Organize your meetings and meeting notes in a channel like Slack
Learn more about ZipDo
Next Step

Step 4: Review of Achievements

During the sprint review, the scrum team examines completed tasks and objectives, recognizing how these achievements align with the project’s overarching goals, thereby ensuring progress and cohesion within the team.

Next Step

Step 5: Discussing Unfinished Items

During the sprint review, any unfinished tasks are thoroughly analyzed and discussed. The team examines the obstacles they encountered, strategizing ways to overcome them for the upcoming sprint, ensuring continuous improvement and successful project completion.

Next Step

Step 6: Product Demonstration

The team showcases a functional prototype of the product, utilizing the tasks accomplished during the sprint. This allows stakeholders to have a comprehensive understanding of the latest advancements made in the project.

Next Step

Step 7: Feedback Collection

Feedback is an essential component of the evaluation process, as it gathers valuable input from stakeholders who provide comments, suggestions, and perspectives on the product’s demonstration and overall project.

Next Step

Step 8: Backlog Adjustment

The feedback received allows for adjustments in the product backlog, including reordering items based on new insights and prioritizing tasks accordingly. This ensures the product development aligns with the evolving needs and expectations of the stakeholders.

Next Step

Step 9: Goals for Next Sprint

During the team’s objective-setting session for the upcoming sprint, they review the backlog and consider feedback from stakeholders. This ensures alignment and clarity on goals for the sprint.

Next Step

Step 10: Retrospective Meeting Planning

During this phase, the scrum master initiates preparations for the upcoming retrospective meeting, where the team will review the successes and failures experienced during the recently completed sprint.

Questions to ask as the leader of the meeting

1. What was achieved during this sprint? – This question helps the leader assess the progress made during the sprint and understand the output delivered by the team.

2. Did we meet our sprint goals? – This question helps the leader determine whether the team successfully met their predetermined objectives for the sprint.

3. What challenges did the team face during this sprint? – This question encourages team members to voice any difficulties or obstacles they encountered, providing an opportunity to address them and improve future sprints.

4. How well did the team collaborate during this sprint? – This question allows the leader to gauge the level of teamwork and collaboration among team members, helping identify areas for improvement or acknowledgment.

5. Did we maintain the quality standards set for this sprint? – This question ensures that the team reflects on the quality of their work and whether it meets the expected standards, helping identify any areas that need improvement.

6. Did we deliver value to the stakeholders? – This question evaluates whether the work completed during the sprint provided value to the stakeholders or if there are ways to enhance customer satisfaction.

7. Were there any changes or adjustments made that impacted the sprint? – This question helps the leader understand any changes or unexpected events that occurred during the sprint, allowing them to assess the impact on the team’s performance.

8. What did we learn as a team during this sprint? – This question promotes a culture of continuous learning, where the team reflects on their experiences and identifies valuable lessons that can be applied to future sprints.

9. Did we adhere to the sprint timeline and prioritize effectively? – This question allows the leader to evaluate the team’s ability to manage time effectively, ensuring that tasks were completed within the sprint timeframe and with appropriate prioritization.

10. Are there any suggestions or feedback for improving future sprints? – This question invites team members to provide their input on how to enhance future sprints, ensuring continuous improvement within the team’s working processes.

As a leader, preparing a sprint review meeting agenda requires careful planning. Start by setting clear objectives for the meeting and identify the specific items to be discussed, such as completed user stories and key metrics. Allocate time for team presentations, stakeholder feedback, and any necessary discussions or clarifications. Prioritize the most important topics and ensure everyone is aware of the agenda in advance to maximize productivity and engagement during the meeting.

How To Prepare For A Sprint Review Meeting
Meeting Preparation Icon

During a sprint review meeting, it is crucial to discuss the completed user stories, the progress made towards the sprint goals, any challenges faced, and how they were overcome. Additionally, customer feedback and suggestions should be addressed, and adjustments should be made based on the lessons learned.

See Our Sprint Review Meeting Template
Meeting Template Icon

Software tools to facilitate a Sprint Review Meeting

Software helps leaders run sprint review meetings by providing an organized platform for tracking progress, gathering feedback, and presenting results. With customizable features like task boards, real-time data visualization, and collaboration tools, it streamlines the entire process, enabling leaders to efficiently assess team performance and make informed decisions for future sprints.

Our Recommendations:


In conclusion, the sprint review meeting is a crucial event in the agile development process that allows teams to showcase their work, gather feedback, and make necessary adjustments. By following the steps outlined in this blog post, you can ensure that your sprint review meetings are effective, efficient, and productive.

Remember to prioritize transparency, collaboration, and continuous improvement throughout the sprint review process. Encourage open communication, celebrate team accomplishments, and use customer feedback to drive the next steps in your development cycle.

By embracing the sprint review meeting as an opportunity for learning and growth, you can empower your team to deliver high-quality, customer-centric solutions. So, start implementing these tips and watch your sprint review meetings become invaluable in driving success for your business.

Popular Questions

What is the main purpose of a Sprint Review Meeting?

A Sprint Review Meeting primarily exists to inspect the outcome of the sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress towards the Sprint Goal is discussed.

Who should attend a Sprint Review Meeting?

Typically, the participants of a Sprint Review Meeting include the Product Owner, Scrum Master, the Scrum Team, and key stakeholders. Anyone interested in checking the progress of the project may attend.

What is the usual duration of a Sprint Review Meeting?

The Sprint Review is time-boxed to a maximum of four hours for a month-long Sprint. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the meeting takes place and that attendants understand its purpose.

What should be presented in a Sprint Review Meeting?

The Product Owner typically starts the Sprint Review by explaining what Product Backlog items have been done and what have not. The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved. The Development Team demonstrates the work that it has “Done” and answers questions about the Increment.

What happens after a Sprint Review Meeting?

After a Sprint Review Meeting, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on the changes to the Product Backlog during the Sprint, attendees collaborate on what to do next, which results in a revised Product Backlog that defines the probable Product Backlog items for the next Sprint.