How To Estimate:

  1. The Team will estimate the story. Large stories, typically stories with estimated story points of thirteen or higher, will need to be decomposed into smaller Stories. Product Owner/Proxy PO should do this offline. As a rule of thumb, if the Story is too big to be completed by one “ideal” person in the Sprint, then it should be treated as a large Story that needs to be broken into smaller Stories.
  2. Dev Team estimates each backlog item using the Modified Fibonacci Scale (0, .5, 1, 2, 3, 5, 8, 20, 40, 100). The backlog items are estimated based on relative complexity. Complexity is defined as effort, risks, and unknowns, and is relative to the baseline Story. Therefore, the Dev Team should have one baseline Story that can be completed in 1 ideal day, and give that Story an estimate of 1 point. When the Dev Team does relative sizing, they are comparing the Story size to the baseline Story. For a Story committed to a Sprint, the Story size should be 8 points or less.