What's the difference between Story Points and Fibonacci?

Story Points are the estimation method. Fibonacci is the numeric scale many Scrum teams use when assigning Story Points.

Are Story Points measured in hours?

No. Story Points estimate relative effort, considering complexity, uncertainty, and the amount of work. They should not be converted directly into hours or days.

Should Product Managers estimate effort?

Product Managers can participate, but engineering teams are typically best positioned to estimate implementation effort. Cross-functional discussions often lead to better understanding, but engineering should generally own the final effort estimate.

Which estimation scale is best?

There isn't a universally best scale. Choose one your team understands, apply it consistently, and revisit it only if it stops supporting productive planning conversations.

Agile Estimation Scales

Every Agile team needs a way to estimate work. Some teams use Story Points. Others prefer Fibonacci, T-Shirt Sizes, or a simple 1-10 scale. A growing number of teams even choose not to estimate at all. The good news is that there isn't a universally 'correct' estimation scale. The best estimation scale is the one your team understands, applies consistently, and uses to have better conversations about work.

Why Estimate Work?

The purpose of estimation isn't to predict exactly how long something will take.

Instead, estimation helps teams:

Compare the relative size of work.
Plan upcoming sprints.
Discuss uncertainty.
Identify large or risky initiatives.
Improve forecasting over time.

Good estimation creates better conversations — not perfect predictions.

Story Points

Story Points are one of the most common Agile estimation methods.

Rather than estimating hours or days, Story Points measure the relative effort required to complete a piece of work by considering:

Complexity
Amount of work
Risk and uncertainty

A Story Point isn't a unit of time. A five-point issue doesn't necessarily take five days to complete.

Best for: Scrum teams, sprint planning, teams experienced with Agile.

Advantages: Encourages relative estimation. Accounts for uncertainty. Widely recognized across Agile teams.

Challenges: Often misunderstood as hours. Less intuitive for non-technical stakeholders.

Fibonacci

Many teams estimate Story Points using the Fibonacci sequence:

1, 2, 3, 5, 8, 13, 21

The gaps between numbers become larger as work grows because larger initiatives are naturally harder to estimate accurately.

Instead of debating whether something is an 11 or a 12, teams acknowledge the uncertainty and choose either an 8 or a 13.

Best for: Planning Poker, Scrum teams, teams estimating implementation effort.

Advantages: Reflects increasing uncertainty. Prevents false precision. Simple to facilitate during estimation sessions.

Challenges: Larger values can be difficult for new teams to interpret. Less meaningful outside Engineering.

T-Shirt Sizes

Instead of numbers, some teams estimate work using relative sizes:

XS · S · M · L · XL

This approach removes unnecessary precision and is particularly useful during early planning or roadmap discussions.

Best for: Product discovery, roadmap planning, cross-functional workshops.

Advantages: Easy for everyone to understand. Encourages relative thinking. Great for non-technical participants.

Challenges: Less useful for sprint forecasting. May eventually need to be translated into engineering estimates.

Numeric Scale (1-10)

Some teams prefer a simple numeric scale.

Each issue receives an effort score between 1 (very small) and 10 (very large).

This approach is easy to understand and works well when both technical and non-technical stakeholders participate in estimating work.

Best for: Product teams, cross-functional prioritization, collaborative scoring sessions.

Advantages: Easy to learn. Familiar to everyone. Flexible enough for most discussions.

Challenges: Teams need shared definitions for each value. Can create false precision if values aren't well understood.

No Estimates

Some Agile teams choose not to estimate work at all.

Instead of assigning Story Points or sizes, they focus on delivering consistently small work items and measuring actual throughput over time.

The goal is to spend less time estimating and more time delivering value.

Best for: Mature Agile teams, continuous delivery, teams with predictable flow.

Advantages: Eliminates estimation meetings. Encourages smaller backlog items. Focuses on delivery rather than prediction.

Challenges: Doesn't help compare large initiatives. Makes roadmap planning more difficult. Not suitable for every team or organization.

Comparing Estimation Scales

Story Points — best for Scrum; easy to learn: moderate; good for sprint planning: yes; good for cross-functional teams: limited.
Fibonacci — best for Scrum & Planning Poker; easy to learn: moderate; good for sprint planning: yes; good for cross-functional teams: limited.
T-Shirt Sizes — best for discovery & roadmaps; easy to learn: very easy; good for sprint planning: limited; good for cross-functional teams: yes.
1-10 Scale — best for product prioritization; easy to learn: very easy; good for sprint planning: yes; good for cross-functional teams: yes.
No Estimates — best for continuous delivery; easy to learn: moderate; good for sprint planning: no; good for cross-functional teams: yes.

Which Estimation Scale Should You Choose?

There isn't a universally correct answer. A good rule of thumb is:

New Agile teams: Start with T-Shirt Sizes or a simple 1-10 scale.
Scrum teams: Story Points using Fibonacci remain the most common approach.
Roadmap planning: T-Shirt Sizes encourage broader conversations without unnecessary precision.
Cross-functional teams: A 1-10 scale is often the easiest for everyone to understand.
Mature teams with stable delivery: Consider whether No Estimates fits your workflow.

The most important factor isn't the scale itself.

It's using the same scale consistently.

Estimation Isn't Prioritization

One common mistake is treating estimation as prioritization.

Estimation answers: How much work is this?

Prioritization answers: How important is this?

A large initiative may still be the highest priority.

A one-point task may be low priority.

Effort should inform prioritization — not replace it.

How CoJii Fits In

CoJii separates estimation from prioritization.

Teams estimate effort using the scale they're most comfortable with — whether that's Fibonacci, T-Shirt Sizes, or a 1-10 scale — while evaluating other prioritization dimensions such as Impact, Customer Signal, and Strategic Alignment independently.

This keeps effort as one important input without allowing it to dominate every prioritization decision.