Skip to main content

In the realm of agile estimation or story point estimations, utilizing the Fibonacci numerical sequence can be a powerful technique for estimating effort. This blog post delves into how this mathematical series can be applied and adapted to improve estimation accuracy within IT projects, particularly those involving complex tasks and large teams.

We’ll begin by examining the traditional Fibonacci sequence and its adaptation for agile estimation purposes. Next, we’ll explore Weber’s Law and its impact on effort estimation in relation to distinguishing weights.

Moving forward, we will discuss modifications to the traditional Fibonacci sequence tailored to agile teams. We will also compare different planning poker sequences, such as modified Fibonacci vs simple doubling, and factors influencing their selection.

Lastly, we will emphasize the importance of accurate estimations in agile projects using the Fibonacci Agile Estimation method while highlighting its benefits in enhancing overall project success rates.

Table of Contents:

The Fibonacci Sequence in Agile Project Management

This mathematical concept, which models natural phenomena like spirals in shells and branching patterns in trees, has been adapted to enhance agile estimation. Normally used during Sprint Planning, Scrum development teams use this approach to estimate the relative size of User Stories or Product Backlog Items. The adaptive nature of the sequence works especially well when used in conjunction with agile estimating approaches such as planning poker. Additionally, the sequence works when evaluating smaller or larger user stories, complex tasks, complex stories and large projects. As long as the Scrum team establishes a relative baseline, the sequence supports teams in estimating size.

Understanding the Traditional Fibonacci Sequence

The traditional Fibonacci sequence begins with 0 and 1, followed by subsequent numbers such as 1, 2, 3, 5, 8 and 13. Agile teams use this sequence to assign effort points to tasks or user stories during planning poker sessions. It’s a simple and intuitive way to compare relative sizes without getting bogged down in exact figures.

Adapting the Sequence for Agile Estimation

Some IT professionals have modified the original sequence to better suit their needs. For example, they may skip certain values or use rounded-off alternatives with higher increments between subsequent elements. This flexibility allows teams to choose a sequence that best fits their specific project requirements and preferences.

Popular modified Fibonacci sequences used in agile estimation include 0, 1, 2, 3, 5, 8, 13…20 (skipping the number “21”), and even adding larger increments such as …40-100 for extreme values. By consistently using the Fibonacci sequence or its variations throughout the project lifecycle, teams can estimate workloads effectively and foster healthy discussions.

Weber’s Law and Its Impact on Estimation

Weber’s Law is a psychological principle that states humans can perceive differences between objects based on percentages rather than absolute values. This concept plays a significant role in the estimation process, particularly when it comes to agile estimating. By understanding Weber’s Law and its implications, IT professionals can improve their ability to estimate tasks or user stories accurately.

Distinguishing weights as an example of Weber’s Law

One classic demonstration of Weber’s Law involves comparing two different weights. If two weights are held, the heavier one may be noticed if it is more than 10% in mass compared to the lighter one. If the two weights are almost equal in mass, it is difficult to perceive any difference between them.

This phenomenon suggests that our perception of differences relies on relative comparisons rather than exact measurements. In other words, we’re better at judging how much more effort something might require compared to another task instead of determining precise numerical values for each job.

How Weber’s Law applies to effort estimation

In agile projects, teams must estimate the amount of work required for various tasks. Traditional methods like using hours or days often lead to inaccurate predictions due primarily because they don’t account for human perceptions governed by Weber’s Law.

  • Focusing on relative sizes: Agile teams should focus on comparing tasks’ sizes relatively instead of trying to assign specific timeframes or numeric values directly related to actual working hours/days involved.
  • Using percentage-based increments: Agile teams can use percentage-based increments when estimating efforts to accommodate this natural tendency. This approach aligns with the Fibonacci sequence commonly used in agile estimation, which features a series of numbers where each number is approximately 1.618 times larger than its predecessor.
  • Avoiding false precision: By using relative sizes and percentages instead of exact figures, teams can avoid falling into the trap of false precision – believing that their estimates are more accurate than they are.

