Story Point Calculator
Estimate a user story with effort, complexity, uncertainty, risk, and dependencies. Get a Fibonacci story point recommendation you can copy into Jira.
Try an example
Effort
How much implementation work is involved?
Complexity
How much design or technical reasoning is needed?
Uncertainty
How many unknowns remain before work starts?
Risk
What could break if this work goes wrong?
Dependencies
How much does the story rely on other people or systems?
Recommended estimate
2
story points
Small
Confidence: High
Sizing score: 3/15
Planning guidance
This story looks well understood. Use the estimate as a starting point for team discussion.
Confirm acceptance criteria, testing approach, and rollout expectations before finalizing the estimate.
- Confirm acceptance criteria and Definition of Done.
- Run Planning Poker if the estimate needs team agreement.
- Compare the estimate against sprint capacity before committing.
Estimate breakdown
Effort
Small
Score: 1
Complexity
Known
Score: 1
Uncertainty
Minor
Score: 1
Risk
Low
Score: 0
Dependencies
None
Score: 0
When to use this calculator
Use it during backlog refinement when a story is understood enough to discuss, but before the team commits it to a sprint. For live team voting, use Planning Poker after everyone has reviewed the story.
How this story point calculator works
The calculator combines five parts of a user story: implementation effort, technical complexity, uncertainty, delivery risk, and dependencies. The combined score maps to a Fibonacci estimate such as 1, 2, 3, 5, 8, 13, or 21 points.
Treat the result as a discussion starter, not a promise of hours. Compare it with completed stories, confirm the acceptance criteria, and use Planning Pokerwhen the whole team needs to vote together.
Frequently Asked Questions
How does the story point calculator work?
The calculator scores effort, complexity, uncertainty, risk, and dependencies, then maps the total to a Fibonacci story point estimate. Treat the result as a starting point for team discussion, not a replacement for estimation conversation.
Should story points equal hours?
No. Story points estimate relative size, including effort, complexity, and uncertainty. Hours are a time forecast. A five-point story may take different amounts of time for different teams.
What should we do with a 13 or 21 point story?
Split it before sprint commitment. Large estimates usually hide multiple deliverables, unclear acceptance criteria, or unresolved dependencies.
Is this tool free?
Yes. The story point calculator is free, requires no login, and runs in your browser.