{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "@id": "https://www.vidyasource.com/blog/fibonacci-theater-adding-mathematical-mystique-to-scrum-estimation/",
  "url": "https://www.vidyasource.com/blog/fibonacci-theater-adding-mathematical-mystique-to-scrum-estimation/",
  "mainEntityOfPage": "https://www.vidyasource.com/blog/fibonacci-theater-adding-mathematical-mystique-to-scrum-estimation/",
  "headline": "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.",
  "datePublished": "2025-01-18T00:00:00.000Z",
  "author": {
    "@type": "Person",
    "name": "Neil Chaudhuri",
    "jobTitle": "President",
    "url": "https://www.linkedin.com/in/neil-chaudhuri/",
    "sameAs": "https://www.linkedin.com/in/neil-chaudhuri/"
  },
  "publisher": {
    "@id": "https://www.vidyasource.com/#organization"
  },
  "image": "https://www.vidyasource.com/img/blog/fibonacci.jpg",
  "keywords": [
    "Agile",
    "Scrum",
    "Project Management",
    "Software Engineering",
    "Testing",
    "Continuous Integration"
  ],
  "articleBody": "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.\n\n![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)\n\nStory points are the fundamental metric in Scrum, which through sustained, effective marketing has become the default agile methodology. Story points have been a source\nof confusion for decades because it's easy to mistake what they represent. Story points\nare 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\nrelative 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.\n\nAnother fundamental notion in Scrum, and really agile writ large, is uncertainty, which is a profound element of software engineering. We need to be intentional\nabout 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\nexponentially rather than linearly, Fibonacci numbers are a clever (if gimmicky) symbol of an idea—the idea that even the slightest increase in\nuncertainty yields a significant increase in our story point estimate.\n\nIt 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\nengineering effort and productivity or anything remotely provocative like that. It's just symbolic of the consequences of uncertainty.\n\nThe 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."
}