Story Points Examples

# ​​Template

This is a template. Please copy this and make this your own!

# ​​Why?

Story points are how we estimate the amount of work required to complete a user story. We use this formula to figure out the number of story points:

# ​​SP = Volume of Work x Complexity x Unknowns

where:
• Volume of Work is simply, “there’s a lot to do to get this story completed”
• Complexity is “this is hard to do, and involves lot of moving parts”
• Unknowns are “lot of things here that we don’t know how to complete” Ideally, we spike these unknowns.

We use the Fibonacci scale to estimate story points, and this is how we calibrate it:
 ​​Story Points ​​Description ​​1 ​​Trivial work! ​​2 ​​Perhaps some of volume of work or complexity, but no unknowns. ​​3 ​​One or more of increased volume of work, complexity, and perhaps a few unknowns. ​​5 ​​The most complex work that a developer can take up in a sprint! ​​8 or more ​​Should ideally be split up into smaller chunks.
Note: if this can’t be split up, then it’s very likely that the work involved will go beyond a single sprint.

# ​​Reference Issues

Here are examples of some issues and our estimates, for reference and comparison:

# ​​Important Notes

1. When possible, always spike unknowns as a separate story.
1. Story points are not an absolute measure of effort, so never think of estimation as: 1 story point = 1 developer day of effort. Instead, story points are relative measures. The reference issues above can be used as a comparison for this effort measure.
1. If playing planning poker is taking too long, consider: magic estimation.