A Guide to Sprint Review Agendas (Definition and Tips)

By Indeed Editorial Team

Updated November 4, 2022

Published October 8, 2021

The Indeed Editorial Team comprises a diverse and talented team of writers, researchers and subject matter experts equipped with Indeed's data and insights to deliver useful tips to help guide your career journey.

Scrum teams use sprint review agendas to provide stakeholders with information about their work and deliverables. These reviews require stakeholders to provide feedback that professionals then use to adjust their backlog. By having a strong agenda, you can promote the success of your deliverables. In this article, we discuss the definition of sprint review agendas, provide you with information about who attends these reviews, discuss how to attend a review and provide you with several tips to help you succeed.

What is a sprint review agenda?

Sprint review agendas refer to agendas that occur in agile project management. These are informal meetings held following the end of a sprint and allows a Scrum team to present results. These teams discuss new features and aims to create transparency, establish collaboration and generate feedback. Sprint review agendas don't provide status updates to stakeholders. Instead, these professionals ask stakeholders for feedback and adjust their backlog following the meeting. These reviews are Scrum events and inspect the overall product backlog.

Related: How To Run a Sprint Retrospective (With Tips)

Who attends a sprint review?

The members of a sprint review depends on the projects being considered. Generally, these reviews include product owners, the Scrum team, Scrum masters, members of upper management, customers and developers. This provides team members with the opportunity to receive feedback from stakeholders. These stakeholders have the opportunity to inspect and adapt to and reviews that were previously built. These events are also time-boxed and last approximately one hour. They last approximately two hours for two-week Sprints. Here is some more information about sprint review members:

Scrum team

The Scrum team consists of the Scrum Master, Scrum development team and the product owner. These individuals collectively collaborate with stakeholders, answer questions and provide feedback about products. From here, team members make adjustments to accommodate the Scrum team.

Related: Definitive Guide To Scrum Development

Internal stakeholders

The internal stakeholders are those within the organization who have a stake in whether the product or service delivers. These professionals include program managers, along with scrum masters, marketing professions and sales professionals. Business development teams provide feedback to the sprint team through the spring team review.

Related: What Is Scrum Project Management?

External stakeholders

Sprint team reviews typically contain fewer external stakeholders compared to internal stakeholders and Scrum team members. The external stakeholders may include any teams who worked on the product website, along with agents and those who can market the product. This provides the team with information about the product's early life cycle.

Related: 10 Scrum Interview Questions With Example Answers

How to conduct a sprint review

Here is a guide to help you conduct a sprint review:

1. Identify attendees

The first step toward conducting a sprint team review and developing an agenda is to identify which professionals attend the meeting. The Scrum team has mandatory participation, but you may find it beneficial to invite all stakeholders to improve professional relationships and receive affective feedback. This also establishes the acceptance and usage of the delivered product.

2. Send an invitation

When you establish which members to invite to the sprint review, you may find it beneficial to send personalized invitations to these members. These reviews typically occur on the last day of the Sprint, which typically has a consistent duration. For example, sprints that have a duration of two weeks typically require invitations to sprint reviews every two weeks. Consider sending all of your invites simultaneously to ensure stakeholders have a clear schedule planned.

3. Consider whether the work is complete

When creating your agenda, you may find it beneficial to establish whether you completed the anticipated work for the sprint review. If not, include time in your agenda to discuss which components of the project require completion and how this impacted the deliverable. This encourages transparency between you and stakeholders, which improves professional friendships and provides them with a clear idea of what your team accomplished.

4. Prepare for demonstration

You may want to consider how to present the demonstration and whether you plan to do so as a single, cohesive team. This requires you to develop a plan and establish which employees present the product to stakeholders. The Scrum Master, for example, may present the charts and overall velocity of the team. The development team can also present their work and discuss the process used to obtain this work.

5. Executing the review

When you finish preparing for the sprint review, you can then execute the review meeting. Here is an approximate agenda to follow for your sprint review:

Summarize

The first component of your review is to summarize the project. The Product Owner typically does this and provides stakeholders with information about the backlogged items. Product owners also explain the status of particular items. For example, they explain whether the status is "Done" or "Not Done".

Demonstrate

Following the summary of the deliverable, sprint reviews require a demonstration of completed work. During this demonstration, the development team discusses which challenges and obstacles they overcame. This provides stakeholders with a clear image of the development team's ability to find solutions. When stakeholders have questions about any of the completed work items, the development team answers these questions.

Adapt

Finally, the sprint review requires stakeholders to provide the sprint team with feedback about the deliverables. The product owner discusses the product backlog, along with its current status. This professional then provides stakeholders with target dates and general milestones for work that requires completion. The product owner uses the feedback provided by stakeholders to adapt the product backlog and prioritize items effectively.

Tips for creating a sprint review agenda

These reviews provide critical feedback for Scrum. Here are some tips to consider when creating these review agendas:

  • Demonstrate products: When conducting the demonstration, you may want to consider allowing stakeholders to control the demonstration. This provides them with direct experience regarding the product and allows them to better understand the product features.

  • Collaborate with others: You may want to consider how to foster collaboration between the development team and the stakeholders. This promotes project success and allows team members to fulfill needs.

  • Establish organizational skills: Sprint reviews require strong organizational skills to develop agendas and establishing itineraries.

meta

Explore more articles