Story Point Estimator

Estimate story points with a shared rubric for complexity, uncertainty, dependencies, risk, and effort.

Session basedExplainable outputCalibration ready

Why this starts simple

A stable rubric makes early adoption easier than opaque automation or external integrations.

Extension path

Future extensions can add saved calibration profiles, team-specific scales, and historical benchmarking.

Guided questionnaire

Story point estimator

The current calibration lives inside the shared session, so teams can reopen the same scoring discussion later.

Work item titleDescriptionWork item link

Complexity5 / 8

How tricky is the implementation or design space?

Uncertainty3 / 8

How much is still unknown or likely to change?

Dependencies2 / 8

How much outside coordination is required?

Risk4 / 8

How likely is rework, failure, or production impact?

Effort5 / 8

How much execution work is involved overall?

Calibration

Guide

How story point estimation works

What is a story point estimator?

A story point estimator gives teams a shared frame for comparing work by effort, complexity, uncertainty, risk, and dependency load.

How story points are estimated

Teams score a work item across a few dimensions, apply agreed weights, and then map that normalized score onto a point scale.

Complexity vs effort in agile estimation

Effort describes how much work is involved. Complexity reflects how tricky the work is. Strong estimates usually consider both, not just one.

FAQ

Story points are not the same as hours. Fibonacci is the most common scale. Teams usually get better results when estimation is done together, not by one person alone.

Suggested point

3 points

Suggested 3 points because effort carries the strongest weight in the current rubric.

Normalized score3.98

Highest driverEffort-heavy

ItemSearch results redesign