What is responsibility or involvement of stakeholder in Sprint review

Last post 03:24 pm March 9, 2017
by Ian Mitchell
5 replies
Author
Messages
03:33 am January 17, 2017

Hi All !

Sprint review writes as below. However, I see these below are all of responsibility and involvement of scrum.

Could you share me "What is responsibility or involvement of stakeholder in Sprint review" in these below ?

Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
 The Product Owner explains what Product Backlog items have been “Done” and what has
not been “Done”;
 The Development Team discusses what went well during the Sprint, what problems it ran
into, and how those problems were solved;
 The Development Team demonstrates the work that it has “Done” and answers questions
about the Increment;
 The Product Owner discusses the Product Backlog as it stands. He or she projects likely
completion dates based on progress to date (if needed) ;
 The entire group collaborates on what to do next, so that the Sprint Review provides
valuable input to subsequent Sprint Planning;
 Review of how the marketplace or potential use of the product might have changed what is
the most valuable thing to do next; and,
 Review of the timeline, budget, potential capabilities, and marketplace for the next
anticipated release of the product.

06:24 am January 17, 2017

The last three items requires stakeholder's involvement

12:37 pm January 17, 2017

The Product Owner explains what Product Backlog items have been “Done” and what has
not been “Done”;
The Development Team demonstrates the work that it has “Done” and answers questions
about the Increment;

07:16 pm January 17, 2017

If key stakeholders have been invited by the Product Owner, it will be their responsibility to maximize the opportunity by:
a) inspecting the increment, and
b) providing timely, focused, and good quality feedback about product value.

11:54 am March 9, 2017

Hi @Ian Mitchell, will you allow the stake holders to continuously be changing the design and scope of the product? Will it not cause detriment to the MVP?

I am experiencing an issue where a BA was assigned as a proxy PO, but I can see that the Stakeholders involvement she is doing is more related to the BA requirement gathering process, rather than what you recommend on your reply above:

If key stakeholders have been invited by the Product Owner, it will be their responsibility to maximize the opportunity by: 
a) inspecting the increment, and 
b) providing timely, focused, and good quality feedback about product value.

Let me have your comments please.

 

Carlos

 

03:24 pm March 9, 2017

> will you allow the stake holders to continuously be changing

> the design and scope of the product?

The Product Owner must have authority over product scope, including the work described on the Product Backlog. That means balancing and moderating stakeholder demands so that the value of each product increment is maximized. All stakeholders must respect the Product Owner's decisions in that regard.