close button
Power up your meetings in seconds.

Record and transcribe meetings
Get shareable meeting summaries
Meeting recaps to stay prepared
Sprint Review Meeting Agenda

Sprint Review Meeting Agenda

Sprint review meetings are conducted at the end of every sprint cycle as a recap of the sprint. The main purpose of the Sprint Review meeting is to identify opportunities for improvement. In this article, we deep dive on agenda for the meeting and how to prepare for a successful discussion.

Sprint review meetings are conducted at the end of every sprint cycle as a recap of the sprint. In a typical sprint review meeting, the developers informally present the work they completed in the sprint and gather feedback from the group. Similarly, the scrum master conducts a retrospective of the sprint and facilitates discussion to identify opportunities for improvement.

Attendees of sprint review meetings should include the scrum master, development/tech team, and business teams - product owners, designers, and data, analytics team. The scrum master should facilitate each sprint review meeting.

Here, we have put together an agenda to help you conduct a productive sprint review meeting.

What should you include in the sprint review meeting agenda?

Scrum masters often modify agenda that suits their team the best, however, an effective review meeting agenda should include the following three topics:

1. Review sprint goal

2. Review completed tasks

3. Sprint retrospective  

Review sprint Goal

Kick-off the sprint planning meeting by reviewing the goals of the completed sprint. These goals or objectives are usually derived from the sprint stories prioritized in the last cycle. The purpose of each sprint is for the teams to have a potentially shippable product, feature, or campaign in the end.  

Completed Tasks

After reviewing the goals of the completed sprint, summarize the team’s accomplishments. Refer to the sprint board and go over the list of tasks completed. Now is a good time for the engineering team to conduct demo presentations. The presentation can be informal but should clearly outline the completed tasks, including newly added features and bugs fixes or updates to existing features. The demo should also discuss how these improvements tie back to each sprint story.  The story owners/business teams can also leverage this time to ask clarifying questions and ensure that the completed task meets the criteria of acceptance and specifications outlined in the initial story.  It is common for the business and development teams to iterate based upon the feedback during sprint demos.

The demo portion of the meeting is also an excellent mechanism to celebrate a successful sprint cycle. This keeps the teams connected and builds morale.  

Sprint Feedback/Retrospective

This part of the meeting has nothing to do with the completed tasks. This agenda item is dedicated to the sprint planning process and performing a retrospective on the completed sprint cycle to outline “what worked well?” and identify opportunities for improvement.

Facilitate the discussion by creating a sprint retrospective board and asking the stakeholders to take a few minutes to pen down their feedback for the completed sprint. You were the sprint story owner and did not get a chance to connect with the engineer to answer clarifying questions? -  Now is the right time to share this feedback. This is a great platform for the team to come together and identify opportunities for improvement for a smoother sprint cycle.