Range estimation in Scrum
•Download as PPT, PDF•
3 likes•2,530 views
Presentation by OpenSource Connections consultant Arin Sime at Agile2010 conference on how to incorporate range estimation techniques into Scrum.
![Building a more accurate burndown Using Range Estimation in Scrum Agile 2010 Conference August 2010 Arin Sime 434 996 5226 [email_address]](https://image.slidesharecdn.com/rangeestimation-100804064906-phpapp01/85/range-estimation-in-scrum-1-320.jpg)
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Range estimation in Scrum
Similar to Range estimation in Scrum (20)
More from OpenSource Connections
More from OpenSource Connections (20)
Recently uploaded
Recently uploaded (20)
Range estimation in Scrum
- 1. Building a more accurate burndown Using Range Estimation in Scrum Agile 2010 Conference August 2010 Arin Sime 434 996 5226 [email_address]
- 2. Pitfalls of traditional estimation techniques
- 3. How long does it take you to get to work? traffic optimistic every day? method of travel
- 16. Agile and Scrum can run into other pitfalls though…
- 17. Potential pitfalls: Single-point estimates What about Risk? Implies a set delivery of features Story points are hard to explain
- 18. Better accuracy using range estimation
- 21. Incorporating range estimation into Scrum
- 25. Range estimation in Scrum Poker Still middle of the road, but Green recognizes some risk Orange sees this as really easy Blue sees this as more complicated The likely discussion: Orange and Blue need to compare their visions for this task. Likely Outcome: 8-13? Red and Blue no longer agree: Red is confused or sees big risks
- 26. Using ranges in your task list
- 27. Using ranges in your task list Enter Low/High =(Lo*0.33)+(Hi*0.67) Sums of Lo, Hi, 2/3; then trend them to zero update daily
- 28. Using ranges in your burndown
- 29. Ranges help to highlight obstacles and know when to cancel an iteration
- 30. We were able to improve on the next iteration, but it was still hard
- 31. Ranges help reinforce obstacles Obstacle removed
- 33. Using ranges to better communicate
- 35. How long? Um… 2 days 4 days Do you know your fudge factor? You Your Boss Big Boss
- 36. How long? 2-4 days 2-4 days Ranges help you control your fudge factor You Your Boss Big Boss
- 37. Another example: Use ranges to better empower your boss or client You Your Boss Big Boss
- 38. Perfect – Do it! How long? How much for X? GRRR Umm….. You Your Boss Big Boss 2 days Actually … 4 days 4 days later… 2 days * rate Budget Left: 2 days
- 39. Instead…. You Your Boss Big Boss
- 40. No thx, do something easier How long? How much for X? YES! You Your Boss Big Boss 2-4 days Done! 2 days later… 2-4 days * rate Budget Left: 2 days
- 41. Potential pitfalls of range estimation
- 42. Potential pitfalls of range estimation Really Wide Ranges Not everything can take 2 – 200 hours or you lose all credibility
- 43. Potential pitfalls of range estimation Bosses who don’t get it You’re going to have to sell them on how your estimates will improve their decision making ability.
- 44. Potential pitfalls of range estimation Pushed back deadlines Ranges are not an excuse to always miss deadlines. But they do make it less of a surprise, and encourage you to be more cautious.
- 45. Potential pitfalls of range estimation Is 2/3 the new single-point? Be careful not to just start treating the 2/3 calculated estimate, use the ranges.
- 46. Further Reading
- 47. Questions? Arin Sime 434 996 5226 [email_address] Twitter.com/ArinSime
Editor's Notes
- how long does it take you to drive to work? Is that everyday? Traffic? Optimistic?
- Show single point then double point
- Yellow doesn’t know what they’re talking about.