Does PO who knows only business and not technical should be part of Sprint Demo

Last post 04:28 pm January 19, 2020
by Eric Naiburg
9 replies
Author
Messages
10:00 am January 16, 2020

Hi,

 

This sprint ,we didnt has any increment of the feature that was developed.

Team developed some enhancements which are useful for the development team.However ,PO can't understand as he knows only business.

Does the PO who is a Business user should be called for the demo.

Thanks,

Kavitha 

 

 

 

02:15 pm January 16, 2020

You (or others) might want to ask why the Product Owner has allowed funding of a sprint that didn't produce an increment.

02:40 pm January 16, 2020

How did the development team's work impact the key value areas of the product (current value, unrealized value, ability to innovate, or time to market) ? 

The Product Owner should still understand the benefit of what is being created as it relates to the overall success of the product and be able to speak to that in a Sprint Review. 

If there's something that can be demonstrated or collaborated around the dev team can always take that piece if it's beyond the understanding of the PO. 

03:23 pm January 16, 2020

I am going to point out something which you may not like.

Isn't PO the team member? What made you think that the PO understands only business and doesn't know the value of what has been created? Maybe I am getting it wrong, but I have encountered far too many scenarios like this, where one or the other member/group of the team thinks that they know it all. Do you think that by not inviting PO for a demo (actually PO is the one who should make the formal invitations for Sprint Review to appropriate stakeholders) are you following core values of Scrum which includes Openness and RESPECT?

Secondly, was the enhancement you are referring to was prioritized? If not, what was the reason the development team did not choose the PBIs which had a high priority for the development? 

04:09 pm January 16, 2020

Kavitha,

From the Scrum Guide:

The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. 

Do you believe that this key responsibility was adhered to in this sprint?   More to the point, why do you believe you are still following Scrum if the Development Team is developing items that the Product Owner doesn't understand?

 

04:21 pm January 16, 2020

This sprint ,we didnt has any increment of the feature that was developed.

Team developed some enhancements which are useful for the development team.However ,PO can't understand as he knows only business.

That sounds like an increment to me.  It is providing value to the Development Team and in this case they are the primary stakeholders.  However the PO is also responsible for maximizing that the work the Development Team does is producing value.  The PO made a decision to order these items high enough in the Product Backlog to be taken into a Sprint and they dedicated the Sprint to providing value for the Development Team.  I am assuming that these changes make it easier for the Development Team to add to and update the code base which in turns leads to the ability for them to provide features with less friction and possibly faster.  There is the business value which you seem to think the Product Owner doesn't understand. 

Does the PO who is a Business user should be called for the demo.

I am hoping that you are not referring to the Sprint Review as "the demo" and will answer as though you are not since the Sprint Review is so much more than a demo. What harm would it do to demo the work that was done to the Product Owner?  As part of that demo the developers can explain how the work that was done is providing value. 

05:46 pm January 16, 2020

Team developed some enhancements which are useful for the development team.However ,PO can't understand as he knows only business.

 

@Kavitha Kantheti, It sounds to me like you just paid back on your technical debt. Is this made transparent to the PO?

 

Does the PO who is a Business user should be called for the demo

In short yes, the PO should be invited and should attend the Sprint Review or the demo as you call it.

Unrelated to your concern about the technical experience/knowledge of the PO but, Don't you think Business users who would actually be using the product be the best kind of stakeholder at this meeting so that you can get feedback regarding what you just built? For example: If you built a scientific calculator app and your end user is a college student, do you think it would matter to the student how you wrote the code or what the quality of the code is? What do you think would really matter to the student? 

As long as the PO understand the value of re-paying technical debt, wouldn't you still consider they need to have a technical acumen?

06:16 pm January 16, 2020

This sprint ,we didnt has any increment of the feature that was developed.

How will the team inspect and adapt, using the evidence of this Sprint, so product value will be maximized?

01:23 am January 18, 2020

Hi All, 

Thanks a lot for all the replies.Many of you were trying to answer from the standard scrum which is very good.

 

We need to understand the project picture as well .The PO is a business user .We all know that leadership is key in supporting these intitaives.The leadership has agreed to only 1 PO for all the four Scrum teams and PO protrizes the requirements and for multiple releases.The US are taken accordingly in the Sprint .To backfill PO, we do have BA support as well.

In this scenario, I feel PO is not required as the increment done is to fasten the delivery of a feature.

 

Having said that, the invite has to be sent to PO too so that he can decide if he would like to come or not.

 

Thanks,

Kavitha

 

04:28 pm January 19, 2020

@Kavitha, have you ever been in a situation where you create requirements for someone else to build and the once you saw the actual product you had feedback, concern or general ideas around it?  Also, if the Product Owner isn't at the Sprint Review, how do they hear what they stakeholders are saying about what they are seeing?  The entire idea of a Sprint Review is to provide and capture feedback about the work performed during the Sprint and as the whole product comes together.  If the PO is absent, they are not only not getting the feedback, they are not providing it.  The PO is absolutely needed to be at the Sprint Review.