Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Agile Estimation Techniques<br />Mikalai Alimenkou<br />http://xpinjection.com<br />16.04.2011<br />
Background<br />Java Technical Lead/Scrum Master at Zoral Labs<br />6+ years in software development<br />4+ years of work...
Calculated approximation of a result which is usable even if input data may be incomplete or uncertain<br />The art of gue...
By definition <br />estimates are inaccurate<br />
Do we need <br />estimates <br />in Agile?<br />
Time waste<br />
No time<br />for good<br />decisions<br />
Fear to miss estimate<br />
But estimates are useful<br />
Better business decisions<br />
Select scope for release<br />or iteration<br />
Healthy discussion<br />
Get team commitment<br />
Build trust<br />Increase<br />responsibility<br />
Spread realistic <br />complexity vision<br />
Parkinson’s Law<br />Work expands to fill the <br />time available for doing it<br />
Let’s do it<br />Agile way!<br />
Think differently…<br />
We are really good at comparison<br />
Planning Poker<br />
Why<br />it<br />works?<br />
Be careful of anchoring!<br />
Team Estimation Game<br />
Why Team Estimation Game?<br />
Optimize it!<br />
Don’t try <br />to estimate <br />everything<br />
No 100% agreement?<br />Reduce risks!<br />
Classification<br />instead of estimation<br />
Use other scale<br />
Divide work on equal parts <br />
How to estimate better?<br />Learn from your failures<br />Practice, practice, practice!<br />Estimate with other teams<br...
Apply on personal level<br />Working time<br />management<br />Personal time<br />management<br />
How to avoid<br />estimation?<br />
Highly motivated <br />and responsible team<br />
Team is interested<br />in product success<br />
Product roadmap<br />is scope based<br />
is based on<br />continuous<br />improvement<br />
Any questions?<br />
Upcoming SlideShare
Loading in …5
×

Agile Estimation Techniques

16,656 views

Published on

Presentation from Agile Base Camp conference (Kiev, April 2011) about estimation techniques in Agile teams.

Agile Estimation Techniques

  1. 1. Agile Estimation Techniques<br />Mikalai Alimenkou<br />http://xpinjection.com<br />16.04.2011<br />
  2. 2. Background<br />Java Technical Lead/Scrum Master at Zoral Labs<br />6+ years in software development<br />4+ years of working by Agile methodologies<br />Expert in Agile engineering practices<br />Founder and coachat XP Injection (http://xpinjection.com)<br />
  3. 3. Calculated approximation of a result which is usable even if input data may be incomplete or uncertain<br />The art of guessing what the amount of time will be for a certain activity<br />Guessing the complexity and duration of a task/feature<br />
  4. 4. By definition <br />estimates are inaccurate<br />
  5. 5. Do we need <br />estimates <br />in Agile?<br />
  6. 6. Time waste<br />
  7. 7. No time<br />for good<br />decisions<br />
  8. 8. Fear to miss estimate<br />
  9. 9. But estimates are useful<br />
  10. 10. Better business decisions<br />
  11. 11. Select scope for release<br />or iteration<br />
  12. 12. Healthy discussion<br />
  13. 13. Get team commitment<br />
  14. 14. Build trust<br />Increase<br />responsibility<br />
  15. 15. Spread realistic <br />complexity vision<br />
  16. 16. Parkinson’s Law<br />Work expands to fill the <br />time available for doing it<br />
  17. 17. Let’s do it<br />Agile way!<br />
  18. 18. Think differently…<br />
  19. 19. We are really good at comparison<br />
  20. 20.
  21. 21.
  22. 22. Planning Poker<br />
  23. 23. Why<br />it<br />works?<br />
  24. 24. Be careful of anchoring!<br />
  25. 25. Team Estimation Game<br />
  26. 26. Why Team Estimation Game?<br />
  27. 27. Optimize it!<br />
  28. 28. Don’t try <br />to estimate <br />everything<br />
  29. 29. No 100% agreement?<br />Reduce risks!<br />
  30. 30. Classification<br />instead of estimation<br />
  31. 31. Use other scale<br />
  32. 32. Divide work on equal parts <br />
  33. 33. How to estimate better?<br />Learn from your failures<br />Practice, practice, practice!<br />Estimate with other teams<br />Compare your estimates<br />
  34. 34. Apply on personal level<br />Working time<br />management<br />Personal time<br />management<br />
  35. 35. How to avoid<br />estimation?<br />
  36. 36. Highly motivated <br />and responsible team<br />
  37. 37. Team is interested<br />in product success<br />
  38. 38. Product roadmap<br />is scope based<br />
  39. 39. is based on<br />continuous<br />improvement<br />
  40. 40. Any questions?<br />

×