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

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'.

Related videos

Related videos

Spawn an Online Game with Blazor, .NET 7 and Clean Architecture in under 60 minutes | Luke Parker | SSW User Groups

Full Stack Web Developers are commonplace, but what if you were told those very skills can directly translate to building an online game?! 🎮

Master Video Editing Terms with Adam and Eve Cogan | SSW Rules

It’s important for anyone involved to know the basic video editing terms to keep feedback clear and concise.

Boost Productivity: Say Goodbye to Time Wasting with this Simple Trick – No Hello | SSW Rules

Please don’t say just ‘Hello’ in chat. It’s as if you called someone on the phone and said “Hi!” and then put them on hold!

Augmented reality and the future of devices with Richard Campbell and Ulysses Maclaren

Phones have ruled our digital experience for over a decade. But where will we go for information and how will we expect it to be delivered?

Building inclusion into organisations with Sammy Herbert and Penny Walker | NDC Sydney 2022

This session will cover Sammy’s 3-year journey of starting in a small company and building it to become a multi-award winning organisation

The remote revolution with Richard Campbell and Ulysses Maclaren

After COVID the world was forced to exist remotely. Will it be the way all companies move forward into the future of business?

Best way to ask for content changes | Ulysses Maclaren | SSW Rules

When asking for changes to be made to any file like a web page, Word document, PowerPoint slide, or code, always include the original version of the content (“X”) together with the changes you require (“Y”).

Azure on a Budget | Bryden Oliver | .NET User Group

Are you about to embark on a new Azure project? Do you want to know how much it’ll cost to run? And everyone needs to get the cost down on their current project. Right? 💸

Cost cutting with Power Apps and development strategies with Richard Campbell and Ulysses Maclaren

Can we save costs and future proof our products? Let’s use Power Apps and new development strategies.

Running a world class event with Jakob Bradford and Adam Cogan at NDC Sydney 2022

Running events is a challenge. And making sure your speakers and attendees are happy is an even bigger task. Adam and Jakob discuss keeping conferences interesting and adding value to future events.