Product Owners:  Five Mistakes  That Make Your Project  #fail Nils Weisensee
What's this about? “ He is most powerful who has power over himself ” Seneca ( Roman philosopher)
“ Many people fall because they are  afraid of letting go” Lisa Weisensee (German rock climber )
Who? [email_address] <ul><ul><li>Background in Media Studies, Political Science & International Journalism </li></ul></ul>...
Topics  <ul><ul><li>Lack of Priorities  </li></ul></ul><ul><ul><li>Lack of Planning </li></ul></ul><ul><ul><li>Lack of Pro...
Mistake #1 Lack of Priorities Do everything at once!
Mistake #1: Lack of Priorities <ul><ul><li> Don't prioritize only by gut feeling or intuition </li></ul></ul><ul><ul><li>...
Mistake #1: Lack of Priorities <ul><ul><li> Don't prioritize only by gut feeling or intuition </li></ul></ul><ul><ul><li>...
Mistake #2 Lack of Planning Surprise your team with new ideas in the middle of the sprint!
Mistake #2: Lack of Planning <ul><ul><li> Ideas are good, but sometimes have to wait </li></ul></ul><ul><ul><li>Don't dis...
Mistake #3 Lack of Product Vision Change direction  as often as possible!
Mistake #3:   Lack of Product Vision <ul><ul><li> No clear vision for your product? Urgh.  </li></ul></ul><ul><ul><li>Lac...
Mistake #3:   Lack of Product Vision <ul><ul><li> No clear vision for your product? Urgh.  </li></ul></ul><ul><ul><li>Lac...
Mistake #4 Lack of Presence Get an office on the top floor!
Mistake #4:   Lack of Presence <ul><ul><li>Problems: Lack of physical or intellectual presence </li></ul></ul>
Mistake #4:   Lack of Presence <ul><ul><li>Problems: Lack of physical or intellectual presence </li></ul></ul><ul><ul><li>...
Mistake #5 Lack of Trust Make your team work harder!
Mistake #5: Lack of Trust <ul><ul><li>Pressuring the team will backfire </li></ul></ul><ul><ul><li>Lack of testing and ref...
Conclusions <ul><ul><li>Don't be afraid of letting go where the team should function on its own </li></ul></ul><ul><ul><li...
Thanks for listening! <ul><ul><li>Which mistakes did you make? </li></ul></ul><ul><ul><li>What lessons did you learn? </li...
Upcoming SlideShare
Loading in …5
×

Product Owners: Five Mistakes That Make Your Project #fail

2,592 views

Published on

Presentation at Shanghai Scrum Forum 2010 by Nils Weisensee, CSPO at The NetCircle, Shanghai.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,592
On SlideShare
0
From Embeds
0
Number of Embeds
41
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Product Owners: Five Mistakes That Make Your Project #fail

  1. 1. Product Owners: Five Mistakes That Make Your Project #fail Nils Weisensee
  2. 2. What's this about? “ He is most powerful who has power over himself ” Seneca ( Roman philosopher)
  3. 3. “ Many people fall because they are  afraid of letting go” Lisa Weisensee (German rock climber )
  4. 4. Who? [email_address] <ul><ul><li>Background in Media Studies, Political Science & International Journalism </li></ul></ul><ul><ul><li>Worked as web designer & online consultant </li></ul></ul><ul><ul><li>Did fun stuff totally unrelated to software </li></ul></ul><ul><ul><li>Joined The NetCircle as Community Manager in Shanghai (they build social networking software) </li></ul></ul><ul><ul><li>Did more fun stuff unrelated to software </li></ul></ul><ul><ul><li>Became Certified Scrum Product Owner at The NetCircle </li></ul></ul>
  5. 5. Topics <ul><ul><li>Lack of Priorities </li></ul></ul><ul><ul><li>Lack of Planning </li></ul></ul><ul><ul><li>Lack of Product Vision </li></ul></ul><ul><ul><li>Lack of Presence </li></ul></ul><ul><ul><li>Lack of Trust </li></ul></ul>
  6. 6. Mistake #1 Lack of Priorities Do everything at once!
  7. 7. Mistake #1: Lack of Priorities <ul><ul><li> Don't prioritize only by gut feeling or intuition </li></ul></ul><ul><ul><li>Don't let the team do your work in the Planning Meeting ____________________________________________ </li></ul></ul><ul><ul><li>Prioritize by business value and risk  </li></ul></ul>
  8. 8. Mistake #1: Lack of Priorities <ul><ul><li> Don't prioritize only by gut feeling or intuition </li></ul></ul><ul><ul><li>Don't let the team do your work in the Planning Meeting ____________________________________________ </li></ul></ul><ul><ul><li>Prioritize by business value and risk  </li></ul></ul><ul><ul><li>Fail fast and reiterate </li></ul></ul>
  9. 9. Mistake #2 Lack of Planning Surprise your team with new ideas in the middle of the sprint!
  10. 10. Mistake #2: Lack of Planning <ul><ul><li> Ideas are good, but sometimes have to wait </li></ul></ul><ul><ul><li>Don't disrupt the team because your ideas are running late </li></ul></ul><ul><ul><li>Disruptions have a price: Lower quality, delayed deployment </li></ul></ul><ul><ul><li>If a story change affects the estimated points, don't do it </li></ul></ul>
  11. 11. Mistake #3 Lack of Product Vision Change direction as often as possible!
  12. 12. Mistake #3: Lack of Product Vision <ul><ul><li> No clear vision for your product? Urgh. </li></ul></ul><ul><ul><li>Lack of consistency in product vision? Confront the client! Realize the costs of disruption! </li></ul></ul>
  13. 13. Mistake #3: Lack of Product Vision <ul><ul><li> No clear vision for your product? Urgh. </li></ul></ul><ul><ul><li>Lack of consistency in product vision? Confront the client! Realize the costs of disruption! </li></ul></ul><ul><ul><li>Agile flexibility is useless if efficiency is lacking </li></ul></ul>
  14. 14. Mistake #4 Lack of Presence Get an office on the top floor!
  15. 15. Mistake #4: Lack of Presence <ul><ul><li>Problems: Lack of physical or intellectual presence </li></ul></ul>
  16. 16. Mistake #4: Lack of Presence <ul><ul><li>Problems: Lack of physical or intellectual presence </li></ul></ul><ul><ul><li>Risks: Questions not asked during sprint,  team members assume leadership </li></ul></ul><ul><ul><li>But: PO presence does not mean PO interference! </li></ul></ul>
  17. 17. Mistake #5 Lack of Trust Make your team work harder!
  18. 18. Mistake #5: Lack of Trust <ul><ul><li>Pressuring the team will backfire </li></ul></ul><ul><ul><li>Lack of testing and refactoring, more bugs to fix later </li></ul></ul><ul><ul><li>Nobody hates fixing old code more than your developers </li></ul></ul><ul><ul><li>Trust the team. If they say it's a 20, don't argue </li></ul></ul>
  19. 19. Conclusions <ul><ul><li>Don't be afraid of letting go where the team should function on its own </li></ul></ul><ul><ul><li>Know which tasks cannot be delegated </li></ul></ul><ul><ul><li>Be available when needed, but don't disturb </li></ul></ul><ul><ul><li>Trust your team </li></ul></ul>
  20. 20. Thanks for listening! <ul><ul><li>Which mistakes did you make? </li></ul></ul><ul><ul><li>What lessons did you learn? </li></ul></ul>Nils Weisensee   [email_address]

×