Intro to Scrum (11 of 16): What is the Sprint Review?

What is the Sprint Review?

Is a Sprint Review needed for every Sprint? Who should attend? What should we have ready for this Event? What is the Sprint Review? In this vlog, I’m going to go over what the Scrum Guide definition is and what that all really means to you.

Never miss a post.

Sign up now and receive updates when we post new content.

I will never give away, trade or sell your email address. You can unsubscribe at any time.

The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to the key stakeholders, and progress towards the Product Goal is discussed.

During this event, the Scrum Team and the stakeholders review what was accomplished during the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next.

The Product Backlog may be adjusted to meet new opportunities. The Sprint Review is a working session, and the Scrum Team should really avoid limiting it to just a presentation.

The Sprint Review is the second to last event in a Sprint, and it is time-boxed to four hours as a maximum in a one-month Sprint. Usually, it is shorter with shorter Sprint lengths.

So, that’s it for the Sprint Review. There’s not a lot in the Scrum Guide about this event. It’s not super prescriptive on exactly how this meeting goes, or who would facilitate such an event, what kind of stakeholders you bring into this meeting, so you’ll have to do your best on that.

If all of this information about Scrum is interesting to you and you’d like to learn more, please join us in one of our Applying Professional Scrum courses, Professional Scrum Master courses, or Professional Product Owner courses. If you have any other questions, feel free to contact us.

Robert Pieper

Robert Pieper has been a licensed Professional Scrum Trainer since 2014 and National Public Speaker since 2013. Robb holds an MBA from Marquette University and an Electrical Engineering Degree from Milwaukee School of Engineering. Robb has 15 years of professional software development experience with a passion for making Scrum work delivering real products and services
Filed Under: ,
Tagged with: ,