How to Fail with Agile Kamon Treetampinij
The article Full Article at  http://www.mountaingoatsoftware.com/system/article/file/40/HowToFailWithAgile.pdf   By Clinto...
Management (5) <ul><li>Guideline 1: </li></ul><ul><li>Don’t trust the team or agile.  </li></ul><ul><li>Micromanage both y...
Management (5) <ul><li>Guideline 2: </li></ul><ul><li>If agile isn’t a silver bullet, blame agile. </li></ul>
Management (5) <ul><li>Guideline 3: </li></ul><ul><li>Equate self-managing with self-leading  </li></ul><ul><li>and provid...
Management (5) <ul><li>Guideline 4: </li></ul><ul><li>Ignore the agile practices. They don’t  </li></ul><ul><li>apply to m...
Management (5) <ul><li>Guideline 5: </li></ul><ul><li>Undermine the team’s belief in agile. </li></ul>
Team (4) <ul><li>Guideline 6: </li></ul><ul><li>Continually fail to deliver what you  </li></ul><ul><li>committed to deliv...
Team (4) <ul><li>Guideline 7: </li></ul><ul><li>Cavalierly move work forward from one  </li></ul><ul><li>iteration to the ...
Team (4) <ul><li>Guideline 8: </li></ul><ul><li>Do not create cross-functional teams.  </li></ul><ul><li>Put all the teste...
Team (4) <ul><li>Guideline 9: </li></ul><ul><li>Large projects need large teams. Ignore  </li></ul><ul><li>studies that sh...
Product Owner (4) <ul><li>Guideline 10: </li></ul><ul><li>Don’t communicate a vision for the  </li></ul><ul><li>product to...
Product Owner (4) <ul><li>Guideline 11: </li></ul><ul><li>Don’t pay attention to the progress of  </li></ul><ul><li>each i...
Product Owner (4) <ul><li>Guideline 12: </li></ul><ul><li>Replace a plan document with a plan “in  </li></ul><ul><li>your ...
Product Owner (4) <ul><li>Guideline 13: </li></ul><ul><li>Have one person share the roles of  </li></ul><ul><li>ScrumMaste...
Process (7) <ul><li>Guideline 14: </li></ul><ul><li>Start customizing an agile process  </li></ul><ul><li>before you’ve do...
Process (7) <ul><li>Guideline 15: </li></ul><ul><li>Drop and customize important agile  </li></ul><ul><li>practices before...
Process (7) <ul><li>Guideline 16: </li></ul><ul><li>Slavishly follow agile practices without  </li></ul><ul><li>understand...
Process (7) <ul><li>Guideline 17: </li></ul><ul><li>Don’t continually improve. </li></ul>
Process (7) <ul><li>Guideline 18: </li></ul><ul><li>Don’t change the technical practices. </li></ul>
Process (7) <ul><li>Guideline 19: </li></ul><ul><li>Rather than align pay, incentives, job  </li></ul><ul><li>titles, prom...
Process (7) <ul><li>Guideline 20: </li></ul><ul><li>Convince yourself that you’ll be able to  </li></ul><ul><li>do all req...
The checklist
Q/A
Upcoming SlideShare
Loading in …5
×

How To Fail With Agile

2,336 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,336
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
30
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

