Stop 07 · Agile, Execution & DeliveryTopics · 6/12

Story Pointing & Estimation

Part of the Product Management Roadmap

In short

Humans are bad at guessing hours but decent at saying "this is about twice as big as that". Story points use that strength.

Assigning relative effort scores (often Fibonacci numbers) to backlog items instead of hours — because relative sizing tends to be more accurate than absolute time estimates.

The purple blob holds a watermelon in one hand and a mango in the other at a fruit stall.

Think of it like this

Watermelon vs mango

At the fruit stall, without a scale, you can't say a watermelon weighs exactly 4.2 kg. But you know at once it's much heavier than a mango. Story points work the same way: compare sizes, don't measure them.

Watch it happen

Planning poker with Fibonacci cards

1
0
2
1
3
2
5
3
8
4
13
5

1/5Cards follow a Fibonacci-like scale. The gaps grow because bigger work is harder to size precisely.

The big ideas

What you need to know

Relative, not hours

Points compare effort, complexity and uncertainty against a reference story the team knows.

Vote in secret

Revealing together stops everyone copying the senior engineer's number.

Gaps start conversations

A 3 and a 13 on the same story means someone knows something others don't.

Velocity is for the team

Points help a team plan its own sprints. They're not for comparing teams.

Save yourself the pain

Common mistakes

Oops

Converting points to hours, like "1 point = 4 hours".

Do this instead

Keep points relative. Converting brings back all the problems of hour estimates.

Oops

Comparing two teams' velocities to judge performance.

Do this instead

Each team's scale is different. Velocity only helps that team plan.

Your mission

Play planning poker

~25 min

Quick check

In planning poker, why does everyone reveal their card at the same time?

Go deeper

  1. 1Practice Planning Poker-style estimation with a small group on hypothetical stories.
  2. 2Learn why story points measure complexity and uncertainty, not just time.
  3. 3Understand velocity: how a team's average points-per-sprint helps forecast future work.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge