We’ve converted the ‘Product Owner’ definition from the 2013 Scrum Guide into cartoon form to illustrate the role of a Product Owner in a Scrum team.

(from the 2013 Scrum Guide)
The Product Owner

The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.

The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes:

  • Clearly expressing Product Backlog items;
  • Ordering the items in the Product Backlog to best achieve goals and missions;
  • Ensuring the value of the work the Development Team performs;
  • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
  • Ensuring the Development Team understands items in the Product Backlog to the level needed.

The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.

The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a backlog item’s priority must convince the Product Owner.

For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner’s decisions are visible in the content and ordering of the Product Backlog. No
one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn’t allowed to act on what anyone else says.

Adam Cogan, Chief Architect at SSW and Certified Scrum Trainer, has more tips on his blog:

What does a good Product Owner need to do?

  1. Be available for Sprint ReviewsRetrospectives and Sprint Planning meetings (approximately half a day for these 3 meetings, for each 2 week sprint).
  2. Order the Product Backlog. The important things will be done first, in order to maximize the ROI as the budget will run out one day.
  3. Be available, at least remotely, to unblock a developer if he has questions/impediments. A good PO has a feeling of urgency.
  4. Ideally listen in on Daily Scrums. This is optional but means that the PO will have daily insight into the team’s progress.
  5. Understand Product Backlog Items (PBIs) and be able to explain what they want using Acceptance Criteria. This is the main way that developers and POs sync their understanding of what needs to be done.
  6. Agree on a Sprint Goal for each sprint.
  7. Not influence (or anchor) developer estimates with comments like “this one will be easy” and allow the team to come up with converged estimates.
  8. Respect the Sprint Goal. Understand that the team will only work on things in the Sprint Backlog and don’t expect other things to be done as well. Most things can wait for the next sprint.

Rest of Adam’s post

Take the Quiz!

[WATUPRO 3]

About the speakers

Mr Product Owner

Hello! I'm the Product Owner, It's nice to be featured here on SSW TV :)

If you want to know more about what it takes to be a good Product Owner, check out SSW's 'Rules to Better Product Owners'.

Academy

Related Videos

Do you have playlists & custom thumbnails on your YouTube channel?

See SSW Rules for more: https://www.ssw.com.au/rules/sort-videos-into-playlists https://www.ssw.com.au/rules/video-thumbnails SSW Chief Architect Adam Cogan shows how to categorize your YouTube channel with playlists and custom thumbnails to maximize user engagement. || Subscribe for more content from SSW TV || || Press like and leave a comment below to let us know how we’re doing || Twitter ↴…

Do you use great email signatures?

https://www.ssw.com.au/rules/great-email-signatures SSW Chief Architect and Microsoft Regional Director Adam Cogan shows how to setup professional email signatures with a few clicks of a button using CodeTwo. || Subscribe for more content from SSW TV || || Press like and leave a comment below to let us know how we’re doing || Twitter ↴ https://twitter.com/ssw_tv Facebook…

Get the most out of EF Core by avoiding these common mistakes

Do you know how to get the best performance from your EF Core projects? SSW Senior Software Architect Andreas Lengkeek speaks with SSW Solution Architect Jernej (JK) Kavka about common mistakes on EF Core projects and how to fix them. || Subscribe for more content from SSW TV || || Press like and leave a…

Why developers should build their public profile

SSW Chief Architect and Microsoft Regional Director Adam Cogan gives a bootcamp to developers on why they should build their public profile. Recorded at the opening of SSW Newcastle. Interested in working for us? Get in touch: ssw.com.au || Subscribe for more content from SSW TV || || Press like and leave a comment below…

Chewing The Fat Review – How ROI affects decision making

https://www.ssw.com.au/rules/return-on-investment SSW Chief Architect Adam Cogan reviews Chewing The Fat feedback from the SSW team on Return on Investment (ROI) best practices. He is joined by SSW Solution Architect Jean Thirion. || Subscribe for more content from SSW TV || || Press like and leave a comment below to let us know how we’re doing…

Why you should be making the most of extending your AD

https://www.ssw.com.au/rules/extending-AD Do you know how to make the most of your active directory? SSW Chief Architect Adam Cogan talks with SSW Solution Architect Jean Thirion about how to take advantage of extending AD with Microsoft SharePoint. || Subscribe for more content from SSW TV || || Press like and leave a comment below to let…

Chewing The Fat Review – Allowing multiple options on forms

https://www.ssw.com.au/rules/allow-multiple-options SSW Chief Architect Adam Cogan and SSW Senior Software Architect Piers Sinclair review feedback from the SSW team about allowing multiple options on forms instead of making them choose a single option. || Subscribe for more content from SSW TV || || Press like and leave a comment below to let us know how…

Logging in .NET Core can save you hours when debugging

https://www.ssw.com.au/rules/best-trace-logging SSW Solution Architect JK is a battle scared logging in .NET Core veteran. He shows Andreas Lengkeek his best practices for logging, gathered through his years of experience. When setup correctly, logging can save you hours in those moments when your code don’t run as planned. So take some notes on these best practices…

Do you know when to mock your API?

Sometimes you may not know what the backend technology for your API could be… perhaps it is a serverless Azure Functions App, a Logic App, or even a set of services running in Kubernetes. These questions may take time to answer, but you already made a choice on the frontend technology. You may already have…

The best tool to manage and document your API

Having a documented and discoverable API is fantastic. Your API consumers are able to easily understand and reason about your API to build their own integrations. Azure API Management provides us with everything we need to publish our APIs to the world. We can import one or more OpenAPI Spec docs, Swagger, WSDL, and other…