Back to Forum

Sprint Review & Absences

Last post 06:49 pm April 7, 2023 by Ian Mitchell
2 replies
Vik Kumar
11:28 am April 7, 2023

Hi,

We have SM, PO and Stackholders when doing Sprint Review/demo. Many times, we have a situation when all stakeholders are not available because of absences/holidays/critical activities. What can be the best option:

1- Should we cancel or reschedule the review? We have a review just a day before the sprint completes, so rescheduled review might happen in the next sprint.

2- Can we have a review couple of days before the sprint completes? This way, we might show/discuss those tickets Done already.

3- Can we do multiple reviews in one sprint? This way, we might show/discuss those tickets Done already.

4- Should we ignore stakeholders if the product owner is present for review?

 

Thomas Owens
04:27 pm April 7, 2023

I don't think any of those are appropriate.

There's nothing wrong with getting feedback and information from stakeholders more frequently than once per Sprint. I'd consider 3 to be a viable option, but getting feedback from stakeholders isn't the same as getting all your key stakeholders in the same place at the same time.

Instead, I'd look at the overall scheduling. Look at things like the Sprint duration, the day of week where you hold the Sprint Review, and even the time of day that you hold it. Make the appropriate adjustments to maximize the key stakeholders who attend. However, the Scrum Master should also be working with the key stakeholders to make sure they understand the importance of not only attending, but also participating in the Sprint Review event.

Ian Mitchell
06:49 pm April 7, 2023

Many times, we have a situation when all stakeholders are not available because of absences/holidays/critical activities. What can be the best option

Bear in mind that being invited to a Sprint Review as a stakeholder is a privilege. The Scrum Team are not obliged to invite and accommodate everyone.

If a stakeholder has been invited, it is because they are thought by the team to be key, with respect to the work being reviewed that Sprint. Should a key stakeholder be indisposed to provide feedback at this time, it is best to consider the available options in that light.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.