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
It takes more to be a great coder than you might think! Check out this video from NDC Sydney featuring Adam Cogan, Michael Smedley and Matt Goldman on the importance of teamwork and good communication in software development. Learn about SSW’s new mobile app and how it connects us with the software development community.
Pragmatic DevOps It’s easy to feel like DevOps is too hard to implement because the theory is hard to apply in their company. Rather than give up, it’s important to be pragmatic and try to solve the problems. To do this effectively, you need the theory. With books like The Phoenix Project and The Unicorn…
New features of C#8.0 SSW’s Andreas Lengkeek talks with ‘the C# guy’ Filip Ekberg on the new features of C# 8.0 and what’s coming down the line. They discuss: – Nullable Types – Async Streams – Pattern Matching – Coming up features
Explore the impressive new features on docs.microsoft.com with Brendan Richards and Dan Fernandez. Docs.microsoft are awesome… and now have code samples that run! See how the magic happens via Azure containers that provide interactive docs that execute .Net code samples and Azure CLI operations in real-time. Also, hear behind-the-scenes stories on how one documentation site…
Remote procedure calls (RPC) have been around since the beginning of time – most of them never copped a speeding ticket! Many of us have lived through XML-RPC – SOAP – .NET Remoting – WCF – JSON-RPC and most recently – REST. Back in 2015 Google threw their hat into the ring with gRPC, promising…
NDC was one of our highlights for 2019! NDC hosted so many great presenters including some of our very own developers. The release of the SSW Rewards app was also a great success with so many on the show floor taking part in the SSW Treasure Hunt.
“Hey Dev, stop for a Sec… it’s not all about Ops!” Admit it! Ever since you adopted DevOps, things are spinning way faster than you thought they would. Tools are taking care of the CI/CD process, an APM platform gives you insights into issues in production, and you are fully focused on your code. Having…
Quick analysis of the Cambridge Analytica scandal currently facing Facebook.
Office 2019 will only work on Windows 10 + what’s the difference between an MSI and Click To Run? | Adam Cogan
Office 2019 will only work on Windows 10. We also cover Windows installer technologies; what’s the difference between an MSI and Click To Run?
This is not the same container 101 talk you’ve seen a dozen times. The point of this talk is how to ship a container to production, once you’ve built it. We’ll containerize a .net core app, debug locally, set up continuous deployment, set up a container cluster and deploy to it.