How To Run An Agile Sprint Review Meeting

In an Agile Sprint Review Meeting, present completed work during the sprint to stakeholders for feedback, reflect on the progress, align everyone’s understanding, and make improvements for future sprints.

An Agile Sprint Review Meeting is a type of gathering in the Agile development process, typically held at the end of a sprint cycle, to review the work completed and the work not completed. This meeting provides an opportunity for stakeholders, the scrum team, and the product owner to discuss the progress made, demonstrate the accomplished work, gain immediate feedback, and align everyone for future expectations. The overall goal of this meeting is to ensure transparency and collaboration throughout the team, as well as enable necessary corrections or adjustments to be made for the next sprint for continuous improvement and efficiency.

What is the purpose of a Agile Sprint Review Meeting?

The purpose of running an agile sprint review meeting as a leader is to gather feedback from stakeholders, assess the progress of the project, and make necessary adjustments. It provides an opportunity to showcase completed work, address any issues or concerns, and ensure that the team is aligned with the project goals and customer expectations.

How To Run An Agile Sprint Review Meeting: Step-By-Step


Step 1: Meeting Preparation

Before the agile sprint review meeting, the team readies a detailed demonstration of the completed work. This preparation is pivotal as it efficiently communicates the accomplishments of the sprint, showcasing progress, addressing any challenges faced, and setting up the direction for future work.

Our application, ZipDo, transforms your calendar by importing meetings into a collaborative environment designed for team interaction. Here, a collective meeting agenda is developed, encouraging input from all team members. This approach fosters better-prepared meetings, enhancing efficiency and easing the burden of meeting preparation and follow-up.

With ZipDo, our application, the hassle of preparing for team meetings is significantly reduced. Meeting leads benefit from a central hub of information from prior meetings, streamlining the retrieval of agendas and notes. This methodical approach ensures complete topic coverage.

Next Step

Step 2: Sprint Review Invitation

The product owner extends an invitation to stakeholders, fellow teams, management personnel, and any other party vested in the project to attend the sprint review session. This assembly of key participants is crucial as each individual is encouraged to provide feedback. This collaborative dialogue is vital in aligning the project’s trajectory towards success and meeting everyone’s expectations.

Next Step

Step 3: Product Increment Demonstration

During team meetings, typically a designated member acts as the presentational lead, tasked with exhibiting the product increment to key stakeholders. This crucial demonstration effectively communicates the progress made during the sprint, ensuring that everyone involved fully comprehends the achievements and tasks completed in this developmental phase.


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
Try ZipDo free
Next Step

Step 4: Discussion and Feedback

Following the product demonstration, meeting participants actively engage in dialogue about the product increment. This immerses them in critical evaluation, enabling them to offer valuable feedback, initiate clarifying questions, and propose potential adjustments for product refinement. This constructive discussion drives continuous improvement and innovation.

Next Step

Step 5: Product Backlog Revision

The product owner takes into account feedback received, infusing it into the product backlog, thus possibly rearranging the sequence of future tasks. Such reshuffling might be driven by insights from past experiences, alterations in the prevailing circumstances or valuable suggestions from stakeholders, fostering continuous improvement.

Next Step

Step 6: Review Conclusion and Follow Ups

In wrapping up the meeting, a comprehensive summary of the arguments presented and decisions made is provided, capitalizing on essential changes promulgated. Planning for the project’s next stage and coordination for any consequent meetings or tasks also form a fundamental part of this conclusion.

Questions to ask as the leader of the meeting

1. What was accomplished during this sprint?
– To understand the progress made and the tasks completed.

2. Was the sprint goal achieved?
– To assess the success of meeting the sprint objective.

3. What challenges did the team face during this sprint?
– To identify any obstacles encountered and take necessary actions to overcome them.

4. Were all user stories done according to acceptance criteria?
– To verify if all the user stories were completed as planned and met the defined acceptance criteria.

5. Did the team face any bottlenecks or dependencies?
– To identify any issues that may have impacted the team’s productivity or progress.

6. Were there any scope changes or requests for additional features?
– To understand if there were any modifications to the original scope or any new requirements added during the sprint.

