Story Point Estimating Taking the Guessing out of it

  1. The team uses hours instead of Point system
  2. Estimates are typically wildly off what they had originally stated
  3. The team is frustrated and don’t see the value in estimating work item
  • T-shirt size (S, M, L, XL)
  • Fibonacci (1,2,3,5,8)

Setting the Team formation

Where to Start — Collaborate with Product Owner

Running Estimation sessions — Playing a Game of Point Poker

  1. If everyone selects the same value then, it’s given to the User Story.
  2. If two or more persons have a wide variance of the estimate, then the members discuss how they arrived at those estimates and the team makes the final decision.
  3. If the User Story has too many uncertain elements for the team to commit an estimate to, then the Product owner can intervene for further clarity or request clarification from the business.

Bench-marking Stories

From Story Points to Hours

  • Capacity — The amount of work a team can do in a specific Sprint
  • Velocity — Measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum
  1. Not having the right composition of team member involvement
  2. The availability of information to do accurate estimations (partially missing or incomplete)
  3. Lack of refining team approach and estimates; learning from past experiences.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Oldane Graham

Oldane Graham

Software Consultant | Project Manager | Certified Scrum Master | Agile Enthusiast | Digital Nomad| Blogger