Few practices on Agile Estimation

1. Estimation - Thoughts Scrum Master Prasad Prabhakaran

4. Iteration planning

5. Release planning

6. Summary

9. Ideal days Estimate size & derive duration

11. Influenced by how hard it is ? & How much there is?

12. Relative values are what is important , for eg: login screen is a 2,search feature is 6

13. Points are unit less

14. On order of magnitude

15. Clue is determine complexity factor ( for eg: due to requirement and technology)

17. It is easier to estimate in ideal time than in ‘actual ‘/ ‘elapsed’ time, because need to consider all the factors that affect elapsed time at the same time you are estimating.What is your office timings? What is your focus factor?

19. Three levels of planning Release plan -> Product back log Sprint / iteration plan -> Sprint back log Daily plan -> Daily Scrum / stand up meeting

24. Availability of team members

25. What is the ‘focus factor’ ( from history, Available days ÷ Story points completed

26. Velocity - use historical, very difficult in initial sprints, forecast it. best in range, total number of story points can be completed in a sprint

29. Many Tasks leading up to the objectives

30. Relative value should be used for estimating - story points

31. Absolute value for tasks

32. Estimate product back log items during release / product planning

33. Estimate tasks during sprint planning meetings

35. Q &A Thanks