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 Reviews, Retrospectives 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

Just Say Yes or No! 3 Tips for Better Communication | Adam Cogan | SSW Rules

When someone asks you a simple question, do you give a straight answer or jump into explanations?
In this video, SSW’s Adam Cogan shares 3 practical tips for communicating clearly and handling feedback professionally.
Discover why starting with a direct “Yes” or “No” avoids confusion, how acknowledging mistakes builds trust, and why becoming defensive or sarcastic only makes difficult conversations worse.

Whether you’re working with clients, colleagues, or your team, these small changes can help you communicate with confidence, take ownership, and keep conversations productive.

Want to be a better consultant? Master the art of managing up | Adam Cogan | SSW Rules

Want to become a better consultant and accelerate your career? Stop bringing problems to your manager and start bringing solutions!

Join SSW’s Adam Cogan in the beautiful city of Strasbourg, France, as he shares practical tips on managing up, a skill that helps you become more proactive, build trust with your manager, and make better decisions.

Adam explains why presenting options with a clear recommendation is far more effective than simply asking your manager what to do. Using real-world consulting examples, he demonstrates how to evaluate resource decisions, communicate your preferred solution, and help managers make faster decisions.

You’ll also discover how to manage up when you’re CC’d on an important email. Instead of waiting for your manager to ask for advice, learn how to proactively draft a suggested response, share your expertise, and save valuable time.

Whether you’re a developer, consultant, architect, or team leader, these simple habits can help you take ownership, demonstrate initiative, and grow professionally.

Takeaway: Don’t just identify the problem. Present the options, recommend the best one, and explain why.

Tick and Flick! 3 tips for better Sprint Reviews | Adam Cogan | SSW Rules

Want better Sprint Reviews? Adam Cogan shares 3 practical tips to keep your reviews short, engaging, and valuable. Learn how to use the “tick and flick” approach, involve stakeholders, and turn feedback into action.

Vibe Coding is fast, but is it Enterprise Ready? | Adam Cogan | SSW Rules

Vibe coding is transforming software development, allowing developers to build features in minutes instead of days. But does faster coding mean better software?

In this SSW TV episode, Adam Cogan explores the excitement and hidden challenges of AI-powered development. Using a Formula 1 analogy, he explains why speed alone isn’t enough when navigating the complexities of architecture, security, testing, and maintainability.

Discover how enterprise vibe coding, or AI-assisted engineering, combines the speed of AI with the right architecture, context, and guardrails to build reliable, maintainable software.

🚀 Enjoy the speed, but don’t forget the corners!

Microsoft Teams Etiquette: Simple Habits That Make Meetings Better | Adam Cogan

Whether you’re working remotely or in the office, small habits can make a huge difference in Microsoft Teams meetings.

Treat Your Code Like Uranium | Adam Cogan

Adam Cogan shares a striking story comparing two World War II factories—one ordinary, one handling uranium—and the surprising lesson that the uranium workers lived longer because they followed disciplined, risk-aware practices. He connects that idea to software teams: the best outcomes come from careful habits like automated tests, telemetry, pull requests, retrospectives, shared rules, and good tools. The message is simple: treat software delivery with the same respect as dangerous work, and you’ll reduce stress, avoid chaos, and get better results.

3 Tips for Better Video Recordings | Adam Cogan

Great coaching can dramatically improve how you present, communicate, and learn. In this video, Adam Cogan shares 3 practical coaching tips that SSW uses every day—from onboarding and role plays to improving video delivery. He explains why having a coach matters, why immediate interruption beats delayed feedback, and how repeating corrections helps lock in better habits.

TinaCMS + Fumadocs: Bring Visual Editing to Your Docs | Hark Singh

Discover how to connect Playwright with AI agents and unlock powerful workflows.

Stop Using 👍 Wrong in Teams | Adam Cogan

A quick communication tip from Adam Cogan: don’t use 👍 as a catch-all response when someone assigns you a task in Teams, Slack, or Google Chat. In the example Adam gives, if a task will take about five minutes, a thumbs up is too ambiguous because it does not clearly say whether you’ve read it, agree with it, are doing it now, or will do it later. Instead, use 👍 for agreement, 👀 to show you’ve seen the task and are actively working on it, and then replace 👀 with ✅ once the task is done. It is a small change, but it removes ambiguity and cuts down unnecessary follow-up messages.

How to record a done video in SSW | Sylvia Huang | SSW Rules

Sylvia Huang from SSW shares her SSW Cultural Exchange experience from Hangzhou, China to Australia