Skip to main content

As a SM, how do you deal with a PO who does not want to involve customers/stakeholders in the sprint review?

Last post 11:45 pm January 20, 2025 by Pierre Pienaar
3 replies
05:23 pm January 20, 2025

05:31 pm January 20, 2025

I would first try to figure out why the Product Owner is opposed to involving customers and other stakeholders in the Sprint Review.


05:35 pm January 20, 2025

Find out their reasons. Is there a situation that the PO anticipates and is trying to avoid? 


11:45 pm January 20, 2025

As mentioned above it’s important to first understand the underlying reasons why the Product Owner doesn’t want to involve stakeholders. Once you have that information, you can explain to the Product Owner the importance and value of regular customer feedback. The Sprint Review is the primary opportunity to gather stakeholder feedback and inspect the product increment. By not involving stakeholders, the team risks missing a valuable opportunity to inspect and adapt, and the product and stakeholder expectations might drift apart over time.

 


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.