Skip to main content

How will our Sprint Review be structured in this scenario?

Last post 05:31 pm September 30, 2021 by Marvin Ynte
4 replies
08:26 am September 29, 2021

So one of our items in the DoD is that once a PBI has undergone development, testing and code review, we will demo it to our stakeholders and deploy it right away in production. I personally find this very neat and collaborative. Having said that, how will our Sprint Review be structured now? Since they are already familiar with the items developed and release, what would you suggest that we discuss in this event? I'm thinking of getting the CSAT from our stakeholders. What do you guys think?



09:31 am September 29, 2021

The critical output of a Sprint Review is an updated Product Backlog. Since a good Sprint Review ought to be a workshop to that effect, how might that shape things?

12:22 pm September 29, 2021

Although the product is inspected, the primary output of the Sprint Review is a revised Product Backlog that reflects the current needs of the stakeholders. If you're continuously inspecting the product throughout the Sprint, then you can focus on other things that influence the state of the Product Backlog - how the product is being used, who the key stakeholders and users are (if there are changes), who the customers are, changes in the competitor landscape, timelines, budgets, changes to the team's capacity or ability to do work. By discussing topics like these and synchronizing, the Product Backlog can be revised to best reflect how the team can deliver the most value to the stakeholders in upcoming Sprints.

02:45 pm September 29, 2021

This is from the current Scrum Guide section that explains the Sprint Review

During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.

I don't see how your situation would change anything for the Sprint Review.  All of the work that has been deployed to production constitute changes in their environment and accomplishments in the Sprint.  There is still a need to collaborate on what to do next. 

The only real impact of your current practice is that the Sprint Review can spend more time focusing on the Product Backlog and what to do next

05:31 pm September 30, 2021

Thanks for all your inputs guys!

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

Please note that the first and last name from your 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. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, 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 may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.