Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Agile Estimation & Sizing

Agile Estimation & Sizing

By: Ty Crockett

Improving

May 29, 2013
Tweet

More Decks by Improving

Other Decks in Technology

Transcript

  1. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Ty Crockett

    Started as an IT dude, now is an Agile dude Loves to work with teams, Digs Scrum Comic Book Fan, Convention Geek
  2. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Why am

    I doing this? I am also an estimation victim….
  3. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. When can

    I have it? How much will it cost? What will I get? The Key 3
  4. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. The Iron

    Triangle Fixed Estimated Resources Time Requirements Conventional Planning 8
  5. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. The Cone

    of Uncertainty 100% 200% 400% 50% 25% Time Actual Completion Realistic Projections Typical Projections
  6. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Why do

    Planning? There is no Plan B There was no Plan A Because it is not ok to not have a plan
  7. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Why do

    Planning? Ø If you do not have a plan Ø They… Ø Think you lack vision Ø Lose confidence Ø Will tell you the date
  8. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Why do

    Planning? We should be able to forecast We should have a forecast Our forecasts should be defensible Based on historical performance It is an act of transparency It is something to measure progress against It is a great way to estimate a project’s cost
  9. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Why do

    Planning? Our clients deserve to know when… Our “team” deserves to know when…
  10. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. The Planning

    Onion Strategy Portfolio Product Roadmap Release Sprint Day Agile Project Planning Market Research
  11. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Inverting the

    Iron Triangle Fixed Estimated Resources Time Features Requirements Resources Time Classic was Plan Driven Agile is Feature Driven 27
  12. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. What type

    of Release? Ø Feature Based Ø Reaching a critical mass of business value Ø Delivering a themed feature set
  13. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. What type

    of Release? Ø Time based Ø Contractual Dates Ø A cadenced release schedule
  14. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Roadmap Planning

    Release Planning Sprint Planning Themes Epics Stories Tasks Daily Planning Finer Levels, Finer Detail 31
  15. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Lack of

    detail... What about when we lack all of the information?
  16. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Lack of

    detail… Even with minimal information we still size. (It’s all relative of course) Our teams still have the option to resize as new information becomes apparent.
  17. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Change Sometimes

    you have to reset your plan. By sometimes, I mean very often… Mom, I can’t call Tracy, I’m like… all out of minutes and stuff! Yes, I like… put limits on your plan. Buh-bye!
  18. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. White Elephant

    Sizing Smaller Larger 1 2 3 5 8 13 20 40 100 USER STORY #1 This first one is a ___ in the world of stuff that we do.
  19. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. White Elephant

    Sizing Smaller Larger 1 2 3 5 8 13 20 40 100 USER STORY #2 USER STORY #3 The team continues to put up stories under the size that they feel is appropriate When all the stories are up the team takes turn moving stories and having discussion on why When the group feels that enough progress has been made they have a sized backlog
  20. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. Release Burnup

    Chart 6.25 11 18 25.5 24 28 36 40 0 5 10 15 20 25 30 35 40 45 50 1 2 3 4 5 6 7 8 Points Sprints Release Progress Cumulative Points Description Simple tool for Team to track progress during a Sprint. Key Characteristics "   Shows work remaining, not work completed "   Allows analysis of true Team capacity Managed by Team, ScrumMaster 48
  21. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. When is

    when? 500 pt Product Backlog Two week Sprints 500 25 20 Sprints 2 weeks 40 wks. or 10 Mo.
  22. ©2010 Improving Enterprises, Inc. ©2011 Improving Enterprises, Inc. By the

    way… http://www.forbes.com/sites/carolpinchefsky/2012/02/21/how-much-would-it-cost-to-build-the-death-star-from-star-wars/ The Death Star was pretty expensive. “$852,000,000,000,000,000. Or roughly 13,000 times the world’s GDP” …and that’s just the cost of steel production. …and we built it twice!