Weber’s Law highlights the importance of focusing on relative comparisons rather than attempting to pin down specific values when estimating tasks’ efforts in an agile project. By understanding this psychological principle and applying it to their estimation process, IT professionals can make better predictions about how much work will be required for different tasks or user stories within a project.

The Role of Fibonacci Agile Estimation

Fibonacci Agile Estimation leverages Weber’s Law by providing a fixed set of values based on the Fibonacci sequence or its modified versions. These values help teams focus on comparing tasks’ relative sizes without getting bogged down in trying to assign precise numerical estimates for each job. As a result, this method fosters healthy discussions among team members while also improving overall accuracy in effort estimations.

Key Takeaway: 

Weber’s Law is a psychological principle that affects agile estimation by highlighting the importance of focusing on relative comparisons rather than exact measurements. Teams can use percentage-based increments to accommodate this and avoid false precision when estimating efforts. Fibonacci Agile Estimation leverages Weber’s Law by providing a fixed set of values based on the Fibonacci sequence to improve accuracy in effort estimations while fostering healthy discussions among team members.

Modifying the Fibonacci Sequence for Agile Teams

Agile teams used the real Fibonacci sequence for estimation, but they soon realized it was too precise for their needs. So, they started modifying it by rounding off numbers and adding larger increments to better account for uncertainty and complexity in software development projects.

Why modify the traditional sequence?

The main reason for adapting the sequence is to prevent over-optimism or underestimation by encouraging team members to consider a range of possible outcomes. This approach helps improve estimation accuracy while still maintaining the benefits of relative sizing.

Experimenting with different sets of numbers

Agile teams can explore various numerical combinations to discover the most suitable requirements. Some popular alternatives include T-Shirt Sizes, Powers of Two, and Fibonacci-Like Sequences.

  • T-Shirt Sizes (XS, S, M, L, XL) provide a straightforward way to classify tasks in terms of size without needing exact numerical values.
  • Powers of Two (1, 2, 4, 8…): This method doubles each value in the series which might be more suitable for projects where efforts tend to increase exponentially rather than linearly.
  • Fibonacci-Like Sequences (0.5, 1, 2, 3, 5…): These sequences combine elements of both the traditional Fibonacci sequence and other modified versions to create a more flexible estimation scale.

It’s important to keep in mind however that story points should be tailored to each team’s context rather than following a strict formula or rule.

Modifying the Fibonacci sequence allows agile teams to make accurate estimates while benefiting from the relative sizing approach. By experimenting with different sets of numbers and adapting them based on project requirements and experiences, teams can improve their ability to estimate tasks with varying levels of complexity and effort required.

Key Takeaway: 

Agile teams have modified the Fibonacci sequence for estimation by rounding off numbers and adding larger increments to account for uncertainty and complexity in software development projects. This approach prevents over-optimism or underestimation, improves estimation accuracy while maintaining relative sizing benefits, and allows teams to experiment with different sets of numbers tailored to their context.

Planning Poker Sequences Comparison

Various planning poker sequences have been developed, including modified versions inspired by doubling and rounding off. While no definitive studies prove one method superior, successful teams find their preference based on individual experiences.

Modified Fibonacci Sequence vs Simple Doubling

The Modified Fibonacci sequence is famous for agile estimation because it balances precision and uncertainty. By using rounded values like 20 or introducing larger increments such as 40 and 100, this approach helps teams make more accurate estimates while fostering healthy discussions about relative sizes and efforts required for different tasks.

In contrast, simple doubling sequences like (1, 2, 4, 8…) may not provide enough granularity in estimating efforts for tasks that fall between these numbers. Assigning either number could lead to inaccuracies in overall project estimations.

