Story Points Calculator
The formula
What the story points tells you
Attainment of story points against a target, with the absolute gap and the weighted contribution for scorecard roll-ups.
Calculation: attainment = actual ÷ target × 100; weighted contribution = attainment × weight. Enter your inputs and every substitution is shown below the result.
Reading the result
Green scores with soft targets flatter; audit the target, not just the result.
Limitations and best practice
One weighted line hides in a dashboard — a 90 % composite can be a 120 % and a 40 % wearing makeup.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Is 100 % always good?
How do I weight lines?
Source & methodology
Balanced-scorecard attainment arithmetic.
Story Points explained: formula, worked example and honest limits
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. There are plenty of pages about Story Points; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.
Like most useful measures, Story Points is a summary, and summaries hide as much as they reveal. The companion outputs and the input table are here to reopen what the headline compressed.
What makes Story Points worth calculating is not precision but position: it tells you which side of a threshold you are on, and by how much. A rough figure that settles the direction beats an elaborate one that never commits.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to attainment score = 70.4% on the default inputs, and the sensitivity section ranks the inputs that move the result — Target / benchmark first, at ≈11.1 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
Inside the Story Points calculation: formula and every input
The engine implements a single stated model: attainment = actual ÷ target × 100; weighted contribution = attainment × weight. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Actual / achieved (example value 88) is a measured number in the unit named by the label; the formula does not convert for you. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Target / benchmark (example value 125) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Weight of this line in the whole (example value 1) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Stay in one unit system top to bottom; conversion rounding is where small errors enter.
Story Points on the example inputs: the complete substitution
The tool prints its own working; this is the same arithmetic on the example values, reproduced so you can follow it by hand. Starting figures: Actual / achieved, Target / benchmark, Weight of this line in the whole. Run to the end, the attainment score resolves to 70.4% — Material miss — this line needs intervention, not encouragement on the bands this tool uses.
- Attainment = 88.0 ÷ 125.0 = 70.4 %
- Gap = 37.0 units
Gap to target — 37.0. This is the number experienced users quote when the headline alone would mislead.
Gap as % — 29.6%. This is the number experienced users quote when the headline alone would mislead.
Weighted contribution — 70.4. Compare it against the main result of 70.4% before drawing conclusions.
Re-running with your own figures is instant; re-running by hand once is the best way to know the tool is telling you the truth.
The Story Points corridor: your result across a realistic band
Single-point answers invite false confidence, so the same engine was run across a band around the input that matters most here. Each row is a full recalculation of Story Points, not an interpolation.
| Target / benchmark setting | Attainment score |
|---|---|
| 80 % of the example value | 88.0% |
| 90 % of the example value | 78.2% |
| example inputs | 70.4% |
| 110 % of the example value | 64.0% |
| 120 % of the example value | 58.7% |
That spread — 58.7% at the low end, 88.0% at the high — is what a careful read of Story Points looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Target / benchmark alone; the substitution steps will follow your figures exactly.
What actually moves your Story Points
Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the attainment score. Read it as a map of where Story Points is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- Nudge Target / benchmark by ±10 % and Story Points lands between 64.0% and 78.2% (sensitivity ≈11.1 %)
- Nudge Actual / achieved by ±10 % and Story Points lands between 63.4% and 77.4% (sensitivity ≈10.0 %)
Target / benchmark is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 64.0% to 78.2%. That is where a careless figure does the most damage, so check it against a source, and treat Actual / achieved as the second priority (≈10.0 % per ten percent). The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
Reading the result: bands, zones and thresholds
A number on its own is trivia; a number against a range is intelligence. The verdict attached to the default calculation — “Material miss — this line needs intervention, not encouragement” — is one band on a ladder your own figure may sit somewhere else on. Before treating the band as fact, note its width: ten percent either way on Target / benchmark already spans 64.0% to 78.2%. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
Set Story Points beside its neighbours and it usually plays a specific role: this figure establishes the size of something, and the neighbouring tools establish whether that size is acceptable. Skipping the first step makes the second one arbitrary.
Common mistakes with Story Points (and the fix)
One weighted line hides in a dashboard — a 90 % composite can be a 120 % and a 40 % wearing makeup. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Using stale inputs. Story Points is only as current as the numbers behind it — an estimate carried over from a previous season, rate table or report quietly biases every output. Re-measure the inputs first; that single habit fixes more bad Story Points figures than any formula change.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: Target / benchmark first, everything else second.
The subtlest error is answering the wrong question precisely. Confirm that attainment score is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
Before you trust your Story Points: a short checklist
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Compare the output against one published benchmark or a colleague’s independent estimate.
- Put Target / benchmark under a magnifier; the sensitivity table above is the reason why.
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Compare the result with one independent method or published benchmark.
- Confirm the answer against one independent method or published benchmark for Story Points.
How to use the Story Points tool properly
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — collect, then type. Everything this tool asks for is listed above (actual / achieved, target / benchmark, weight of this line in the whole). Pull each figure from something you can point at — paperwork, a dashboard, a label — before touching a field. Guesswork at the input stage cannot be repaired at the interpretation stage. If a result feels obviously right, that is the moment to check the inputs hardest.
Step 2 — baseline before exploration. Get one defensible Attainment score on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. Rounding early is the quietest way to introduce a permanent error.
Step 3 — isolate your variables. Change one field, observe, revert. The live sensitivity list does the ranking for the default inputs; verify it against your own, because dominance shifts when the starting point shifts. Compare the calculation to the rough guess you arrived with, and ask why they differ.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. Most surprises in numbers are surprises about inputs, not about formulas.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 70.4%, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Where Story Points matters in practice
Technology & Computing arguments end at arithmetic or they do not end. Story Points is the arithmetic: 70.4% on the example inputs, reproducible by anyone who types the same numbers. Compare the calculation to the rough guess you arrived with, and ask why they differ.
The companion outputs — Gap to target and Gap as % — exist for the second stage of that screen: the headline sizes the prize, while the companions describe the trade-off you are accepting to get it. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
There is a personal-administration use people overlook: periodic self-checking. Story Points quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.
The questions that come up most about Story Points
What affects Story Points the most?
Measured on this engine, Target / benchmark is the dominant lever: moving it ±10 % shifts the attainment score across 64.0% to 78.2% — about 11.1 % of the headline, with Actual / achieved next at ≈10.0 %. The ranked list in the sensitivity section is computed live, not asserted from a template.
Which matters more: actual / achieved or target / benchmark?
For Story Points, Target / benchmark wins the head-to-head (≈11.1 % against ≈10.0 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical Story Points?
There is no honest universal average for Story Points, but there is a reference point: the defaults on this page produce 70.4% (Material miss — this line needs intervention, not encouragement). Replace the inputs with your own and compare — that comparison is the useful meaning of “typical”.
How do I calculate Story Points by hand?
attainment = actual ÷ target × 100; weighted contribution = attainment × weight is the entire method. Work the inputs in that order — Attainment = 88.0 ÷ 125.0 = 70.4 % — and you will reach 70.4% on the default figures, the same number this tool prints.
What happens to Story Points if target / benchmark changes by 10 %?
The engine was re-run with that field moved by ten percent while everything else stayed fixed: the attainment score goes across 64.0% to 78.2%, a swing of roughly 11.1 % around the 70.4% baseline. That ratio is the practical definition of how much this input matters.
Is the Story Points result of 70.4% good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Story Points sit against the 70.4% reference above, how far would a plausible input error move it (≈11.1 % per ten percent on Target / benchmark), and what does the alternative option compute to?
How often should I check Story Points?
Whenever an input changes by more than a few percent, and otherwise on the rhythm of your decisions — before a purchase, a review, a renewal. Story Points is a snapshot, not a subscription; stale snapshots are the most common silent error in Technology & Computing planning.
Which model does Story Points use?
The stated formula: attainment = actual ÷ target × 100; weighted contribution = attainment × weight. It is the same arithmetic the vendor calculators and standards documents implement; differences appear only where vendors tune hidden coefficients, which the pitfall section above flags.
Is 100 % always good?
Only if the target was set honestly; consistently hitting exactly 100 % suggests sandbagged targets.
How do I weight lines?
By consequence — revenue and safety earn higher weights than administrative metrics.
Do I need an account to use this Story Points calculator?
No, and no data leaves the tab. The engine runs in the page itself, which is why the worked example, the bands and the sensitivity ranking all respond instantly to your keystrokes.
The vocabulary of Story Points
- Gap to target
- 37.0 in the default Story Points calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Gap as %
- 29.6% on the example inputs — a companion figure printed beside the headline of Story Points so that no result is read in isolation.
- Weighted contribution
- 70.4 on the example inputs — a companion figure printed beside the headline of Story Points so that no result is read in isolation.
- Attainment score
- The primary output of this tool: 70.4% for the default inputs, computed exactly from attainment = actual ÷ target × 100; weighted contribution = attainment × weight.
- Worked example
- Every substitution in order, from the example inputs to 70.4% — the audit trail for the headline figure.
- Verdict band
- The interpretation attached to a result (“Material miss — this line needs intervention, not encouragement” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Story Points moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
The provenance of this Story Points calculation
The model is published arithmetic implemented exactly as written: attainment = actual ÷ target × 100; weighted contribution = attainment × weight. Source of record: Balanced-scorecard attainment arithmetic. Any other implementation of this model should return the same figure for the same inputs. If one does not, the difference is in its assumptions — which this page prints and that one probably does not.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.
Next steps after the calculation
Save the number together with its inputs and today’s date; a Story Points figure without context is unusable the moment an input changes.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.