Upcoming SlideShare
×

# Introduction To Agile Estimating and Planning

5,199 views

Published on

My presentation on Agile Estimating and Planning to PMI, Queensland (Australia) Chapter, on 17th June 2009.

Published in: Technology
8 Likes
Statistics
Notes
• Full Name
Comment goes here.

Are you sure you want to Yes No
• Be the first to comment

Views
Total views
5,199
On SlideShare
0
From Embeds
0
Number of Embeds
1,831
Actions
Shares
0
166
0
Likes
8
Embeds 0
No embeds

No notes for slide

### Introduction To Agile Estimating and Planning

1. 1. Agile Estimating & Planning Kane Mar Certiﬁed Scrum Coach and Trainer. http://KaneMar.com http://Scrumology.com.au
2. 2. Creative Commons Attribution 3.0 Kane Mar and Others (see credits) You are free: to Share — to copy, distribute and transmit the work to Remix — to adapt the work Under the following conditions: Attribution. You must attribute the work in the manner speciﬁed by the author or licensor (but not in any way that suggests that they endorse you or your use of the work) http://creativecommons.org/licenses/by/3.0/
3. 3. Agenda About me. Traditional Estimating vs Agile Estimating Relative Estimates Context is Important Deriving Project Duration
5. 5. Tradition Estimating vs Agile Estimating KLoC Ideal Days Function Story Points Points
6. 6. Relative Estimates Agile estimates are estimates made on a relative scale Here’s an example: Smarties in a glass
7. 7. Relative Estimates Points are abstract representations of size, which includes complexity, effort etc. Scales currently used: Fibonacci Scale: 1, 2, 3, 5, 8, 13 ... Linear Scales: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 T-shirt sizes: XS, S, M, L, XL
8. 8. Relatives Estimates Points do not have units Points are not related (easily) to hours or days What use are relative estimates if we don’t have a time or duration associated with them? How can we use an abstract concept to derive durations and timeframes?
9. 9. Exercise: Relative Estimates We use an abstract concept to enable transactions for goods and services every single day. We deﬁne the value of a dollar (“ﬁat money”) by how much “stuff” we can buy with it
10. 10. Exercise: Relative Estimates 1 litre of milk:
11. 11. Exercise: Relative Estimates A loaf of bread:
12. 12. Exercise: Relative Estimates A dozen eggs:
13. 13. Exercise: Relative Estimates A desert:
14. 14. Exercise: Relative Estimates This is a Runeberg Tart. It’s named after the Finnish national poet Johan Ludvig Runeberg (1804 - 1877) who, according to the legend, enjoyed the tart with punch
15. 15. Context is important Context is important when estimating with relative sizing The relevance of a Point is very, very local Comparing points between teams has very little meaning (although it is possible with additional effort)
16. 16. Relative Estimates Estimating with Points is fast Points can be easy to explain and communicated They allow us to deal with ambiguity The whole team is involved with estimation
17. 17. Project duration from Points Iteration 1 Iteration 3 10 Pts 9 Pts Iteration 2 11 Pts 30 Pts
18. 18. References “Agile Estimating and Planning”, Mike Cohn “User Stories Applied”, Mike Cohn
19. 19. References “Agile Software Development with Scrum,” Ken Schwaber and Mike Beedle, 2001 “Agile Project Management with Scrum”, Ken Schwaber “Scrum and the Enterprise”, Ken Schwaber “Scrum in 5 minutes”, Softhouse Nordic AB http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf
20. 20. Credits http://www.ﬂickr.com/photos/rugby_pioneers/ http://www.ﬂickr.com/photos/lﬂ/ http://www.ﬂickr.com/photos/66164549@N00/ http://www.ﬂickr.com/photos/rugby_pioneers/ http://www.ﬂicker.com/photos/vernhart/ http://www.ﬂickr.com/photos/sierravalleygirl/
21. 21. Credits http://www.ﬂickr.com/photos/rugby_pioneers/ http://www.ScrumWorksPro.com/ http://www.ﬂickr.com/photos/rbh/ http://www.ScrumWorksPro.com/ http://www.ﬂickr.com/photos/mattimattila/