Agile Patterns: Estimation - Stephen Forte | FalafelCON 2014
•
0 likes•603 views
The document discusses agile estimation techniques. It defines estimation as "the calculated approximation of a result which is usable even if input data may be incomplete or uncertain." Traditionally, estimates become an unbreakable schedule where any deviation is seen as bad. However, agile estimation throws this logic away and always re-estimates a project after each iteration. Using techniques like user stories, story points, planning poker, and velocity, agile estimation embraces the uncertainty in estimates and sees deviations not as failures but as opportunities for more accurate estimations.
Recommended
Recommended
More Related Content
Similar to Agile Patterns: Estimation - Stephen Forte | FalafelCON 2014
Similar to Agile Patterns: Estimation - Stephen Forte | FalafelCON 2014 (20)
More from FalafelSoftware
More from FalafelSoftware (13)
Recently uploaded
Recently uploaded (20)
Agile Patterns: Estimation - Stephen Forte | FalafelCON 2014
- 1. Making Agile Es-ma-on Work Stephen Forte @worksonmypc
- 2. I’m Steve
- 8. Es-ma-on Defined (sort of) “Es$ma$on is the calculated approxima$on of a result which is usable even if input data may be incomplete or uncertain.” • Problem — Wikipedia is that es.mates become a unbreakable schedule, where any devia.on is considered bad
- 9. The Es-ma-on Problem • When you come up with a project idea, your first es.mate is off by +/4x • Not enough details are known • Tradi.onally too much .me is spent on building a specifica.on which is not complete • Again, not enough details are known • As .me progresses, more details emerge about the system and its details • The cone of uncertainty
- 10. The Cone of Uncertainty 4x 2x 1.5x 1.25x 1.0x .8x .67x .5x 25x
- 11. Agile Es-ma-on • Es.ma.on is uncertain by defini.on! • Problem is that es.mates become an unbreakable schedule, where any devia.on is considered bad • Agile Es.ma.on throws this logic away and always re-‐es.mates a project aIer each itera.on • Different value system, devia.ons are not devia.ons, they are more accurate es.ma.ons • Uses the cone of uncertainty to your advantage
- 12. How to Es-mate
- 13. User Stories
- 14. Story Points
- 15. Planning Poker
- 16. Product Backlog
- 17. Velocity
- 18. Re-‐es-ma-on
- 20. Reading List Books we have read and recommend: • User Stories Applied by Mike Cohn • Agile Es0ma0ng and Planning by Mike Cohn • Agile Retrospec0ves by Esther Derby and Diana Larsen
- 21. Ques-ons?