How to Use the Fibonacci Scale to Estimate Story Points
We focus on processes to effectively and efficiently develop digital products. One of our processes is using Agile Development, which includes using Agile Story Points to assign a common definition to the effort required to complete tasks.
Table Of Contents
What is the modified Fibonacci Sequence?
In this post, we’ll focus on the modified Fibonacci Sequence – 0, 1, 2, 3, 5, 8, 13, 21, etc – as an exponential complexity scale (good discussion on why, other than the cool name).
This definition of complexity should be shared by a whole team, from developers, product owners, project managers, executives, to anyone else who’d like to understand the nuances and complexities of developing digital products within this framework. The framework allows you and the organization to have visibility into timelines, complexity, budget, and staffing.
Why Use the Fibonacci Sequence for Estimation in Agile?
Why do we need this? Because humans are bad at estimating effort, especially when complexity increases. In software development, large features have hidden complexities that don’t become apparent until one is “in the weeds.”
However, every team is different. The purpose of using Agile Story Points is to agree on software project estimates in order to most effectively plan and execute product development (sprints, tasks, etc.).
