Estimating User Stories Learning Why and How    Stephane Rondal    Arexo Consulting      2012 October
Grabsome free food05/05/09   www.agiletour.com
About Stephane  • Consultant for banks, insurances, European    institutions &SMEs  • Java Architect (16+) & Agile Practio...
In this Talk, You’llLearn About•    Definitions of User Stories, Estimations•    WhyShould You Estimate User Stories•    T...
Recommended Reading05/05/09   www.agiletour.com
Whatis a User Story• A user story is a very slim and high-level     definition of a requirement, containing just     enoug...
Whatis a User Story• Good User Stories are     o Focused on features, not tasks     o Independent     o Negotiable     o V...
Whatis an Estimate• The approximate amount of  effort required to achieve a  user story• Called story points• Achieve = Do...
Definition of Done           Source: http://www.scrumalliance.org/articles/106-definition-of-done-a-reference05/05/09   ww...
Why Should You Estimate User Stories                               • Your boss wantsyou                                   ...
Why Should You Estimate User Stories• What can I buy for this price?05/05/09             www.agiletour.com
Why Should You Estimate User Stories• Buy yourself some credibility05/05/09             www.agiletour.com
Why Should You Estimate User Stories• Group estimating reveals differences in  knowledge and understanding• Finding those ...
Estimatingisdifficult.           The more you do it, the betteryou’llgetatit.05/05/09                    www.agiletour.com
What’s all the Bad Fuss About Estimations05/05/09                www.agiletour.com
What’s all the Bad Fuss About Estimations• People construe estimates as promises. Failed  predictions fan blame. Trust and...
What’s all the Bad Fuss About Estimations• Most of these critics are valid• But…     o Are they really questioning estimat...
How to Estimate User Stories                           • Demystify the                                black art…05/05/09  ...
How to Estimate User Stories     Scrum recommends a technique called                          Planning Poker05/05/09      ...
Planning Poker   Get your team together, you want everybody to                     participate05/05/09             www.agi...
Planning Poker               Grab the top priority user                 stories from your                 backlog         ...
Planning PokerFor each story     o Be time-boxed     o (Re-) present the user story,       briefly     o Then…05/05/09    ...
Planning Poker   Step 1 - Reflection Time (individual)Source: http://www.crisp.se/bocker-och-produkter/planning-poker  05/...
Planning Poker   Step 2 – Showdown & DiscussSource: http://www.crisp.se/bocker-och-produkter/planning-poker  05/05/09     ...
Planning Poker   Step 3 – Repeat until convergenceSource: http://www.crisp.se/bocker-och-produkter/planning-poker  05/05/0...
Best Practices• Do not use units of time for story points• Involve all those active in the realization of the  story• Base...
What’sNext• We now have a     backlog with     more important     user stories     estimated more     precisely.• But how ...
What’sNext• How do we draw  the release  date?• Or how do we  know what we’ll  get at a certain  date?05/05/09            ...
Velocity• How many story points were actually delivered at the end of the sprint? 05/05/09            www.agiletour.com
Velocity• Continue measuring     velocity of each sprint     Sprint             Velocity     Sprint #1          16     Spr...
Estimating the Release DateAssuming there are 5 iterations leftAt our worst velocity, we’ll reach 5x14 SPAt an average vel...
Estimating the Release Date   • A good plan will go from       o We’ll be done in the 4th quarter       o We’ll be done in...
When to Estimate            Product                     PrioritizedBacklo                                                 ...
Where to Estimate• Online: www.planningpoker.com• Within most Agile project managment tools• At a table, using cards05/05/...
Conclusion• Planning Poker and Velocity are not a perfect,  flawless estimation techniques• Still much better than no esti...
Thank You!           Questions / Feedback                 stephane.rondal@arexo.be                 @stephanerondal05/05/09...
Upcoming SlideShare
Loading in …5
×

Agile Tour Brussels 2012 - Estimating user stories

1,561 views

