Modern Product Ownership

One of the most critical roles in Scrum is the Product Owner.  When I consult with organisations about Scrum, often they want me to focus on helping the person in this role.

Some PO's are full time, however most PO's I meet are part-time.  They already have a job.  They are unsure how much time this additional role will take.  They know their business but they often do not know Scrum.

More importantly they often do not understand how short iteration development should work.  Lots of the books and blogs say glib comments like 'The PO should manage the product backlog in order to maximize the ROI of the product

Sounds great, but how?  Is putting the Product Backlog in order enough?  No.

Good Product Ownership means an understanding of Scrum, why it works, and a number of complimentary techniques.  For example what techniques should I use for prioritisation? 

  • Moscow
  • Kano
  • Business Value
  • Risk
  • Walking Skeleton
  • Validated Learning
 How much should I spend writing User Stories? (hint: probably not much)

Release Planning is worth a separate blog post entirely but this is another key area for a PO to understand and spend time planning.  Many PO's like to use a story mapping approach to build a product backlog and create a release plan.  Story Mapping is an essential technique that all PO's should understand.

The Lean Start up movement is also a rich source of ideas that are finding their way into a modern PO's toolbox.

So next time someone asks you to be a PO.  Ask yourself - do I understand how to use these techniques to extract the maximum value from my Scrum team?

Would you like to understand the principles of modern Product Ownership?  Are you struggling with how to get the most value from your Scrum team?  We have Professional Scrum Product Owner training that can help.  See our current list of public courses here or ask for private training at

No comments :

Post a Comment