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

Azure Resource Naming Conventions with Luke Cook

Having inconsistent resource names across projects creates all sorts of pain:
– Struggling to identify resources
– Unsure what to label new resources.
– Risk of duplicating resources

Developing Flexible Authorization Capabilities in ASP.NET Core with Jason Taylor

In this talk, Jason Taylor will demonstrate an approach using permission-based authorization to overcome these limitations by building a flexible approach to managing roles and permissions from within your system. This will improve the maintainability and visibility of access control across your system. Putting the power into the hands of application users and administrators, rather than developers.

SSW 2022 Welcome Back To Office Lunch

On the 4th of February we welcomed everyone back to the office with a fantastic lunch! 🥗

It has been a roller coaster 12 months with restrictions, so it was amazing to see everyone back in the office working side by side again 👏

Tech News: State of JS Survey 2021, AU domains available, GitHub issues changes, .NET 7 preview

Join Adam as he delivers the latest Tech News during our March User Group.

SSW is proud to announce its latest product – The SSW TimeBand!

Our development team spent a few months working really hard on this new product, and Chief Architect Adam Cogan is officially launching it today.

Rules to Better Security with Adam Cogan – The 10 tips CEOs Must Know

Do you know the security best practices for both end-users and SysAdmins?

Join Adam for the 10 tips CEOs must know for both end-users and SysAdmins.

Microservice Solutions with Ocelot on Azure with Patrick Zhao

Learn from Patrick how valuable Ocelot is and see the ins and outs of building an API gateway and protect the services using Azure VNet.

Searching Outlook Effectively with Ulysses Maclaren

Some people are really good at using Outlook search to find the emails they need, while others have a hard time. Searching for emails can be a real struggle, sometimes you want to find emails from months ago but you aren’t sure exactly what to search for.

Taming GitHub – Notification Hell 🔥 with Adam Cogan and Luke Parker

Notifications from GitHub can be quite a pain, as they send a lot of emails. This leads to many developers ignoring the important emails they receive.

Every client deserves a Team! Link Microsoft Teams with your CRM eg. Dynamics 365, SalesForce

Do you link your customers in CRM to their respective Teams?

Microsoft Teams is a great solution for organizing client files and conversations. Create a new Team for each of your clients, and if you have multiple projects for one client, use Channels to keep them separate.