Agile Estimating

  • View
    2.070

  • Download
    1

Embed Size (px)

Text of Agile Estimating

  • 1.Mike CohnNorwegian Developers Conference6 June 2012Agile Estimating1

2. Copyright Mountain Goat SoftwareAgendaWhat is agile planning?Story pointsIdeal timeEstimating with Planning Poker2 3. Copyright Mountain Goat SoftwareIteration BacklogCode the UI 12Write tests 8Code middle tier 4Update docs 6Automate tests 5As a userProduct BacklogAs a userAs a userAs a userAs a user35522Were talkingabout theseright now3 4. Copyright Mountain Goat Softwareto drive toParis?to read thelast Harry Potterbook?How long will it take4 5. Copyright Mountain Goat SoftwareSize Calculation Duration300kilogramsVelocity=20300/20 = 15iterationsEstimate size; derive duration5 6. Copyright Mountain Goat SoftwareMeasures of sizeTraditionalmeasuresof sizeLines of CodeFunction PointsAgilemeasuresof sizeStory pointsIdeal days6 7. Copyright Mountain Goat SoftwareStory pointsHow long a user story will take (eort)Inuenced by complexity, uncertainty, risk,volume of work, etc.Relative values are what is important:A login screen is a 2.A search feature is an 8.Basic math properties should hold5+5 = 107 8. Copyright Mountain Goat SoftwareEstimating in zoo pointsLionKangarooRhinocerosBearGiraffeGorillaHippopotamusTiger8 9. Copyright Mountain Goat SoftwareAgendaWhat is agile planning?Story pointsIdeal timeEstimating with Planning Poker9 10. Copyright Mountain Goat SoftwareIdeal TimeHow long somethingwill take if:its all you work onno one interrupts youand everything youneed is available10 11. Copyright Mountain Goat SoftwareElapsed time vs. ideal timeMonday has 8 hoursEach week has 40hoursIdeallyEach day has something like:2 hours of meetings2 hours of email4 hours left for the projectBut insteadHow long will thistake?Are you answeringwhat is beingasked?11 12. Copyright Mountain Goat SoftwareStory points are additive; time-basedestimates may not be1Story points help avoid problemswith unit confusion2Two big advantages to story points12 13. Copyright Mountain Goat SoftwareConfusing unitsIteration BacklogCode the UI 12Write tests 8Code middle tier 4Update docs 6Automate tests 5As a userProduct BacklogAs a userAs a userAs a userAs a user305050202013 14. Copyright Mountain Goat SoftwareAgendaWhat is agile planning?Story pointsIdeal timeEstimating with Planning Poker14 15. Copyright Mountain Goat SoftwarePlanning PokerAn iterative approach to estimatingStepsEach estimator is given a deck of cards, each card hasa valid estimate written on itCustomer/Product owner reads a story and itsdiscussed brieyEach estimator selects a card thats his or her estimateCards are turned at the same timeDiscuss dierences (especially outliers)Re-estimate until estimates converge15 16. Copyright Mountain Goat SoftwareEstimator Round 1Trond 5Ana 5Maria 8Johannes 20Round 288813Planning Pokeran example16 17. Copyright Mountain Goat SoftwareProduct Backlog Items EstimateRead (and understand) a high-level, 10-page overview of agilesoftware development in a celebrity news magazine.Read (and understand) a densely written 5-page research paperabout agile software development in an academic journal.Your uncle owns a clock store and wants to sell clocks over theinternet. Write a basic product backlog for him covering whathell need his website to do.Recruit, interview, and hire a new member for your team.Create a 60-minute presentation about agile softwaredevelopment for your coworkers.Wash and wax your boss Porsche.Read (and understand) a 150-page book on agile softwaredevelopment.Write a 5-page summary of this conference for your boss.Estimate these17 18. Copyright Mountain Goat SoftwareFree, or Iwouldntmention itwww.PlanningPoker.com18 19. Copyright Mountain Goat Softwaremike@mountaingoatsoftware.comwww.mountaingoatsoftware.comtwitter: mikewcohn(888) 61-AGILEMike Cohn19