Factors Influencing the Choice of Planning Poker Sequences

  • Team Experience: Familiarity with different estimation methods can play a significant role in choosing which sequence works best. Teams experienced with Fibonacci-based approaches might prefer sticking to those techniques due to their established understanding.
  • Nature of the Project: The complexity and size of a project can influence which sequence is most suitable. Larger projects with more intricate tasks may benefit from using modified Fibonacci sequences that provide greater flexibility in estimating efforts.
  • Estimation Accuracy Requirements: Depending on the level of precision required, teams might opt for a simple doubling or rounding-off approach to ensure they meet their estimation goals without overcomplicating the process.

It’s important for agile teams to experiment with different planning poker sequences and find what works best for them based on their unique circumstances. By understanding the advantages and limitations of each method, they can make informed decisions about which approach will lead to better estimations and ultimately contribute towards successful project delivery. Check out Scaled Agile Framework for more information on agile estimation and planning.

Key Takeaway: 

Agile teams use various planning poker sequences for estimation, including modified Fibonacci and simple doubling. The choice of sequence depends on factors such as team experience, project complexity, and accuracy requirements. Teams should experiment with different approaches to find what works best for them and make informed decisions about which method will lead to better estimations.

The Importance of Reliable Estimation in Agile Projects

Estimation is needed for agile teams to manage workloads, prioritize tasks, and deliver projects on time and within budget. By using a fixed set of values based on the Fibonacci sequence or its modified versions, teams can improve their ability to make reliable estimates while fostering healthy discussions about relative sizes and efforts required for different tasks.

Benefits of Reliable Estimation in Agile Development

  • Better resource allocation: Good estimations help team members allocate resources efficiently, preventing overcommitting or underutilizing resources.
  • Prioritization: Knowing the relative size of tasks allows product owners and stakeholders to prioritize them based on factors such as business value, risk mitigation, or dependencies with other tasks.
  • Informed decision-making: Accurate estimates provide valuable insights into project progress and help identify potential bottlenecks or areas requiring additional attention.
  • Faster delivery: Clear understanding of the effort involved in completing various tasks helps teams better plan their workloads and avoid delays caused by inaccurate estimations.

How the Fibonacci Sequence Contributes to Better Estimations

The use of the Fibonacci sequence (or its modified versions) provides several advantages when it comes to estimating efforts in agile projects:

  1. Avoiding false precision: Rounded numbers used in modified sequences discourage assigning overly precise estimates, which can lead to unrealistic expectations and missed deadlines.
  2. Encouraging collaboration: Using a fixed set of values like the Fibonacci sequence fosters healthy discussions among team members about relative sizes and efforts required for different tasks.
  3. Accounting for uncertainty: The non-linear nature of the Fibonacci sequence acknowledges the inherent uncertainty involved in software development projects.

Incorporating the Fibonacci sequence into your estimation process effectively improves accuracy while promoting teamwork and communication within your organization. By grasping its advantages and adjusting it to meet your team’s prerequisites, you can accomplish worthwhile ventures on schedule and inside the spending plan.

Key Takeaway: 

Accurate estimation is crucial for agile teams to manage workloads, prioritize tasks, and deliver projects on time and within budget. The use of the Fibonacci sequence (or its modified versions) provides several advantages when it comes to estimating efforts in agile projects while promoting teamwork and communication within your organization. Incorporating this technique into your agile estimation process can improve accuracy and lead to successful project delivery.

FAQs in Relation to Fibonacci Agile Estimation

What is the Fibonacci Sequence in Agile Estimating?

The Fibonacci Sequence is a series of numbers where each number is the sum of the two preceding ones, usually starting with 0 and 1 (0, 1, 1, 2, 3, 5, 8, 13, 21, and so on). In Agile estimating, these numbers are used to size user stories, tasks, or other pieces of work. The goal is to reflect the inherent uncertainty in estimating larger items.

Why is the Fibonacci Sequence used in Agile Estimating?

