---
title: "Fibonacci Theater: Adding Mathematical Mystique to Scrum Estimation"
description: "Story points are the fundamental metric in Scrum, but using the Fibonacci Sequence to estimate them is more gimmick than substance."
canonical: https://www.vidyasource.com/blog/fibonacci-theater-adding-mathematical-mystique-to-scrum-estimation/
type: article
published: 2025-01-18
author: "Neil Chaudhuri"
tags: ["Agile", "Scrum", "Project Management", "Software Engineering", "Testing", "Continuous Integration"]
image: https://www.vidyasource.com/img/blog/fibonacci.jpg
---

# Fibonacci Theater: Adding Mathematical Mystique to Scrum Estimation

> Story points are the fundamental metric in Scrum, but using the Fibonacci Sequence to estimate them is more gimmick than substance.

- Canonical page: https://www.vidyasource.com/blog/fibonacci-theater-adding-mathematical-mystique-to-scrum-estimation/
- Structured data (JSON-LD): https://www.vidyasource.com/blog/fibonacci-theater-adding-mathematical-mystique-to-scrum-estimation.json
- Published: 2025-01-18
- Author: Neil Chaudhuri
- Topics: Agile, Scrum, Project Management, Software Engineering, Testing, Continuous Integration

I saw this question on LinkedIn and hear it a lot, so I figured I'd write a post for anyone else wondering the same thing.

![Scrum Masters & Agile Coaches: Why do we use Fibonacci Sequence 1,2,3,5,8 etc. for estimation instead of just Natural numbers like 1,2,3,4 etc?](https://www.vidyasource.com/img/blog/fibonacci-question.jpeg)

Story points are the fundamental metric in Scrum, which through sustained, effective marketing has become the default agile methodology. Story points have been a source
of confusion for decades because it's easy to mistake what they represent. Story points
are not hours or a measure of anything particularly concrete but rather a fuzzy representation of the size, scope, complexity, and value of a software feature
relative to one another. Assigning one feature 2 points is marginally useful, but knowing that feature is a lot easier than that 8 over there is much more useful.

Another fundamental notion in Scrum, and really agile writ large, is uncertainty, which is a profound element of software engineering. We need to be intentional
about recognizing what we don't know yet. Story point estimates grow less and less useful with more and more uncertainty. Because the Fibonacci Sequence grows
exponentially rather than linearly, Fibonacci numbers are a clever (if gimmicky) symbol of an idea—the idea that even the slightest increase in
uncertainty yields a significant increase in our story point estimate.

It is really important to remember that the inclusion of fancy-seeming math-iness like Fibonacci in Scrum is not some kind of research-derived correlation between
engineering effort and productivity or anything remotely provocative like that. It's just symbolic of the consequences of uncertainty.

The confusion around Fibonacci's relevance to Scrum is one example of why I believe story points are the key reason Scrum fails so often, but that is a story for another day.

---

Vidya is a certified small business in Northern Virginia that modernizes legacy systems, builds enterprise AI, and designs cloud and data architecture for commercial companies and federal agencies. Vidya documents its delivered engagements in case studies and publishes courses, tutorials, and articles for engineers and the people who lead them. The company name is Vidya. Its website is vidyasource.com. Start at https://www.vidyasource.com/llms.txt for the index of everything Vidya publishes, or https://www.vidyasource.com/contact/ to talk to Vidya.