Who should done PBIs in NExus Sprint Review

Last post 01:34 pm June 11, 2018
by Ching-Pei Li
5 replies
Author
Messages
07:32 am June 8, 2018

Hi all,

I would like to ask a question regarding Nexus Sprint Review. The question is that who should present the PBIs to the stakeholders. As far as i know, The PO is responsible to manage the meeting and collect data from stakeholders. However, the better one is Scrum Team members should present the items to all interested in. What do you think about? You can also see the quotation from @Simon Kneafsey. https://www.thescrummaster.co.uk/scrum/scaled-professional-scrum-nexus-nexus-sprint-review/

It is still the responsibility of the Product Owner to manage the Product Backlog and decide which changes will be accepted and what impact these will have to the ordering the other Product Backlog Items it contains.

As with a Sprint Review, an effective Nexus Sprint Review should be collaborative session to show the new features and functionality that have been created by all the Scrum Teams in the Nexus during the current Sprint.

Let's discuss.

I am really appreciated from now.

06:32 pm June 8, 2018

The Scrum Guide says:

  • The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done";

Do you have any reason to believe that this guidance ought to differ in a Nexus context?

What else does the Scrum Guide have to say about how Sprint Reviews are conducted...and how true is it that the PO “manages” the meeting?

07:14 pm June 8, 2018

Hi Ian,

The question would be like "Who should present the done PBIs(If necessary make a demo) in Nexus  Sprint Review?".PO or representatives from each Scrum Teams? Yes this is a Scrum quotation. However, Nexus includes more items and participated members naturally in Sprint Review. In this case, if PO try to make demo or present all the done items at least, it could be not efficient. 

08:56 pm June 8, 2018

The Product Owner should be able to explain what work has been “Done” and what has not been “Done” at the end of each Sprint. This can be helped by giving a demonstration of certain features but it is not the same thing.

Often, it is most efficient to provide demonstrations throughout the Sprint as work is completed, rather than deferring them to the Review. This also allows for earier feedback and for more inspect-and-adapt opportunities.

01:04 pm June 10, 2018

Hi Ian,

I agree with you regarding making demo is more helpful than review the items. However, i am still wonder about this question. What is the recommendation? Who should present the done PBIs to stakeholders in Nexus Sprint Review? In Nexus perspective, for a 2 weeks sprint, 15 PBIs are released and considered as demo candidate. 

Often, it is most efficient to provide demonstrations throughout the Sprint as work is completed, rather than deferring them to the Review. This also allows for earier feedback and for more inspect-and-adapt opportunities.

By the way have you ever tried this advice before? I think, it is very challengeable issue but worth to try.

 

Best Regards,

07:21 am June 11, 2018

Why do you focus on the "Individual PBIs"?

Nexus-Guide:

A Nexus Sprint Review replaces individual Scrum Team Sprint Reviews, because the entire Integrated Increment is the focus for capturing feedback from stakeholders. It
may not be possible to show all completed work in detail.

Remember that Sprint Review is not a formal meeting for receiving approval from the stakeholders. 
It’s an informal meeting, without exchanging signatures, just aimed at receiving feedback and adjusting the Product Backlog.

"What should be demo" is more important than "Who should present the done PBIs". 
It is the responsibility of the Product Owner.

Just do it as a marketing road show. 
The outcome value is more important than the output features.
The PO decides what features to demo in order to show the outcome value and to collect feedback.
The features choosed by the Product Owner can be presented by representatives from each Scrum Teams or PO. 
Anyway, "Who should present" is not so important.