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
Story Points
Pedro Gonzalez
Imagine that...
You get sick of Software
development as a
career
And you decide is to go
into the restaurant
business
How would you estimate this?
Your first job is to move all these glasses to the
tables outside in the garden
20 meters
Story points
Game
Some insights about estimations
Planning poker
Long-term planning
FAQ
Agenda
Story Points
What’s a story point?
“An estimate of relative complexity of a user story”
It is a unitless number, but still a useful num...
Most commonly used estimating unit in Scrum teams
Factors involved
Volume: How much is there?
Complexity: How hard it is?
...
1. Forces the use of relative estimating
There are studies that show that we’re better at this (1)
2. Focuses on estimatin...
3 Key
Advantages
Who is going to do it faster?
Game5 minutes to form 5-8 people teams
Europe
Europe
NO GOOGLE!
Spain: 505,990 km2
Portugal: 92,212 km2
Actual Areas
Spain: 5x
Portugal: 1x
Estimations
Insights
1. Group A
Given project spec
2. Group B
Given the same spec but with estimation
irrelevant details
List of users
List of ...
1. Group A
Given a 1-page project spec
2. Group B
Given a 7-pages project spec
Double line space
Margins
Some Insights abo...
1. Group A
Given requirements R1-R4
2. Group B
Given requirements R1-R5
3. Group C
Some Insights about estimations
1. 4 ho...
1. Group A
Given project spec
2. Group B
Given project spec
Customer thinks it’ll take 500 hours
Some Insights about estim...
More information will not always provide better estimations
Estimations get influenced very easily by external factors
Som...
Planning
Poker
Planning Poker
Estimator Round 1 Round 2
Minh 3 5
Tam 8 5
Thang 2 5
Truc 5 8
Phuong 3 5
1. PO explains the User Story
2. Q&A (3 mins)
3. Each team member selects card and shows
4. High and low explain and discu...
Planning Poker
Why fibonacci series?
Planning Poker
Why fibonacci series? 1 2 3 5
Planning Poker
Why fibonacci series? 1 2 3 5
Planning Poker
Wait, it’s not exactly fibonacci
People doing the work, estimate the work
Estimators are required to justify estimates
Estimates are constrained to a set o...
Long-term
Planning
Long-term
Planning
Average of 3 worst sprints
27.3
Average of 3 best sprints
38.3
Long-term Planning
y=27.3xy=38.3x
User story
User story
User story
User story
User story
User story
User story
User story
...
Long-term Planning
y=27.3xy=38.3x
User story
User story
User story
User story
User story
User story
User story
User story
...
FAQFREQUENTLY ASKED QUESTIONS
FAQ
What if there is no Front-End
work in the story?
FAQ
What if my team is remote?
https://www.planningpoker.com/
FAQ
What if the story is not clear yet?
What part is missing?
Play with the uncertainty
part
Assume the worst
scenario
FAQ
What if there are dependencies?
Can you join dependent stories
into a bigger story?
Can you create one story for the
c...
FAQ
What about teams new to
Scrum?
http://theagilepirate.net/archives/109
FAQ
How to prevent estimate
inflation?
1 2 5
3
FAQ
How to prevent estimate
inflation?
1 3 5
2
Questions?
Thank you!
Agile Estimation, Mike Cohn -
https://www.youtube.com/watch?v=fb9Rzyi8b90
Agile Product Ownership in a Nutshell -
https://...
Upcoming SlideShare
Loading in …5
×

[HCM Scrum Breakfast] Agile estimation - Story points

873 views

Published on

This August Scrum Breakfast, we have a new speaker - Mr. Pedro Gonzalez - Scrum Master at TINYpulse.

He will bring us an interesting topic about Agile estimation using story points, giving some tips on why relative estimations are far better than absolutes, why we shouldn't spend too long in details, and other issues he has experienced himself with his team.

Published in: Software
  • Be the first to comment

