Fibonacci Story Point Estimation

The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34…) is the most widely used scale in planning poker. Teams pick the next number in the sequence rather than any integer because the gaps widen as work grows — matching how uncertainty increases with size. Estimating a small bug fix as either 2 or 3 points is meaningful; debating 20 vs 21 is not.

Why Fibonacci fits agile estimation

Story points measure relative effort, not hours. A 5-point story should feel roughly twice as complex as a 3-point story the team delivered recently. Fibonacci forces coarse buckets at the top of the scale, which pushes teams to split oversized work instead of pretending they can estimate huge epics precisely.

Cards in a standard planning poker deck

PlanITPoker's Fibonacci deck includes 1, 2, 3, 5, 8, 13, 21, and 34, plus two special cards:

• Question (?) — The story needs more information before you can estimate. Use this instead of guessing.
• Coffee break — You need a short pause. Keeps long sessions humane without derailing the room.

How teams calibrate Fibonacci points

Pick a reference story the whole team remembers — often a medium complexity item everyone agrees was a 5. New stories are compared to that anchor: "Is this about half the work? Then 3. Double? Then 8." Calibration drifts if the reference story is forgotten, so revisit anchors every few sprints.

When to pick a higher Fibonacci number

• Unknown dependencies or integration risk with external systems
• Work spanning multiple components, services, or teams
• Missing or vague acceptance criteria
• Significant research or spike work embedded in the story
• Performance, security, or compliance constraints that add hidden scope

When estimates cluster at 13 or above

That is a refinement signal, not a success. Stories at 13, 21, or 34 usually contain multiple deliverables masquerading as one ticket. Split them into independently valuable slices, estimate each slice, and sum only if your process allows composite pointing — many teams prefer pointing the smallest shippable increment instead.

Fibonacci vs other scales

Some teams use modified Fibonacci (1, 2, 3, 5, 8, 13, 20, 40) or powers of two. The exact sequence matters less than consistency. Switching scales mid-project breaks velocity trends. For early roadmap sizing without numeric points, consider T-shirt sizing first, then convert buckets to Fibonacci when stories mature.

Practice with PlanITPoker

Create a room, select the Fibonacci deck, and run a mock estimation on last sprint's stories to calibrate new team members. For the theory behind story points themselves, read Story Points Explained.