Estimation field guide

Story Points Are Not Time Estimates

A story point is a relative estimate, not a fixed number of hours. That distinction matters when teams discuss size, plan capacity and communicate uncertainty.

Relative size needs a shared reference

A team can judge one story as larger than another without predicting its exact completion time. A point scale expresses that relative judgment using reference work the team understands. The estimate should include the work needed to finish the item, not just writing the first implementation.

Teams use story points in different ways. Agree on what your scale means and keep the references visible. A point from another team is not automatically comparable, even if both teams use the same Fibonacci-style cards.

Why “one point equals four hours” breaks down

A fixed conversion implies more stability than the work usually has. Two similarly sized stories can take different amounts of elapsed time because of interruptions, review queues, dependencies or unexpected discoveries. Even the effort required can vary with the people and context involved.

If stakeholders need an estimate in hours for a specific decision, discuss that need explicitly. Do not disguise the same hour estimate by dividing it by four and calling it story points. Explain the assumptions, the work included and the uncertainty in the requested unit.

The same size does not promise the same date

Illustrative example — not a customer report

Imagine two export improvements the team rates similarly. One uses well-understood data and can move through testing immediately. The other waits for access to a representative dataset. The waiting changes when the work can finish; it does not mean that every point in the team’s scale has acquired a new hourly value. Record the dependency and account for it in the delivery conversation.

Use history as evidence, not a guarantee

For a reasonably stable team, completed work from recent iterations can inform a forecast of how much similarly estimated work it may finish next. Consider several observations, changing availability and differences in the upcoming work. A range is often more honest than a single date derived from a fixed multiplier.

  • Use the same team’s history and check whether its estimation scale changed.
  • Separate the size of the work from availability, waiting time and external deadlines.
  • Update forecasts when new evidence appears; do not turn velocity into an individual performance target.

Keep estimation and scheduling connected but distinct

In refinement, clarify complexity, effort and risk. In planning, combine that understanding with capacity, dependencies and the team’s delivery history. Consonus uses scope as the middle dimension by default; teams can choose time instead. Either way, the output comes from your configured weights and mapping. A time rating does not automatically make one story point equal a fixed number of hours.

Ready for clearer estimates?

Bring one story to Consonus. Compare your team’s complexity, effort and risk ratings, discuss the different assumptions and agree on your next step.

Free during public preview. No payment details required.