[HCM Scrum Breakfast] Agile estimation - Story points

  1. 1. Agile Estimation Story Points Pedro Gonzalez
  2. 2. Imagine that... You get sick of Software development as a career And you decide is to go into the restaurant business
  3. 3. How would you estimate this? Your first job is to move all these glasses to the tables outside in the garden 20 meters
  4. 4. Story points Game Some insights about estimations Planning poker Long-term planning FAQ Agenda
  5. 5. Story Points
  6. 6. What’s a story point? “An estimate of relative complexity of a user story” It is a unitless number, but still a useful number Story Points
  7. 7. Most commonly used estimating unit in Scrum teams Factors involved Volume: How much is there? Complexity: How hard it is? Uncertainty: What’s NOT known? What’s known? Story Points
  8. 8. 1. Forces the use of relative estimating There are studies that show that we’re better at this (1) 2. Focuses on estimating size, not duration We can derive duration empirically 3. Unlike time estimates, it puts estimates in units that we can add together A 10-point user story is expected to take twice as long as a 5-points user 3 Key Advantages (1) https://www.google.com.vn/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0ahUKEwjVn6GawK7OAhUFk5QKHfGXAwoQFggpMAI&url=https%3A%2F%2Fwww.simula.no%2Ffile%2Fsim ulasimula814pdf%2Fdownload&usg=AFQjCNHkTpakk2JSFS--CGpwiqn6hoSdBw&sig2=x-5y_uQlXbl1LSzZCCvq0g&bvm=bv.129391328,d.dGo
  9. 9. 3 Key Advantages Who is going to do it faster?
  10. 10. Game5 minutes to form 5-8 people teams
  11. 11. Europe
  12. 12. Europe NO GOOGLE!
  13. 13. Spain: 505,990 km2 Portugal: 92,212 km2 Actual Areas Spain: 5x Portugal: 1x
  14. 14. Estimations Insights
  15. 15. 1. Group A Given project spec 2. Group B Given the same spec but with estimation irrelevant details List of users List of passwords Some Insights about estimations 1. 20 hours 2. 39 hours
  16. 16. 1. Group A Given a 1-page project spec 2. Group B Given a 7-pages project spec Double line space Margins Some Insights about estimations 1. 117 hours 2. 173 hours
  17. 17. 1. Group A Given requirements R1-R4 2. Group B Given requirements R1-R5 3. Group C Some Insights about estimations 1. 4 hours 2. 4 hours 3. 8 hours
  18. 18. 1. Group A Given project spec 2. Group B Given project spec Customer thinks it’ll take 500 hours Some Insights about estimations 1. 456 hours 2. 555 hours 3. 96 hours
  19. 19. More information will not always provide better estimations Estimations get influenced very easily by external factors Some Insights about estimations
  20. 20. Planning Poker
  21. 21. Planning Poker Estimator Round 1 Round 2 Minh 3 5 Tam 8 5 Thang 2 5 Truc 5 8 Phuong 3 5
  22. 22. 1. PO explains the User Story 2. Q&A (3 mins) 3. Each team member selects card and shows 4. High and low explain and discuss If more than 2/3 minutes —> Revote Converges after 2-3 rounds Planning Poker
  23. 23. Planning Poker Why fibonacci series?
  24. 24. Planning Poker Why fibonacci series? 1 2 3 5
  25. 25. Planning Poker Why fibonacci series? 1 2 3 5
  26. 26. Planning Poker Wait, it’s not exactly fibonacci
  27. 27. People doing the work, estimate the work Estimators are required to justify estimates Estimates are constrained to a set of values So we don’t waste time in meaningless arguments Group discussions lead to better estimates Emphasizes relative instead of absolute estimates Planning Poker - Why does it work?
  28. 28. Long-term Planning
  29. 29. Long-term Planning Average of 3 worst sprints 27.3 Average of 3 best sprints 38.3
  30. 30. Long-term Planning y=27.3xy=38.3x User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story Less priority
  31. 31. Long-term Planning y=27.3xy=38.3x User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story User story Less priority
  32. 32. FAQFREQUENTLY ASKED QUESTIONS
  33. 33. FAQ What if there is no Front-End work in the story?
  34. 34. FAQ What if my team is remote? https://www.planningpoker.com/
  35. 35. FAQ What if the story is not clear yet? What part is missing? Play with the uncertainty part Assume the worst scenario
  36. 36. FAQ What if there are dependencies? Can you join dependent stories into a bigger story? Can you create one story for the common work and STILL add value? Do 2 estimations for the dependent stories: 5 if done first 2 if done later
  37. 37. FAQ What about teams new to Scrum? http://theagilepirate.net/archives/109
  38. 38. FAQ How to prevent estimate inflation? 1 2 5 3
  39. 39. FAQ How to prevent estimate inflation? 1 3 5 2
  40. 40. Questions? Thank you!
  41. 41. Agile Estimation, Mike Cohn - https://www.youtube.com/watch?v=fb9Rzyi8b90 Agile Product Ownership in a Nutshell - https://www.youtube.com/watch?v=502ILHjX9EE https://www.simula.no/publications References

×