Product Owner Dos and Don’ts

DO

  1. Say what needs to get done.
  2. Challenge the team
  3. Get interested in building a high-performance team.
  4. Practice business-value-driven thinking.
  5. Protect the team from outside noise.
  6. Incorporate change between sprints.

Don’t
  1. Say how to do it or how much it will take.
  2. Bully the team
  3. Focus on the short-term deliveries only.
  4. Stick to the original scope and approach “no matter what.”
  5. Worry the team with changes that might happen, until they become real.
  6. Allow change to creep into sprints.

Advise from  Lyssa Adkins

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros...
Read more