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

Agile Estimation with Planning Poker

Agile Estimation with Planning Poker

Slides "Agile Estimation with Planning Poker" by Hector Benitez at Regional Scrum Gathering Peru 2016 #rsgpe2016

Hector Benitez

April 18, 2016
Tweet

More Decks by Hector Benitez

Other Decks in Technology

Transcript

  1. What’s Planning Poker? AGILE ESTIMATION WITH PLANNING POKER Planning poker

    is a consensus-based, gamified technique for estimating, effort in development tasks in software development.
  2. • A few service design terms • Frontstage & backstage

    • Elements of a service • Service blueprints AGILE ESTIMATION WITH PLANNING POKER Why estimate? ➔ To prioritize product backlog ➔ To make longer-term predictions
  3. Why PlanningPoker? AGILE ESTIMATION WITH PLANNING POKER ➔ No bias

    ➔ Independent thinking ➔ Reach consensus ➔ Ownership
  4. What you need AGILE ESTIMATION WITH PLANNING POKER ➔ User

    Stories ➔ Egg Timer ➔ Sets of cards (local teams) ➔ PlanningWith.Cards app (distributed teams)
  5. Who gets to play? AGILE ESTIMATION WITH PLANNING POKER ➔

    All developers ➔ Scrum Master/Project Manager* ➔ Product Owner* OBSERVERS ONLY ➔ QA ➔ Designers
  6. How to play AGILE ESTIMATION WITH PLANNING POKER ➔ Each

    player = 1 deck of cards ➔ ScrumMaster moderates the meeting ➔ Moderator provides quick task overview ➔ Opportunity to clarify assumptions and assess risks ➔ Product owner answers any questions
  7. How to play AGILE ESTIMATION WITH PLANNING POKER ➔ Each

    estimator privately picks a card and don’t show ➔ All cards are simultaneously shown ➔ People with high or low estimates justify their estimation ➔ Use the egg timer to limit this discussion ➔ Repeat until a consensus
  8. When is the estimate good enough? AGILE ESTIMATION WITH PLANNING

    POKER ➔ How many rounds? ➔ Average, Highest, Lowest, Majority?
  9. FAQ about participants AGILE ESTIMATION WITH PLANNING POKER ➔ Planning

    Poker for Designers/QAs? ➔ ScrumMaster? ➔ Product Owner? ➔ Mixed teams? ? ? ? ?
  10. Story Points AGILE ESTIMATION WITH PLANNING POKER It’s an arbitrary

    number that tells the team how hard the story is ➔ Example ➔ Baseline 15 3 40 ? ? ?
  11. Story Points vs Hours AGILE ESTIMATION WITH PLANNING POKER ➔

    Story Points are about effort ➔ Story points are for stories ➔ Could involve multiple roles/persons ➔ Not every 3-point story will take exactly the same amount of time ? ?
  12. Velocity AGILE ESTIMATION WITH PLANNING POKER ➔ Sum of estimates

    to be delivered for features per iteration ➔ Gets more accurate with time TWO APPROACHES 1. Commitment-driven sprint planning 2. Velocity-driven sprint planning
  13. ➔ After a story-writing session ➔ At the start of

    the sprint planning ➔ Once per sprint (Grooming) When to use it? AGILE ESTIMATION WITH PLANNING POKER Sprint !
  14. Why do we ♥ Planning Poker? AGILE ESTIMATION WITH PLANNING

    POKER ➔ Discussions lead to accurate estimations ➔ Not just the opinion of principals ➔ Greater understanding of work ➔ Leverages collective knowledge and teamwork ➔ High level architecture and design discussion ➔ Ownership of estimate
  15. Recommendations AGILE ESTIMATION WITH PLANNING POKER ➔ Voters = Who

    actually do the work ➔ Avoid long technical discussions ➔ Time the session ➔ Use the “I need a break” & “question” cards ➔ Use PlanningWith.Cards for distributed teams
  16. Nearsoft Talks - Mejores Prácticas para Trabajar Remotamente LUN 18

    ABR A LAS 19:30, SAN ISIDRO EVENTO GRATUITO Por: Nearsoft, StartupWeekend Lima & GDG Lima