Articles → PROJECT MANAGEMENT → Fibonacci Estimation Technique In Agile

Fibonacci Estimation Technique In Agile

This article explains the Fibonacci estimation technique in Agile.

Purpose

The Fibonacci estimation technique is commonly used in Agile, especially in Scrum, to estimate the effort, complexity, or size of tasks and user stories. It uses the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, and so on), where each number is the sum of the two preceding numbers.

How Does The Fibonacci Estimation Technique Work?

Relative Estimation

Instead of assigning exact hours or days, the Fibonacci sequence helps teams estimate the relative size of tasks, emphasizing that complexity, uncertainty, and risk increase with higher numbers.

Simplicity and Focus

The Fibonacci sequence has noticeable gaps between numbers as the sequence progresses, which makes it easier for teams to decide if a task is, for instance, a 5 or an 8, instead of getting trapped in small differences like 6 vs. 7.

Estimation in Story Points

Teams usually use Fibonacci numbers as story points assigning, a story point value to each user story based on its complexity and the effort required.

Planning Poker

Each member privately selects a Fibonacci number card that they believe represents the effort needed. The team then discusses the estimates and reaches a consensus on the final story point.

Scenario

Consider the following user stories.

Scenarios
As a user I want to be able to log in so that I can access my personal account.
As a user I want to be able to search for products so that I can find what I am looking for.
As an admin I want to be able to view sales reports so that I can understand business performance.

User Story 1: User Login

The team considers this a straightforward task, though it requires careful attention to authentication and security considerations. Overall, the complexity is moderate with limited uncertainty.

The team estimates this effort at 3 story points.

User Story 2: Product Search

Implementing the search feature will involve database queries, indexing, and UI integration. Additional complexity may arise from search filters and optimization requirements.

After discussion, the team concluded that this user story is more complex than the login functionality and assigned it 8 story points.

User Story 3: Sales Report For Admin

Generating a sales report involves data processing, multiple report components, and potentially visualizations. In addition, there is some uncertainty regarding the exact data requirements and possible changes after stakeholder feedback.

Considering this complexity and ambiguity, the team estimates this story at 13 story points.

Posted By -	Karan Gupta

Posted On -	Sunday, November 24, 2024

Query/Feedback

Your Email Id		**

Subject		*

Query/Feedback	Characters remaining 250	**