Total pageviews

Monday, May 29, 2017

What does the Product Owner need to know?




Many times the PO importance may be disposed In relation to other scrum actors. If that happen, the project fatally won't be successful. In this text I will give you 5 tips that will contribute to your success as Product Owner in a project.


1 - Trust is the key

The PO has the business knowledge but may not have enough technical knowledge to argue with the development team about certain issues.

Also, the development team might suggest to the PO some changes in the backlog that can accelerate the production.

In this scenario, considering that you have a pro efficient team, the best thing to do is hear their feedback and trust their judgment.


2 - The PO's job is to serve the team

The ultimate goal of development is to launch an excellent product in time. The PO should try to be available and respond as soon as possible to the team's questions.

If the team is working with 2-week (10-day work) Sprints, imagine that if there is an impediment that paralyzes work for 1 day it may mean that 10% of the time available for work has been thrown away.

3 - Users perspectives are essential

Is essential for the Product Owner to understand people that are going to use the product. The better the understanding about the end user is, better will be the product's direction, its functionalities and it's business rules. Nothing is more important than the time spent to understand the end user.

Although it seems difficult, the goal is to achieve the best balance between what you know about the product needs and what represents value for users.

4 - Sometimes the team fails

Even if the team is very productive in a successful sprint, this doesn't mean that necessarily the same thing will happen in the next sprint. The ups and downs in a development process are normal, unpredictable and can happen due to various internal or external factors.

The truth is that the fail or success of a sprint is not as important as the team capability to deliver value for the customer. So there is no reason to despair if not all the stories are approved at the end of the sprint.

Scrum teams are always trying to improve on each sprint. The Product Owner must trust the team and be aware that failure may occur because the team decided to test new techniques or set a very ambitious goal.

5 - The Product Owner and the Project Manager are different

The Product Owner must not try to carry the world in your arms. That's impossible!

The PO doesn't need to worry about schedule, resources allocation or how the team plans the sprint. His job is to define priorities and answear the team's needs.

To let the team self-organize and trust their way of work will save time and make things easier to both sides.

Give a damn