The document discusses agile estimation techniques, emphasizing the importance of estimating effort and duration in agile projects despite inherent inaccuracies. It advocates for team-based estimation methods, such as Planning Poker, to enhance decision-making, trust, and responsibility among team members. Key strategies include learning from past errors, practicing estimation, and classifying work rather than seeking precise estimates.

1. Agile Estimation TechniquesMikalai Alimenkouhttp://xpinjection.com16.04.2011

2. BackgroundJava Technical Lead/Scrum Master at Zoral Labs6+ years in software development4+ years of working by Agile methodologiesExpert in Agile engineering practicesFounder and coachat XP Injection (http://xpinjection.com)

3. Calculated approximation of a result which is usable even if input data may be incomplete or uncertainThe art of guessing what the amount of time will be for a certain activityGuessing the complexity and duration of a task/feature

4. By definition estimates are inaccurate

5. Do we need estimates in Agile?

6. Time waste

7. No timefor gooddecisions

8. Fear to miss estimate

9. But estimates are useful

10. Better business decisions

11. Select scope for releaseor iteration

12. Healthy discussion

13. Get team commitment

14. Build trustIncreaseresponsibility

15. Spread realistic complexity vision

16. Parkinson’s LawWork expands to fill the time available for doing it

17. Let’s do itAgile way!

18. Think differently…

19. We are really good at comparison

22. Planning Poker

23. Whyitworks?

24. Be careful of anchoring!

25. Team Estimation Game

26. Why Team Estimation Game?

27. Optimize it!

28. Don’t try to estimate everything

29. No 100% agreement?Reduce risks!

30. Classificationinstead of estimation

31. Use other scale

32. Divide work on equal parts

33. How to estimate better?Learn from your failuresPractice, practice, practice!Estimate with other teamsCompare your estimates

34. Apply on personal levelWorking timemanagementPersonal timemanagement

35. How to avoidestimation?

36. Highly motivated and responsible team

37. Team is interestedin product success

38. Product roadmapis scope based

39. is based oncontinuousimprovement

40. Any questions?