Skip to main content

what should the SM and the PO do when the stakeholder unhappy

Last post 02:20 pm April 24, 2021 by Ian Mitchell
2 replies
03:14 am April 24, 2021

hi 

I have some question

1-what should the SM and the PO do when the stakeholder unhappy when they sow the Increment in the sprint review ?

2-could the stakeholder see the increment before the sprint review ?

3-Who determines the quality of the product the stakeholder or the scrum team ?and if the stakeholder is not happy when they see the quality what should they do ?

thanks

 

 

 


01:57 pm April 24, 2021

could the stakeholder see the increment before the sprint review ?

There's nothing preventing this. It depends on the relationship between the organization and team building the product and the stakeholder. The role of the Product Owner includes representing all stakeholders to the team and the Product Owner should be working with the rest of the team every day and in regular contact with all of the stakeholders. However, getting feedback directly from stakeholders is best, so maximizing that feedback is probably in the best interests of everyone involved.

 

Who determines the quality of the product the stakeholder or the scrum team ?and if the stakeholder is not happy when they see the quality what should they do ?

The Developers are responsible for building quality into the product, but the stakeholders (through the Product Owner) are responsible for setting what is expected in terms of product and process quality. If the stakeholders do not believe that an Increment has sufficient quality for potential use, then the Scrum Team should enhance their Definition of Done to ensure that all of the work meets the quality expectations and consider any remediations necessary to bring the existing product up to this level of quality as a form of technical debt.

The Scrum Team may enforce higher levels of quality than the stakeholders demand, but cannot produce Increments that are not sufficient for use.

 

what should the SM and the PO do when the stakeholder unhappy when they sow the Increment in the sprint review ?

This is a good opportunity for a discussion. Understand why the stakeholder is unhappy and figure out what the team can do to make them happy. The Product Backlog can be adjusted to work toward an Increment that meets the stakeholders' expectations.


02:20 pm April 24, 2021

1-what should the SM and the PO do when the stakeholder unhappy when they sow the Increment in the sprint review ?

Use the Sprint Review for its intended purpose - a collaborative working session in which the outstanding requirements are better understood. It's an opportunity to get the Product Backlog in the best possible shape for the next Sprint, which will very shortly begin. 

2-could the stakeholder see the increment before the sprint review ?

Would the Developers find this helpful?

3-Who determines the quality of the product the stakeholder or the scrum team ?

The Developers who are doing the work. No-one else is in a position to do anything about it and build the necessary quality in.

and if the stakeholder is not happy when they see the quality what should they do ?

Flag the issue with the Scrum Team as quickly as possible, because Scrum is not being implemented well. Everyone on the team has a relevant accountability to fulfill and will have actions that ought to be taken.


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.