Story points

What are story points?

Story points are the unit Agile teams use to estimate the relative effort, complexity, and uncertainty of backlog items. They're deliberately abstract. Instead of "this will take three hours," a story point says how hard a piece of work is compared to other work the team has done, without locking in a duration that nobody can honestly predict yet.

Teams usually assign them through planning poker: each person estimates privately, everyone reveals at once, and the group talks through any big gaps before agreeing. Most use the Fibonacci sequence (1, 2, 3, 5, 8, 13) because the widening jumps reflect how uncertainty grows with size. A five-point story is understood to be roughly twice the effort of a two-pointer. A login form might be a two, while a payment integration touching a third-party API lands at an eight, the higher number signalling risk as much as work.

Over time a team learns its velocity, the number of points it tends to finish per sprint, which makes forecasting possible. One caution: points are team-specific. They don't translate between teams, and using them as a productivity scoreboard breaks the honesty that makes them useful in the first place.

Story points at Dallonses

We estimate in story points to keep conversations about difficulty, not deadlines. When we tell a client a feature is an eight, we're flagging risk and complexity, not promising a number of hours we'd have to defend later. That framing leads to better calls about what's worth building and what to cut.

We use velocity to forecast, never to grade. The point of tracking it is a more reliable answer when a client asks what fits in the next month, not a leaderboard. Estimation stays a planning tool, which is the only way it keeps telling the truth.

Want estimates that flag real risk instead of inventing false deadlines? Let's plan your next build.

Talk to us about planning