remove the notion of the PO accepting PBI's
In the section on cancelling a sprint there is the text " If part of the work is potentially releasable, the Product Owner typically accepts it".
This suggests that the PO is the person accepting the work done in the sprint.
Doing so implicitly makes the PO the Boss of the team. If I can accept or reject your work, I am clearly in a power position towards you. This is not in line with the description of the team and the roles, where the PO is *part of* the Scrum Team.
In the rest of the Scrum Guide there is no other notion of the PO accepting or rejecting the work of the team, so I guess, and hope, that this is a 'slip of the pen'.
2 commentsComments are closed
"Doing so implicitly makes the PO the Boss of the team" - rubbish.
Doing so explicitly makes the PO the key decision-maker about whether or not the part-finished work should be included for deployment or not. It's up to the team to convey the level of risk compared to the current quality of the part-complete product, and for the PO to decide go/no-go.
What are you suggesting: that the team can vote on it and deploy something into production without the PO having the final say?
So, we're saying that the Product Owner can present a backlog item for the team to work-on (the team accepts the 'challenge'), and then they can do something completely different with no come-back? Surely the deliverable has to face-up to the original requirement at some point?