The Fibonacci Sequence is used because it balances accuracy and speed. It acknowledges that our accuracy diminishes as we try to estimate larger and more complex tasks. Using the Fibonacci sequence, we avoid the false precision of traditional estimating techniques and embrace the uncertainty in larger items. It is a way of recognizing that the bigger a task or story is, the more uncertainty it holds, and therefore the estimation numbers get increasingly spaced apart.

How do I use the Fibonacci Sequence in Story Points?

While estimating the relative size of user stories or tasks, team members will assign each a value from the Fibonacci Sequence based on its perceived complexity, risk, or effort required. It’s important to note that these points do not correlate to a specific amount of time but rather serve as a relative measure of effort.

What do the numbers in the Fibonacci Sequence represent in Agile?

Each number in the Fibonacci sequence represents a relative size or effort for a piece of work. Lower numbers (0, 1, 2) are typically used for small or simple tasks, while larger numbers (13, 21, 34, and beyond) are used for large, complex, or highly uncertain tasks.

What should we do if a story is larger than the highest number we use in the Fibonacci Sequence for estimation?

If a story is larger than the highest number in your typical estimating range, it often indicates that the story needs to be broken down into smaller, more manageable pieces. This makes the work easier to estimate, reduces risk, and provides more frequent feedback.

Does a Story Point equal a certain amount of time?

Story points are a measure of effort, not time. A common misconception is to equate a point to a specific number of man-hours or days. The idea is to create a normalized estimation scale that abstracts away from time and focuses more on relative effort and complexity.

Why don’t we use a linear sequence (1,2,3,4, etc.) for estimation?

A linear sequence implies a level of precision in estimation that doesn’t exist, especially for larger or more complex tasks. The use of the Fibonacci sequence helps to acknowledge the uncertainty and risk associated with larger tasks, as the gaps between numbers increase the larger you go.

The Fibonacci Sequence for estimation is just a tool – the conversation and collaboration during the estimation process provide the most value. The goal is to reach a team consensus on the relative effort involved in implementing a user story or a task.


Fibonacci Agile Estimation: The Key to solid Project Planning

Agile estimation can be daunting, but Fibonacci Agile Estimation is a powerful tool that can help IT and financial professionals accurately estimate effort in agile projects.

By adapting the traditional Fibonacci sequence for agile estimation and considering Weber’s Law, teams can improve accuracy and experiment with modified sequences to find the best fit for their project.

Comparing planning poker sequences and choosing the right one based on project factors can also contribute to better estimations, leading to numerous benefits in agile development.

Don’t underestimate the power of reliable estimation – make Fibonacci Agile Estimation an essential technique for success in your next project.


Learn with Fractal Systems!

Looking to upskill and boost your career prospects in the world of agile methodology? Look no further than Fractal Systems’ Agile Training!

Our team of real-world practitioners are active in the industry, so you can trust that the techniques you learn are tried and tested in real-life situations. Our training isn’t just a lecture-based session filled with boring PowerPoint slides – we know that interactive, discussion-based learning is the best way to ensure you retain what you’ve learned and are ready to apply it in your work.

Our Agile Training is not only informative but also enjoyable and fun! We believe that training shouldn’t be a chore, but an opportunity to develop new skills and meet like-minded professionals. Our sessions are designed to be fully interactive, with plenty of opportunities for discussion, group activities, and hands-on exercises.

By completing our Agile Training, you’ll gain valuable insights into the latest agile trends and techniques and be equipped with the skills and knowledge to apply them in your own workplace. Our team is dedicated to ensuring you get the most out of your training experience, and we’ll be with you every step of the way.

Don’t miss this opportunity to develop your career and enhance your skills. Sign up for Fractal Systems’ Agile Training today!

Further Agile Scrum Training

 Online Professional Scrum Master Training I (PSMI)

 Online Professional Scrum Master Training II (PSMII)

 Online Professional Scrum Product Owner (PSPO)

 Professional Scrum Product Owner Advanced (PSPO-A)

 Applying Professional Scrum (APS)