Can a Product Owner Hold the Development Team Accountable For Lack of Commitment?

And what does it mean for the Scrum Team if this is an issue?

The Scrum Guide (2017) is very clear that the Product Owner must optimize the value of work the Development Team does. But what does this mean exactly? Can a Product Owner hold the Development Team accountable for not keeping their promises? Is this part of the responsibility to optimize the value of the work?

When this is a loaded question, it tells something about how the Product Owner cooperates with the rest of the Scrum Team. Let me explain.

Image by Gerd Altmann from Pixabay

The Product Owner Role

If you consider all mentions of the Product Owner in the Scrum Guide, you notice a pattern. The Product Owner:

• needs to ensure the team understands goals, product domain and scope;
• must have a transparent and up-to-date Product Backlog;
• suggests a Sprint Goal and Product Backlog Items that meet the Sprint Goal;
• negotiates with stakeholders on what to do next;
• decides if and when to release “Done” Product Increments.

In short: the Product Owner needs to ensure the Development Team can work on the…