Jira Story Points Calculator
Calculate agile story points on the planning-poker (Fibonacci) deck from complexity, effort, risk and dependencies.
Team velocityoptional
Suggested estimate
5points · Medium
A typical story: some complexity, a little uncertainty.
- Next card up
- 8 points
How it’s worked outComplexity 35% · effort 30% · risk 20% · dependencies 15%
- Each factor is scaled to 0–1 (the first pill is 0, the last is 1) and weighted: complexity 35%, effort 30%, risk 20%, dependencies 15%.
- The weighted score maps onto the planning-poker deck: up to 10% → 1, 22% → 2, 36% → 3, 50% → 5, 64% → 8, 76% → 13. Above that the advice is to split the story rather than play 20, 40 or 100.
- Deck: 1, 2, 3, 5, 8, 13, 20, 40, 100, ?. Story points are relative: use the suggestion to start the planning-poker discussion, not to end it.
How this works: Method,
How this works
Method
Each rating is scaled from 0 to 1 and weighted: complexity 35%, effort 30%, risk 20%, dependencies 15%. The weighted score maps onto the planning-poker deck (up to 10% → 1, 22% → 2, 36% → 3, 50% → 5, 64% → 8, 76% → 13); above that the advice is to split the story.
Changes
- Redesigned: ratings in words, suggestions from the standard planning-poker deck (1 to 13, then 20, 40, 100), a split-the-story warning above 13, and the estimate copies as a Jira comment.
- Results now update as you change a rating, starting from a filled-in example.
- First published.
Frequently Asked Questions
What are story points?
Story points are a relative unit that combines effort, complexity, and uncertainty to size backlog items in agile development. They help teams estimate work without committing to specific time estimates, encouraging discussion and reducing optimism bias. One story point typically represents the effort of a small, well-understood task.
Why use the Fibonacci sequence?
Most teams use a modified Fibonacci planning-poker deck: 1, 2, 3, 5, 8, 13, 20, 40, 100 and "?" (true Fibonacci up to 13, then rounded values). The gaps between numbers widen as values grow, mirroring increasing uncertainty for larger pieces of work. This prevents false precision and encourages teams to break down large tasks: anything above 13 is usually a sign the story should be split.
How do I calculate story points for a task?
Use a weighted approach: complexity (35%), effort (30%), risk/uncertainty (20%), and dependencies (15%). Input your ratings (1-5 scale) into the calculator, and it will suggest a card from the planning-poker deck (up to 13; above that it recommends splitting the story). Remember: story points represent relative effort, not time. A 5-point task isn't necessarily twice the time of a 3-point task.
What's the difference between story points and hours?
Story points estimate relative effort, while hours estimate actual time. Story points account for complexity, uncertainty, and risk that hours often miss. A 3-point task might take 2 hours for one developer and 6 hours for another, but both would agree it's 3 points. This makes story points more reliable for sprint planning and velocity tracking.
How do I estimate story points in a team?
Use Planning Poker: each team member privately selects a point value, then all reveal simultaneously. Discuss discrepancies and reach consensus. Start with a baseline task (assigned 3 points), then compare other tasks to it. The calculator's output should be a starting point for discussion, not a final answer.
Can I use different scales instead of Fibonacci?
Yes! Teams can use T-shirt sizes (S, M, L, XL), powers of 2 (1, 2, 4, 8, 16), or custom scales. Fibonacci is popular because it naturally represents increasing uncertainty. The key is consistency - once you choose a scale, stick with it across all estimates for accurate velocity tracking.
Jira is a trademark of Atlassian. Binary Decimal is not affiliated with or endorsed by Atlassian.