Our last article covered the Perfect Development Agenda. Now we will start with the first To Do list: the Product Owner’s.
There are four To Do’s when it comes to the Product Owner’s involvement in Perfect Development in ScrumOne:
- Take care of the Product Backlog (including additions, removals, reprioritization and fine-tuning at her/his own discretion).
- Consult with Stakeholders on future requirements.
- Create a development strategy for product delivery.
- Cooperate with the Developers on required User Story clarification.
Take care of the Product Backlog (including additions, removals, reprioritization and fine-tuning at her/his own discretion).
Things can and do change all the time. New information is obtained from the team or the Stakeholders. Changes happen all the time, so taking care of the Product Backlog is a continuous job.
Consult with Stakeholders on future requirements.
The Product Owner is responsible for understanding the customer's priorities and wants and working with customers to clarify expectations. Therefore, the Product Owner should be in regular and close contact with the Stakeholders during the development process to discuss the requirements and their priority.
Create a development strategy for product delivery.
The Product Owner is responsible for creating the development strategy and updating it (if necessary). This does not mean that the Product Owner will determine the individual technical solutions. That is in the hands of the Developers.
Cooperate with the Developers on required User Story clarification.
If there are any questions from Developers regarding User Story clarification, the Product Owner should be able to answer them. If the Product Owner does not know the answer, he or she should be able to find someone who could provide the answer. It’s all about communication. It is not a problem if the Product Owner cannot react immediately. It is a problem if he or she does not react at all.
And what’s on the Scrum Master’s To Do list in Perfect Development? You will read about it in our next article.
Thank you for reading!