Story Points: How to measure work without counting hours?

In Agile and Scrum, teams use Story Points to estimate work, without being tied to hours or days. This helps with better planning and provides a more realistic view of the amount of work per Sprint. But how exactly does it work? And how do you determine the right Story Points for a User Story?

What are Story Points?

Story Points are a relative measure to determine the complexity, effort, and uncertainty of a backlog item. Instead of saying exactly "this will take 8 hours," the team compares backlog items with each other and assigns them a point score.

The estimate is based on:

• The amount of work – How many tasks are needed?
• The complexity – How complicated is the implementation?
• Uncertainty & risks – How many unknown factors are involved?

Why Story Points and not hours?

• Estimating hours is inaccurate – People are bad at estimating exact time, especially for complex tasks.
• Hours don't account for uncertainty – A simple task can become unexpectedly complex.
• Story Points focus on relative size – Teams learn faster what “a 3” versus “an 8” means.‍
• Better for teamwork – Not everyone works at the same pace; Story Points account for the team as a whole.

Comparison: Story Point estimation

"This will take 4 hours" (hours) VS "This is a 3" (compared to other Stories) (Story Points)

"This task is 16 hours of work" (hours) VS "This is an 8, because it's more complex than the previous Story of 5" (Story Points)

How do you determine Story Points?

‍

1. Planning Poker

A popular technique where team members each choose a card with a Story Point value and reveal them simultaneously. If there are significant differences, the team discusses why and arrives at a shared estimate.

‍

2. Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, …)

Many teams use the Fibonacci sequence because:

• The increments grow larger as complexity increases.
• This prevents overly precise estimates (no 7, but a 5 or 8).
• It helps to distinguish between small and large Stories.

‍

Story Points

Meaning

1: Very small, minimal effort

2-3: Small, simple task

5: Medium, a fair amount of work and some complexity

8: Large, complex, and with potential uncertainties

13+: Too large, likely needs to be broken down

‍

3. Comparing with reference items

By using a few previous User Stories as a reference, teams can estimate new Stories more quickly. For example:

• This Story feels about the same size as the previous 5-Story Point one.

How to use Story Points in Sprints?

• Calculating Velocity – A team's velocity is measured by the average number of Story Points completed per Sprint.
• Sprint Planning – Teams plan work based on their average Velocity.
• Continuous Improvement – After each Sprint, the team reviews whether their estimates were accurate and adjusts them as needed.

‍

Example of Velocity:

Sprint 1: 24 Story Points completed

Sprint 2: 27 Story Points completed

Sprint 3: 26 Story Points completed

👉 Average Velocity = 26 Story Points per Sprint

‍