Published on

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,561
On SlideShare
0
From Embeds
0
Number of Embeds
497
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • personally , if I was to invest all my savings in a software development project, I’d require to know upfront how long it would take/how much it would cost
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Explain why “everybody”
  • Agile Tour Brussels 2012 - Estimating user stories

    1. 1. Estimating User Stories Learning Why and How Stephane Rondal Arexo Consulting 2012 October
    2. 2. Grabsome free food05/05/09 www.agiletour.com
    3. 3. About Stephane • Consultant for banks, insurances, European institutions &SMEs • Java Architect (16+) & Agile Practionner (7+) • Co-founder of Arexo Consulting stephane.rondal@arexo.be @stephanerondal05/05/09 www.agiletour.com
    4. 4. In this Talk, You’llLearn About• Definitions of User Stories, Estimations• WhyShould You Estimate User Stories• The Bad Sides of Estimations• How To Estimate (Planning Poker)• Velocity• Release Planning05/05/09 www.agiletour.com
    5. 5. Recommended Reading05/05/09 www.agiletour.com
    6. 6. Whatis a User Story• A user story is a very slim and high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it.05/05/09 www.agiletour.com
    7. 7. Whatis a User Story• Good User Stories are o Focused on features, not tasks o Independent o Negotiable o Valuable o Small ( <= 1 sprint/iteration) o Testable05/05/09 www.agiletour.com
    8. 8. Whatis an Estimate• The approximate amount of effort required to achieve a user story• Called story points• Achieve = Done (Done Done Done)05/05/09 www.agiletour.com
    9. 9. Definition of Done Source: http://www.scrumalliance.org/articles/106-definition-of-done-a-reference05/05/09 www.agiletour.com
    10. 10. Why Should You Estimate User Stories • Your boss wantsyou to! • Whenwillthisthingber eady?05/05/09 www.agiletour.com
    11. 11. Why Should You Estimate User Stories• What can I buy for this price?05/05/09 www.agiletour.com
    12. 12. Why Should You Estimate User Stories• Buy yourself some credibility05/05/09 www.agiletour.com
    13. 13. Why Should You Estimate User Stories• Group estimating reveals differences in knowledge and understanding• Finding those gaps early is helpful• But be disciplined to resist guessing and speculation. Dig deeper, understand more, then try estimating again. Source : http://www.estherderby.com/2012/03/estimating-is-often-helpful-estimates-are-often-not.html05/05/09 www.agiletour.com
    14. 14. Estimatingisdifficult. The more you do it, the betteryou’llgetatit.05/05/09 www.agiletour.com
    15. 15. What’s all the Bad Fuss About Estimations05/05/09 www.agiletour.com
    16. 16. What’s all the Bad Fuss About Estimations• People construe estimates as promises. Failed predictions fan blame. Trust and openness suffer.• People game estimates.• People compare teams based velocity, while velocity and story points are team-dependent metrics. Source : http://www.estherderby.com/2012/03/estimating-is-often-helpful-estimates-are-often-not.html05/05/09 www.agiletour.com
    17. 17. What’s all the Bad Fuss About Estimations• Most of these critics are valid• But… o Are they really questioning estimations, or just some estimation techniques? o What other alternatives do they propose? o Is your Agile practice at the same maturity level than theirs? o There’s no free lunch05/05/09 www.agiletour.com
    18. 18. How to Estimate User Stories • Demystify the black art…05/05/09 www.agiletour.com
    19. 19. How to Estimate User Stories Scrum recommends a technique called Planning Poker05/05/09 www.agiletour.com
    20. 20. Planning Poker Get your team together, you want everybody to participate05/05/09 www.agiletour.com
    21. 21. Planning Poker Grab the top priority user stories from your backlog Source: http://www.informit.com/articles/article.aspx?p=192823205/05/09 www.agiletour.com
    22. 22. Planning PokerFor each story o Be time-boxed o (Re-) present the user story, briefly o Then…05/05/09 www.agiletour.com
    23. 23. Planning Poker Step 1 - Reflection Time (individual)Source: http://www.crisp.se/bocker-och-produkter/planning-poker 05/05/09 www.agiletour.com
    24. 24. Planning Poker Step 2 – Showdown & DiscussSource: http://www.crisp.se/bocker-och-produkter/planning-poker 05/05/09 www.agiletour.com
    25. 25. Planning Poker Step 3 – Repeat until convergenceSource: http://www.crisp.se/bocker-och-produkter/planning-poker 05/05/09 www.agiletour.com
    26. 26. Best Practices• Do not use units of time for story points• Involve all those active in the realization of the story• Baseline your estimations, what means 2 and 5 for the team• Avoid changing your baseline too often• Keep track of your estimations05/05/09 www.agiletour.com
    27. 27. What’sNext• We now have a backlog with more important user stories estimated more precisely.• But how does this help us?05/05/09 www.agiletour.com
    28. 28. What’sNext• How do we draw the release date?• Or how do we know what we’ll get at a certain date?05/05/09 www.agiletour.com
    29. 29. Velocity• How many story points were actually delivered at the end of the sprint? 05/05/09 www.agiletour.com
    30. 30. Velocity• Continue measuring velocity of each sprint Sprint Velocity Sprint #1 16 Sprint #2 18 Range: Sprint #3 14 Sprint #4 17 14-19 Sprint #5 1905/05/09 www.agiletour.com
    31. 31. Estimating the Release DateAssuming there are 5 iterations leftAt our worst velocity, we’ll reach 5x14 SPAt an average velocity, we’ll reach 5x16,5 SPAt our best velocity, we’ll reach 5x19 SP05/05/09 www.agiletour.com
    32. 32. Estimating the Release Date • A good plan will go from o We’ll be done in the 4th quarter o We’ll be done in November o We’ll be done in November 21stSource: http://www.mountaingoatsoftware.com/ 05/05/09 www.agiletour.com
    33. 33. When to Estimate Product PrioritizedBacklo g Backlog Release Sprintplanni planning ng Sprint BacklogVision Retrospective Planning 2 Sprint BacklogTasks Sprint Review Daily Meetings 05/05/09 www.agiletour.com
    34. 34. Where to Estimate• Online: www.planningpoker.com• Within most Agile project managment tools• At a table, using cards05/05/09 www.agiletour.com
    35. 35. Conclusion• Planning Poker and Velocity are not a perfect, flawless estimation techniques• Still much better than no estimation technique at all• Personally helped me gained lot of Agile experience and maturity• I recommend you use it if you have nothing better05/05/09 www.agiletour.com
    36. 36. Thank You! Questions / Feedback stephane.rondal@arexo.be @stephanerondal05/05/09 www.agiletour.com

    ×