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?
- Be available for Sprint Reviews, Retrospectives and Sprint Planning meetings (approximately half a day for these 3 meetings, for each 2 week sprint).
- 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.
- Be available, at least remotely, to unblock a developer if he has questions/impediments. A good PO has a feeling of urgency.
- Ideally listen in on Daily Scrums. This is optional but means that the PO will have daily insight into the team’s progress.
- 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.
- Agree on a Sprint Goal for each sprint.
- Not influence (or anchor) developer estimates with comments like “this one will be easy” and allow the team to come up with converged estimates.
- 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.
Take the Quiz!
About the speakers
Mr Product Owner
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…
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…
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…
Consumers are very picky when it comes to choosing their favourite API. They don’t appreciate boring pages that lack images, colour and style. Branding your API Portal is important to make your organization and API stand out in the market. By adding some excitement to your API Portal (as well as a properly documented API)…
SSW Chief Architect Adam Cogan takes us through the latest news from the tech industry. 0:00 Introduction 0:24 Windows event invitation https://www.microsoft.com/en-us/windo… 0:54 Windows 11 rumours https://www.techradar.com/au/news/win… 3:22 Meat company pays hacker ransom https://www.smh.com.au/world/north-am… 4:10 World Wide Web inventor auctions internet history NFT https://arstechnica.com/tech-policy/2… 5:10 Visual Studio Code update https://code.visualstudio.com/updates… || Subscribe for more content…
Does setting up logging do your head in? Join JK, a battle scared logging in .NET Core veteran, as he attempts to reduce your headache. Dissolve an aspirin, dim the lights, and let JK soothe your head. In this talk, you will learn easily from JK’s past trials and errors and get straight into setting…
In this lightning talk William Liebenberg covers his favourite features of Azure API Management such as the Developer Portal, Policies and Analytics and how easy it is for you to start using them to secure and monitor your own APIs. He will also highlight where Azure API Management becomes really difficult to manage and how…
SSW Solution Architect Bryden Oliver explains how to create Bicep templates, how to add Managed Identities and he’ll walk us through his new GitHub Repo, “Biceps of Steel”. Bryden is a Solution Architect with over 25 years professional experience. He has a wealth of knowledge from a diverse range of areas but with particular focus…
Is your code exposing valuable secrets for anyone to see? SSW Solution Architect Bryden Oliver shows us how to store our secrets using Azure Managed Identities so your code is safe and secure. SSW.Rules | Do you store your secrets securely? Bryden is a Solution Architect with over 25 years professional experience. He has a…
Looking for a low code custom Power BI chart option? SSW Solution Architect Prem Radhakrishnan takes us through the Charticulator visual, now integrated within Power BI desktop and AppSource. SSW.Rules | Do you always choose the right visual for your reports? Prem is a Solution Architect at SSW and brings over 12 years of enterprise…