What is a Product Owner?
Product Owner definition
Scrum defines three accountabilities:
- the Scrum Master,
- the Developers and
- the Product Owner.
The Product Owner is responsible for increasing the value of the product in the development process and is responsible for the Product Backlog and Product Goal.
In practice, he is often the one who represents the technical viewpoint and acts as the contact person for the developers. Among other things, he formulates requirements for the desired solution and assesses development progress based on functionality, usability and quality.
The tasks of the Product Owner
According to the current Scrum Guide 2020 the Product Owner has the following four tasks:
- Developing and explicitly communicating the Product Goal;
- Creating and clearly communicating Product Backlog items;
- Ordering Product Backlog items; and,
- Ensuring that the Product Backlog is transparent, visible and understood.
In addition, the Scrum Guide states that the Product Owner
- may delegate the above tasks, but he is responsible for them.
- is responsible for maximising the value of a product through the work of the Scrum Team.
- represents the needs of the stakeholders, but changes to the Product Backlog will only be made if he, as the responsible person, is convinced of them.
- is the person with whom the scope can be clarified in a sprint and, if necessary, renegotiated in an ongoing sprint as soon as new insights become available.
- has the authority to cancel a Sprint.
- ensures that the participants in Sprint Planning are prepared and able to discuss the most important Product Backlog Items on the way to the Product Goal.
- suggests in Sprint Planning how the product could increase its value and utility in the current Sprint.
- participates in the Daily Scrum as a developer and therefore as part of the Scrum team.
- supports the developers in sizing the items in the Backlog Refinement if required
- is a person and is not a group or committee.
In order for the Product Owner to work successfully – according to the Scrum Guide – the whole organisation has to respect his decisions, which can be seen through the content and order of the Product Backlog Items, as well as the Increments at the end of the Sprints.
Further activities in practice
In addition to the tasks in the Scrum Guide, there are also practical activities that often fall within the Product Owner’s field of activity, such as
- the regular communication with stakeholders, and thus also the promotion and representation of their needs.
- the responsibility for releases and release plans. Whether the roadmap of the product to be created is his responsibility or that of the Scrum Team depends on the context.
- the clarification of Backlog Items in the Sprint Review, which have been completed or are still open (which should not be presented as such).
- agreeing the Sprint Goal with the Developers and clarifying the User Stories to be implemented.
In addition, it is often the technical contact person for the Scrum Master and the Developers and should be available regularly and ideally also at short notice for questions.
In practice, there are always discussions about whether the Product Owner has the overall responsibility for the product and is responsible for the success of the product and, in the end, for marketing, sales, development, operation and support. It is advisable to consider the specific context of an organisation and to find a common understanding of the responsibilities, tasks and roles, especially since in many organisations it would already be a success if representatives of the above-mentioned areas participated in the Sprint Review.
What is a Product Owner NOT?
It is important to understand what a Product Owner is NOT:
- He is not the project manager – he does not exist in this form in Scrum.
- He is not the superior of the Developers – due to the self-determined approach of the Scrum Team, which is based on the principles of the Agile Manifesto and the promotion of self-management in the Scrum Guide, there is no such leadership role.
- He is not the moderator in various Scrum events such as the Daily Scrum.
He can, but does not have to be a manager in the line organisation; what is important is the ability to represent the stakeholders in a technically competent way. In principle, the Scrum Master should intervene if necessary and ensure that the accountabilities defined in the Scrum Guide are observed. In order to avoid possible conflicts of interest, the Product Owner should not have a double function as Scrum Master or Developer.
It is often claimed that the Product Owner as a representative of the users is responsible for the formulation of User Stories. This is not the case. Apart from the fact that it is context-dependent which elements are managed in the Product Backlog, it is ultimately secondary who formulates them. The responsibility for the Product Backlog and the Product Goal lies with the Product Owner, but most importantly it is important that users and developers understand each other. The Product Owner must make his contribution to this. How he does this depends on the situation. And how well he does it can be discussed in Retrospectives.
Product Owner Certification
There are two acknowledged Product Owner certificates:
- Certified Scrum Product Owner (CSPO), offered by the Scrum Alliance¹
- Professional Scrum Product Owner (PSPO), offered by Scrum.org²
Just like the distinction between the Certified Scrum Master (CSM) and the Professional Scrum Master (PSM), the main difference between the CSPO and the PSPO is the type of certification. To obtain the CSPO certificate, a training course – conducted by a Certified Scrum Trainer (CST) or a Certified Enterprise Coach (CEC) with a subsequent test – is required. The PSPO certificate does not require any training, only the passing of a test.
After the CSPO or PSPO there are further levels for certified product owners:
- Advanced Certified Scrum Product Owner (A-CSPO), offered by the Scrum Alliance
- Professional Scrum Product Owner II + III, offered by Scrum.org
Like all certificates of the Scrum Alliance, the CSPO must be recertified every two years. At Scrum.org there is no such requirement.
Is the Product Owner based in the business department or in IT?
Does the Product Owner come from the business department or IT? In many companies there are considerations as to where the Product Owner should be located. Most organisations prescribe the role (and also the accountability) – if not provided by the external client – in the business department. Depending on the context, however, the answer may vary: if, for example, the organisation is a corporate group or is undergoing an agile transformation, the Product Owner may also come from IT, for example to guarantee the ongoing operation and security of a solution. But even in such a situation, the business department must “set the direction” and the IT department must ensure that everything “necessary” is taken into account, because only then is the “customer focus” above the “system focus”. In the sense of continuous improvement, it can also make sense to raise such and similar issues in organisations again and again and continuously search for the best individual solution.
Download the Product Owner Checklist for free now.
With the checklist, you record various information that is essential for the Product Owner’s work:
- What is the product goal?
- Who are the most important stakeholders, what are your goals and how are they reviewed during the development process?
- How do you work with backlogs?
- How and by whom are efforts estimated?
- How does the cooperation with the Scrum Master and the developers work?
Checklist as working tool for Product Owners.
Impulse to discuss:
Not only the Product Owner should talk to stakeholders, but also team members are encouraged to exchange information with users, for example. From the stakeholders’ point of view, how does this work if they have numerous contacts?
By the way, the LeSS Huge Framework knows Product Owner Teams.
Here you can download a Scrum Whitepaper.
Here you will find additional information from our blog: