What does a product owner?
What tasks are typically involved?
- Responsibility for the budget of a project
- regular measurement of the entrepreneurial activity through Key Performance Indicators (KPI`s)
- The product owner develops the product roadmap from the product vision
- create the product backlog with the development team
- Fill the backlog with Epics, user stories, and tasks
- prioritize the individual elements in the backlog
- Decision about the acceptance of the user-storys-epics etc.
- Formulating simple and easy to understand entries in the backlog
- be available for further inquiries
- regular contact with stakeholders
What does a working day look like?
As a Product Owner the working day is characterized by the rhythm of the Scrum iterations; besides the daily stand-ups the preparation for the next Estimation, Planning or Review Meeting. As a PO has many stakeholder meetings, you should schedule your day in such a way that you can be available for questions from the development team in one half of the day and then plan the other half for meetings with stakeholders.
When a new product vision is agreed upon with the customer so that it can be realized, it is then added to the product backlog as a product roadmap by the PO (Product Owner). The individual epics, user stories, and tasks are then prioritized and written in as easy to understand a way as possible in the backlog. Together with the team of developers and the Scrum master, each individual story or epic is then estimated based on effort and time. The Po participates in the Daily every day to be available for possible questions and to watch the progress of the sprint. This allows the Po to include any additional customer requests in the sprint.
It is also important to regularly consult with stakeholders in order to improve the product or implement changes to the product in the backlog. The TOE must also always include the business side in its work. He or she is responsible for the budget of the project. At the end of the day the TOE should be informed about the current status of the project in order to take necessary actions. Possible difficulties should also be documented in order to discuss them in the Daily.
What are the specifics to be considered?
Since the job of a PO is not a training profession, prospective Product Owners should exchange a lot with experienced Product Owners. The role is often misunderstood. If you think you have to be a “boss”, you will soon realize that this is out of place in agile project management. A lot is at stake here in terms of communication and organization.
A PO must always have the needs of the customer in mind. Observation of the market is also relevant to the project.
As a PO, one should avoid cross-management. The Daily is no place for a status report!
Communication skills are of great importance for the PO, because often he is in the situation to make the customer understand the meaning of agile working. This requires sufficient empathy and sensitivity in dealing with people.
Social Media
https://www.instagram.com/vollcom_digital/
Vollcom Digital GmbH
Thierschstraße 34, 80538 München
info@vollcom-digital.de
