The Product Owner represents the “voice of product stakeholders” to the team and is responsible for creating value that comes from the work of the Development team. This value comes from the work done on clearly defined user-oriented tasks that are important for the creation of the product.
The Product Owner expresses the interest of consumers. Reference: What makes a good Product Owner and what do they do, https://scrumtime.org/what-makes-a-good-product-owner-and-what-do-they-do/
The main responsibilities of the Product Owner role
The main responsibilities of the Product Owner role can be defined as:
- Maintaining an idea and vision of how the product will develop and build
- Ongoing cooperation and communication with stakeholders
- Creating and maintaining a Product Backlog – writing User Stories
- Prioritizing the content of the Product Backlog
- Release management – setting phases and dates for the release of new versions of the product
- Tracking work progress, time, and budget.
Reference: Responsibilities of the Product Owner – Questions and answers, https://brightonbot.com/responsibilities-of-the-product-owner-questions-and-answers/
Scrum does not include the role of Product Manager. This is done by the Product Owner, who is as close as possible to the product manager. He works with stakeholders, represents their interest in the product, and looks for ways to meet their interests and requirements. Reference: What is Scrum and why use this methodology, https://www.businesspad.org/what-is-scrum-and-why-use-this-methodology/
The Product Owner must have product knowledge, must have an understanding of consumers, know their needs, know the market, its features, competition, and follow new trends in the industry in which it operates.
The Product Owner does not take into account the way the teams do their work, does not share technical proposals or specific technical ways of implementation. He is the link between stakeholders and the Development team. Talk to various business representatives, gather information about the next sprints, share the progress of the teams.
When a team member encounters an ambiguity about a task, the Product Owner should be available to assist and share information, details, or an alternative solution for the product. Or it should direct in case of ambiguity. Reference: What is it like to be a Scrum Master?, https://projectmanagers.edublogs.org/2020/09/14/what-is-it-like-to-be-a-scrum-master/
The product owner prioritizes the work
Prioritizing the work means sifting through all these Product backlog items and user stories, from which the Development team can decide which tasks to start with to meet the needs of stakeholders.
Starting with the most important ideas, stakeholders may already be satisfied, and do not see the need to continue working on small tasks.
Therefore, one of the main responsibilities of the Product Owner role is to prioritize the content of the product backlog constantly and regularly, based on many factors.
From all this prioritized Product Backlog, the Development Team in Scrum decides how many tasks it can develop during its Sprint. Reference: Scrum problems, causes of failure and mistakes, phron.org, https://phron.org/scrum-problems/
Logically, the team works on the tasks that are at the top of the list.
Although we can have a lot of planned work, business stakeholders can tell us at any time that we are terminating work on the product. We will likely stop our work because the business is satisfied with the product we have created at some stage. Starting with the most important ideas, stakeholders may already be satisfied, and do not see the need to continue working on small tasks.
What is User Story?
User Stories are the wishes of users or stakeholders that the Product owner shares with the Development team. User Story is an informal and concise description of a consumer need. This is usually a written form that presents the prospect of the potential user of the product regarding its functionality.
The user story describes the user who needs functionality, its context, and goals. Describes the reason why the consumer needs this product. Their need. The user history describes the user who needs functionality, its context, and goals. This may not mean a task, but it can lead to the creation of one. By describing the goals of the user, the Development team can create a task that will satisfy these desires and needs.
The initial activity of the Product Owner role
Before starting work on the product, the Product Owner and stakeholders can work together to create a product vision for the product. The product vision is a collection of information divided into groups. Information is collected about who the real users of the product are, what their needs or expectations are. How the product will be distributed, sales methods, and other market factors. What are the main elements that will determine the price? When all this information is gathered, the Product Vision serves as a basis for creating ideas, concepts, prototypes for the project, as well as its actual production.
What does the value of the work done mean?
Value of work done means creating a product for consumers that is convenient for them to use, useful in work, a product that facilitates their work and brings them some social and professional benefits.
Value of work done for stakeholders means any benefit to them from the product – financial, social, marketing, economic, or others.
The value of the work done for consumers is the creation of a product that is convenient for them to use, useful in work, a product that facilitates their work and brings some social and professional benefits.
Value of work done for the owners means any benefit for them from the product – financial, social, marketing, economic, or others.
- About the BVOP Certified Product Owner, https://bvop.org/productowner/#:~:text=The%20BVOP%E2%84%A2%20Certified%20Product,%2C%20business%20stakeholders%2C%20and%20developers.
- The Product Owner is king, https://www.cio.com/article/3203385/the-product-owner-is-king.html
- Using the Scrum framework as a project management process for product development, https://newia.info/using-the-scrum-framework-as-a-project-management-process-for-product-development/
- Real Scrum problems of the Scrum Master role during the Daily Scrum meeting, https://mpmu.org/scrum-problems-scrum-master-daily-scrum-meeting/
- Comparison between Scrum and Kanban methodologies, https://www.kosovatimes.net/comparison-between-scrum-and-kanban-methodologies/
- The Scrum Master role in real project teams, https://bpedia.org/the-scrum-master-role-in-real-project-teams/
- Reference: Professional Scrum Master vs Professional Scrum Developer, stc-montreal.org, https://stc-montreal.org/professional-scrum-master-vs-professional-scrum-developer/