And so, a Product Owner should not be concerned too much with all the tiny little details.
But you don’t have to be the expert, knowing all the tiny details. Having product, market, customer and domain knowledge is valuable, of course. Somebody who dares to take risks, make mistakes and take ownership. A Product Owner is most of all an entrepreneur. Meaning that a Product Owner is not the most experienced, knowledgable proces or system expert in the company. A Product Owner cares that a team has a velocity, yet he doesn’t care about the actual number or about “optimizing” it. And the Product Owner shouldn’t manage people and resources or Development Team capacity for example. The Product Owner also shouldn’t track and measure team progress. The Product Owner doesn’t create and manage (extensive) project plans such as the Project Initiation Document, Project Plan, Gantt Charts or others. Meaning that a Product Owner is not an Agile Project Manager. Of course, coming up with PBIs is part of the job, but a Product Owner is not a Backlog secretary! Meaning that it is not the Product Owner’s day-job to write User Stories, acceptance criteria or Product Backlog Item (PBI) details all day long. A Product Owner should have clear vision and gather feedback on that vision. A Product Owner shouldn’t collect stakeholder orders. Meaning that a Product Owner is not somebody who visits all the stakeholders, and asks everyone of them what they want. So, what a Product Owner should not do is: In addition to stating what a Product Owner is, let’s also explore what the Product Owner is not.
If you want to learn more about the tasks, accountabilities and authorities of the Product Owner, then check out this article. This also includes inviting the right (key) stakeholders to the Sprint Review, discussing the current status of the Product Backlog, next targets and objectives, likely delivery dates and progress made, during the Sprint Review as well as tracking the total work remaining (at least every Sprint Review) for the Product, creating forecasts and making this information transparent for the stakeholders.
The Product Owner is responsible for Stakeholder Management, in order to align everybody around the product vision and (business) goals and objectives to achieve. This includes activities such as clearly expressing Product Backlog Items, ordering the items in the Product Backlog to best achieve goals and missions and ensuring the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next. 
The Product Owner is also responsible for Product Backlog Management. This also means being responsible for the Return on Investment, Budget, Total Cost of Ownership and the defining, maintaining and sharing of the Product vision for example. The Product Owner is the person who is responsible for making sure that the product delivers as much value as possible. This means that a Product Owner actually owns the product. Maximizing the Value of the Product for customers, users and the organization. To provide visible and sustained support for the product. To provide the resources and authorize the funds for the product. To provide unified direction to the product. To be accountable for the success or failure of the product. Some examples of what a Product Owner should do include: In order to do so, the Product Owner is also responsible for the product vision and for managing the Product Backlog and stakeholders. The way the Product Owner maximizes value, is by continuously making choices about what to built and what not to built in the Product. The Product Owner is one person (not a committee) responsible in the Scrum Framework for maximizing the value. The key responsibility, or the purpose of the Product Owner role is to “maximize the value of the Product”. If you’re having a similar question about the Scrum Master vs the Project Manager, then check out this blog. There is some overlap between the role of Product Owner and the position of Project Manager, however, being a Product Owner is very different from being a Project Manager. In this blog, we’ll dive deeper into the topic: “Product Owner vs Project Manager”. Before we dive into an overview of the differences between a Product Owner and a Project Project Manager, let’s start with the conclusion first, which is: The Product Owner is not an Agile Project Manager. What is a Product Owner? What are the differences between a Product Owner and Project Manager? Isn’t a Product Owner some kind of an Agile Project Manager? These are some of the questions we often get from people in our classes. Product manager vs product owner professional#
Search Professional Scrum Certificate Holders.Professional Scrum with User Experience.Professional Agile Leadership - Evidence-Based Management.
0 kommentar(er)
