Lots of work has been done to understand the role of the ScrumMaster, there has been far less written and said about the role of the Product Owner. Who is this person who is responsible for the ROI of the project? I have tried to create a number of statements that balance the characteristics of the Product Owner.
Characteristics of a Product Owner
Understands thoroughly the needs of the customer YET they understand what it takes to build software
Senior enough to make the decisions YET they are available to the team
Knows when to say no YET they have a good working relationship with stakeholders and the team
Understands how to create value YET they trust the team to get the work done
Understands thoroughly the needs of the customer YET they understand what it takes to build software
The Product Owner is the voice of the customer therefore they must understand thoroughly the needs of the customer. In order to do this they will need to be out talking to customers on a regular basis and have a good understanding of their customers business domain. Yet, the Product Owner needs to have an appreciation of what is involved in technically providing a solution, this is essential to get buy in from the team. Asking the team to do something very difficult in a short amount of time will drive the wrong behaviors out of the team.
Senior enough to make the decisions YET they are available to the team
The Product Owner needs to be empowered to make the decisions about the direction of the project, therefore it is somebody who is trusted by the customer organisation, yet they are available to the team during the Sprint, therefore being Product Owner for the product has to be their day job.
Knows when to say no YET they have a good working relationship with stakeholders and the team
The Product Owner proactively manages the interest of stakeholders and takes advice from the team on dependencies however they are also responsible to ensure priorities are such that the maximum ROI is achieved, therefore they need to be able to say no, yet do it in such a way that everybody understands why the decision has been taken, so that everybody has trust in the Product Owner. The Product Owner needs to be able to take everyone on a journey with them.
Understands how to create value YET they trust the team to get the work done
The Product Owner needs to understand what value the user or customer will get by prioritising one particular feature over another, yet they are not the person who decides how this is technically achieved, they need to trust the team to get the work done, and help the team by providing feedback.