Sprint Review is an opportunity to inspect the product and adapt the Product Backlog. That is why it’s essential to have stakeholders, customers, or end users in your Sprint Review.
However, many teams conduct Sprint Reviews just for the team itself and don’t invite anyone outside of the team. This defeats the whole purpose of this meeting.
Let’s review the usual reasons for why stakeholders might not be in your Sprint Reviews and what you can do about it:
- The team doesn’t feel comfortable to have someone else to attend.
- You don’t know who to invite.
- Stakeholders are too busy to attend.
Watch the video to learn more about these reasons and what you can do to help your team succeed.
Sprint Reviews are essential for your success!
Don’t take Sprint Reviews lightly. Your stakeholders have a role to play in the Scrum implementation – provide frequent feedback about the work done.
Chase them. Send them emails. Provide additional training. Help them understand why they are important.
In my previous video, I discuss what to do if you don’t have anything Done by the end of the Sprint. One thing you shouldn’t do is to cancel your Sprint Reviews. Learn why and what to do instead in my previous blog post.
You will need to work with your team, including the Product Owner, to build a strong foundation for your product’s success.
Run awesome meetings and “Wow!” your managers with your knowledge by getting one of the essential guides from my store. You can find a variety of topics, from facilitating retrospectives, to creating a Defintion of Done. I share real-life examples and actual working templates for you to use.
And if you are looking for more guidance and support on your Scrum journey, I invite you to join us at Mastering Scrum Pro community of practice. Ask questions, share experiences, get actionable plans to resolve a challenge you are facing. I’m there!