7. Did the team observe any improvement opportunities or process inefficiencies?
– To gather insights on how the team can enhance their performance and identify areas for improvement in the process.

8. What feedback did the stakeholders provide during the sprint?
– To gather input from stakeholders and evaluate their satisfaction level with the delivered features.

9. Were there any changes in priorities or upcoming deadlines?
– To stay informed about any shifting priorities or impending deadlines that may affect future sprint planning.

10. How can we make the next sprint even better?
– To encourage the team to reflect on the sprint and suggest ways to improve future iterations.

The reasons for asking these questions are to assess progress, identify challenges, ensure adherence to requirements, address bottlenecks and dependencies, evaluate stakeholder satisfaction, gather feedback, detect improvement opportunities, and consider possible changes for upcoming sprints.

As a leader, preparing an agenda for the agile sprint review meeting is crucial. Start by setting clear objectives for the meeting, including what needs to be reviewed and discussed. Next, identify the key stakeholders who should attend and determine the appropriate time frame. Finally, outline the agenda with specific topics, allowing time for feedback and questions. This will ensure a focused and productive sprint review meeting.

How To Prepare For A Agile Sprint Review Meeting
Meeting Preparation Icon

In an agile sprint review meeting, it is crucial to discuss the progress made during the sprint, including any completed user stories or tasks. Focus should also be given to identifying and addressing any issues or challenges encountered, as well as obtaining feedback from stakeholders on the delivered features. This helps to ensure continuous improvement and alignment with project goals.

See Our Agile Sprint Review Meeting Template
Meeting Template Icon

Software tools to facilitate a Agile Sprint Review Meeting

Software streamlines the agile sprint review meeting process for leaders. It facilitates collaboration, tracking progress, and identifying any bottlenecks. With real-time dashboards, leaders can monitor team performance and prioritize tasks effectively. The software helps capture feedback and generate actionable insights, enabling leaders to make informed decisions and drive the team towards successful project completion.

Our Recommendations:


Mastering the art of running an Agile Sprint Review Meeting is an absolute necessity in today’s fast-paced world. It empowers teams to efficiently assess product progression, introspect on achieved deliverables, prioritize future goals, and validate decisions with stakeholders. By focusing on the objectives – clear communication, active involvement, and real-time feedback, teams can stay on track and validates their journey towards achieving their end goals. But remember, the dynamics of every team are different. There isn’t a one-size-fits-all approach, you have to adapt and tweak your meetings based on your unique project needs and team dynamics. Your sprint reviews are a regular rendezvous of learning and adaptability, a consistent platform to grow as a team, refine your processes, and deliver high-value solutions.

Popular Questions

What is the purpose of an Agile Sprint Review Meeting?

The purpose of an Agile Sprint Review Meeting is to inspect the increment of work that has been done during the sprint, receive feedback, and adapt the product backlog for future sprints if necessary. It is a collaborative discussion about what was accomplished during the current sprint and what should be done in the upcoming sprint.

Who should attend an Agile Sprint Review Meeting?

An Agile Sprint Review Meeting should be attended by the Scrum team, which includes the product owner, the Scrum Master and the development team. Also, stakeholders, such as clients, executives and other interested parties, are encouraged to attend to provide feedback.

How long should an Agile Sprint Review Meeting last?

The duration of an Agile Sprint Review Meeting is typically proportional to the sprint length. For a two-week sprint, a review meeting might last around two hours. However, this can be adjusted as necessary. The goal is to ensure that there is enough time to present and discuss the completed work.

What is typically discussed during an Agile Sprint Review Meeting?

During an Agile Sprint Review Meeting, the team usually discusses what was done during the sprint, what wasn’t completed and why, and presents the completed items to the stakeholders for feedback. The product owner also reviews the product backlog and discusses the next possible items for the upcoming sprint.

How is the success of a sprint measured in a Sprint Review Meeting?

The success of a sprint is often measured by whether the team completed the items they committed to in the sprint backlog, the quality of the work, and whether the increment of work meets the ‘Definition of Done’. Feedback from stakeholders is also a crucial element of measuring success.