I can only assume that organizations think that a Product Owner is no more than a functional project manager. They can’t be more wrong. The PO role is as explicit as its name is : the owner of the product. Nobody (not even the CEO) should be able to tell him what to do on the product. The stakeholders should only be able to try to persuade or convince him. The PO must have 3 traits to be an effective PO (in addition with his skills):
- The business skills
- The availability
- The mandate
The PO must know…
There are 4,5 events in Scrum :
The last event is not described -in the Scrum Guide (SG)- as a proper event, but as a good practice inside the description of what a Product Backlog is. But, in my opinion, this is a very important event and I will explain why.
(I wrote this article using “he/his” pronoun, but it definitively work with every gender).
A PM (for me and for some of job description I‘ve read) is someone who bears the responsibility of the well going of a project. He manages the project. This means that he is responsible of the reporting, the risks management, the requirements analysis, the planning management and the comprehension and respect of objectives by the team. This also means that he manages the team. He is responsible of the staffing, of the assignments, of the individuals and collective performance. The team has to answer positively…
After 10 years in web development and facilitating, I finally decided that I mainly wanted to focus on coaching others on Agile mindset.