Posted in Scrum Roles

Product Owner

‘Responsible for maximising the value of the product resulting from work of the Development Team’ (1)


Be one mind with the sponsor (2)


Vision keeper (2)


Product Owner Responsibilities

Maximising Value

  • how this is done may vary widely across organisations, Scrum Teams, and individuals (1)

Managing the Product Backlog

  • expressing Product Backlog items and ensuring the Development Team understands them sufficiently
  • ordering the items in the Product Backlog to best achieve goals and missions and so it is clear what is to be worked on next
  • transparency of the Product Backlog is ensured and it is visible

Product Owner in the Business

Product Owner is One Person 

  • the Product Owner is one person
  • the Product Owner may represent a committee
  • those wanting to change a Product Backlog item’s priority must address the Product Owner (1)

Stakeholder Mapping (3, pg 178)

  1. With the PO (and identified stakeholders) try and think of every person in the organisation who has a vested interest in the outcome.
    • Where is the money coming from?
    • Who’s job is going to change because of this product?
    • Who might interact with a customer differently as a result of what we are building?
    • Who might be angry if they don’t know what is going on with the product?
  2. Put the following categories on the wall and put each stakeholder inside a category
    • Required for the Sprint Review: these people must inspect and provide feedback on the product increment to enable the Scrum Team to make informed decisions
    • Keep informed of progress: they don’t need to inspect every increment but need to know what progress has been made
    • Monitor: should receive updates periodically (check with them how often they would like these)

Product Owner’s Decisions (1)

  • the entire organisation must respect the Product Owner’s decisions
  • the content and ordering of the Product Backlog makes the decisions visible to all
  • no one can force the Development Team to work from a different set of requirements

Techniques

Product Owner Behaviours

CRACK (2)

  • Committed
  • Responsible (outcome)
  • Authorised (to make decisions)
  • Collaborative
  • Knowledgable (about the business)

Product Owner’s Relationship with the Development Team

Tips from Lyssa Adkins (2)

  • No micromanaging
  • Hold the team to account
  • Show genuine disappointment
  • Be present

References

  1. The Scrum Guide
  2. Coaching Agile Teams by Lyssa Adkins
  3. Fixing Your Scrum by Ryan Ripley and Todd Miller

Explore more Scrum

Scrum Theory Scrum Values Development Team Scrum Master Definition of Done

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s