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

Humans as a Space Faring Civilization | Richard Campbell & Ulysses Maclaren

Join SSW’s General Manager, Ulysses Maclaren in an engaging interview with Arafat Tehsin, an AI MVP with Microsoft, as they delve into the realm of AI beyond chatbots. Arafat shares insights into his innovative project tackling parking sign confusions using multimodal AI. From leveraging Microsoft Project Florence to experimenting with OpenAI’s GPT-3.5, Arafat unveils the journey of building a solution that integrates images and text seamlessly. Discover how advancements in AI are revolutionizing mobile and web app experiences, gamification, personalized recommendations, and even video analysis.

SSW FireBootCamp Journey to become a .NET developer (Story 2) | Jeoffrey Fischer & Isaac Lombard

Hear firsthand from SSW’s graduates about their learning journey with FireBootCamp.

Efficient Task Management with Microsoft Loop Tutorial | Tanya Leahy | SSW Rules

Discover how to streamline your task management with Microsoft Loop! In this video, Tanya Le, the Operations Coordinator at SSW, demonstrates how to create a shared, real-time workspace that you and your boss can edit together. Perfect for those unexpected calls from busy bosses. Learn step-by-step how to set up and use Microsoft Loop within Microsoft Teams, making it accessible anytime, anywhere. Don’t miss this essential productivity tip!

The importance of annual reviews for developers | Adam Cogan & Ulysses Maclaren | SSW Rules

Join SSW’s Chief Architect, Adam Cogan and SSW’s General Manager, Ulysses Maclaren as they discuss the importance of annual reviews for Software Developers, emphasizing the must-haves and the “icing on the cake”. Learn about key metrics, from billability to mentorship, and discover how to balance essential tasks with additional contributions to make the most out of your annual review.

SSW FireBootCamp Journey to become a .NET developer (Story 1) | Ella Smith & Josh Berman

Looking to get started into the software industry but struggling with the ‘experience required’ dilemma? Hear firsthand from SSW’s graduates about their learning journey with FireBootCamp, SSW’s internship program available in Australia, China and France. Discover how they gained valuable experience, learned essential soft skills, and thrived in a supportive environment alongside senior developers. Get inspired to level up your skills and jumpstart your career with FireBootCamp!

Talk before emailing – are you gold or silver? | Adam Cogan & Andrew Harris | SSW Rules

In this interview, SSW’s Chief Architect Adam Cogan sits down with SSW’s Solution Architect Andrew Harris to discuss the importance and evolution of the “As per our conversation” SSW Rule in email communication. They discuss the importance of confirming conversations, the challenges some face in following it, and the value it brings to any business communication. Join the conversation and share your insights in the comments!

Cloud Native Aspirations with .NET Aspire | Matt Wicks and Rob Pearson | SSW User Group

This session focuses on .NET Aspire’s capabilities and the multi-platform versatility of .NET 8.

Feature Management Simplified: A Deep Dive into Feature Boards | Matt Wicks & Lars Klint

Join SSW’s Solution Architect Matt Wicks as he dives into the world of feature management with Microsoft Azure MVP, Lars Klint, at NDC Sydney 2024. Explore the innovative approach of feature boards, shifting the responsibility from developers to product owners. Discover how feature toggling transcends the binary realm and adapts to dynamic audience segmentation. With insights into audience providers, SDK usage across multiple languages, and seamless integration into development pipelines, this conversation uncovers a new era of feature management.

Unlocking Domain-Driven Design: Exploring Contextive | Gert Marx & Chris Simon

In this video, join Gert Marx, SSW Solution Architect, as he interviews Chris Simon, Start up CTO Coach, about his open-source project, Contextive. Contextive is inspired by Domain-Driven Design (DDD) principles, particularly focusing on the ubiquitous language aspect. Chris explains how miscommunication between developers and users can lead to issues in software projects, and how Contextive aims to mitigate this by documenting domain terminology.

Navigating Coding, Deployments, and Legacy Projects | Matt Wicks & Ben Dechrai

Join SSW’s Solution Architect Matt Wicks in this interview with Developer Advocate, Ben Dechrai, at NDC Sydney. They explore the world of coding, deployments, and legacy projects as they discuss strategies for managing deployment debt, the importance of keeping infrastructure and code in sync, and navigating through legacy codebases. Learn practical tips for maintaining code cleanliness and optimizing readability, along with valuable insights on levering cognitive complexity to elevate code quality.