How To Fail With Agile

  1. 1. How to Fail with Agile Kamon Treetampinij
  2. 2. The article Full Article at http://www.mountaingoatsoftware.com/system/article/file/40/HowToFailWithAgile.pdf By Clinton Keith & Mike Cohn
  3. 3. Management (5) <ul><li>Guideline 1: </li></ul><ul><li>Don’t trust the team or agile. </li></ul><ul><li>Micromanage both your team members </li></ul><ul><li>and the process. </li></ul>
  4. 4. Management (5) <ul><li>Guideline 2: </li></ul><ul><li>If agile isn’t a silver bullet, blame agile. </li></ul>
  5. 5. Management (5) <ul><li>Guideline 3: </li></ul><ul><li>Equate self-managing with self-leading </li></ul><ul><li>and provide no direction to the team </li></ul><ul><li>whatsoever. </li></ul>
  6. 6. Management (5) <ul><li>Guideline 4: </li></ul><ul><li>Ignore the agile practices. They don’t </li></ul><ul><li>apply to management. </li></ul>
  7. 7. Management (5) <ul><li>Guideline 5: </li></ul><ul><li>Undermine the team’s belief in agile. </li></ul>
  8. 8. Team (4) <ul><li>Guideline 6: </li></ul><ul><li>Continually fail to deliver what you </li></ul><ul><li>committed to deliver during iteration </li></ul><ul><li>planning. </li></ul>
  9. 9. Team (4) <ul><li>Guideline 7: </li></ul><ul><li>Cavalierly move work forward from one </li></ul><ul><li>iteration to the next. It’s good to keep </li></ul><ul><li>the product owner guessing about what </li></ul><ul><li>will be delivered. </li></ul>
  10. 10. Team (4) <ul><li>Guideline 8: </li></ul><ul><li>Do not create cross-functional teams. </li></ul><ul><li>Put all the testers on one team, all the </li></ul><ul><li>programmers on another, and so on. </li></ul>
  11. 11. Team (4) <ul><li>Guideline 9: </li></ul><ul><li>Large projects need large teams. Ignore </li></ul><ul><li>studies that show productivity </li></ul><ul><li>decreases with large teams due to </li></ul><ul><li>increased communication overhead. </li></ul><ul><li>Since everyone needs to know everything, </li></ul><ul><li>invite all fifty people to the daily standup. </li></ul>
  12. 12. Product Owner (4) <ul><li>Guideline 10: </li></ul><ul><li>Don’t communicate a vision for the </li></ul><ul><li>product to the team or to the other </li></ul><ul><li>stakeholders. </li></ul>
  13. 13. Product Owner (4) <ul><li>Guideline 11: </li></ul><ul><li>Don’t pay attention to the progress of </li></ul><ul><li>each iteration and objectively evaluate </li></ul><ul><li>the value of that progress. </li></ul>
  14. 14. Product Owner (4) <ul><li>Guideline 12: </li></ul><ul><li>Replace a plan document with a plan “in </li></ul><ul><li>your head” that only you know. </li></ul>
  15. 15. Product Owner (4) <ul><li>Guideline 13: </li></ul><ul><li>Have one person share the roles of </li></ul><ul><li>ScrumMaster (agile coach) and product </li></ul><ul><li>owner. In fact, have this person also be </li></ul><ul><li>an individual contributor on the team. </li></ul>
  16. 16. Process (7) <ul><li>Guideline 14: </li></ul><ul><li>Start customizing an agile process </li></ul><ul><li>before you’ve done it by the book. </li></ul>
  17. 17. Process (7) <ul><li>Guideline 15: </li></ul><ul><li>Drop and customize important agile </li></ul><ul><li>practices before fully understanding </li></ul><ul><li>them. </li></ul>
  18. 18. Process (7) <ul><li>Guideline 16: </li></ul><ul><li>Slavishly follow agile practices without </li></ul><ul><li>understanding their underlying </li></ul><ul><li>principles. </li></ul>
  19. 19. Process (7) <ul><li>Guideline 17: </li></ul><ul><li>Don’t continually improve. </li></ul>
  20. 20. Process (7) <ul><li>Guideline 18: </li></ul><ul><li>Don’t change the technical practices. </li></ul>
  21. 21. Process (7) <ul><li>Guideline 19: </li></ul><ul><li>Rather than align pay, incentives, job </li></ul><ul><li>titles, promotions, and recognition with </li></ul><ul><li>agile, create incentives for individuals to </li></ul><ul><li>undermine teamwork and shared </li></ul><ul><li>responsibility. </li></ul>
  22. 22. Process (7) <ul><li>Guideline 20: </li></ul><ul><li>Convince yourself that you’ll be able to </li></ul><ul><li>do all requested work, so the order of </li></ul><ul><li>your work doesn’t matter. </li></ul>
  23. 23. The checklist
  24. 24. Q/A

×