Common Story Point Problems

Close

Most story point problems are caused by how the estimates are used.

The numbers are usually not the problem. The trouble starts when points become days, velocity becomes a target, estimates become commitments, or teams are compared by raw point totals.

Story points work best when they help teams and Product Owners make better decisions under uncertainty.

Points Become Days

The most common story point problem is converting points to time.

A team says, "One point equals one day," because it wants story points to feel concrete. The rule seems helpful for a little while. Then the team is right back where it started.

Team members begin thinking about who will do the work and how fast that person will be. Stakeholders hear a time estimate and treat it as a commitment. Managers start asking why a three-point item took longer than three days.

When points become days, relative estimation disappears.

To fix this, return to comparison. Use baseline items. Ask whether a new product backlog item is larger or smaller than items the team has already estimated. Use velocity later for forecasting, but do not convert individual estimates into calendar time.

Estimates Become Commitments

An estimate is a planning input.

It helps someone make a decision about priority, scope, timing, cost, risk, or tradeoffs. It is not a promise that the work will take exactly that amount of effort.

When estimates are treated as commitments, teams protect themselves. They inflate estimates. They resist estimating. They avoid honest uncertainty. They may spend far too long trying to make every estimate defensible.

To fix this, be explicit about the decision the estimate supports. Also be clear about the uncertainty around the estimate. A Product Owner can use an estimate responsibly without pretending it is a guarantee.

Velocity Becomes a Target

Velocity is useful when it helps a team forecast.

It becomes harmful when it becomes a target.

If a team completed 30 points last sprint, someone may decide the team should complete 35 next sprint and 40 after that. That pressure encourages the team to increase the numbers assigned to work rather than improve the system.

Velocity is an observation. It is not a performance goal.

Teams can improve delivery, but higher velocity numbers do not prove improvement. The team may have estimated differently, split work differently, or inflated points under pressure.

To fix this, use velocity as an input to planning conversations. If leaders want better outcomes, look at flow, quality, team interruptions, backlog clarity, dependencies, and decision speed.

Estimate Inflation

Estimate inflation happens when an item receives more points today than a similar item would have received in the past.

It often begins subtly. A team is deciding whether an item is a two or a three. Under pressure to increase velocity, the team chooses three. The next item is slightly bigger, so it becomes a five. The scale starts moving.

The team may not notice until velocity appears to improve without any real improvement in delivery.

To fix estimate inflation:

  • Compare new items with baseline items
  • Review whether current estimates match similar past estimates
  • Avoid public velocity comparisons across teams
  • Keep velocity out of performance evaluation
  • Make estimates visible enough that obviously inflated estimates are awkward to defend

The best prevention is a healthy environment. Teams inflate estimates when the system rewards bigger numbers.

Teams Are Compared by Velocity

Story points are team-specific.

A five for one team may not mean the same thing as a five for another team. Teams have different baselines, different skills, different domains, different dependencies, and different ways of splitting work.

Comparing raw velocities across teams creates bad incentives. Teams may inflate estimates, split items differently to make numbers look better, or stop collaborating because they are being ranked.

To fix this, stop using velocity as a scoreboard. If multiple teams need to plan together, use shared baselines, historical throughput, or another explicit approach to normalization. Use the data to improve forecasting, not to declare winners.

The Team Estimates Only Complexity

Complexity affects effort, but story points estimate total effort.

A product backlog item can be technically simple but involve a lot of work. Another can be small but uncertain. Another can involve several teams or a risky deployment.

If a team estimates only complexity, it may underestimate large simple items and misread uncertain work.

To fix this, remind the team to consider:

  • Amount of work
  • Risk
  • Uncertainty
  • Complexity

The estimate should reflect the effort needed to get the item done, not just the elegance or difficulty of the code.

The Team Estimates Unclear Items

A number can make an unclear item look more ready than it is.

If the team does not understand the goal, scope, assumptions, or completion expectations, the estimate will be weak. Sometimes the right answer is not a number. It is refinement, story splitting, a spike, or a Product Owner decision.

To fix this, ask whether the team understands what must be true for the item to be considered complete. If not, improve the item before estimating.

Large estimates can be useful for early prioritization. But do not let a large rough estimate substitute for clarity when the item is being considered for near-term work.

The Team Estimates Too Much of the Backlog

Estimating every item far into the future can waste time.

Backlog items change. Some are split. Some are removed. Some are replaced by better ideas. Estimating too far ahead can create the illusion of progress while the team spends time on numbers no one will use.

Estimate when the estimate will help someone act differently.

If an estimate will not influence priority, scope, timing, or another decision, wait.

The Team Estimates Too Little of the Backlog

Some teams go too far in the other direction. They wait until Sprint Planning to estimate.

That can be too late. A Product Owner often needs an estimate before Sprint Planning to make good prioritization decisions. A five-point item may be worth doing soon. A 100-point version of the same idea may cause the Product Owner to split it, reduce scope, or choose a different option.

To fix this, estimate far enough ahead that the Product Owner can use the information. Product backlog refinement is often the right place.

The Team Puts Points on Everything

Some teams assign points to every activity.

That can make velocity look complete, but it can also make the system noisy. Not every task needs story points. Story points are most useful for estimating product backlog items so the Product Owner and team can make planning and prioritization decisions.

Bugs are a special case. If fixing bugs consumes meaningful team capacity and the team wants velocity to reflect that work, estimating bugs may help. If the team uses velocity only to forecast new product backlog functionality, it may choose not to assign points to bugs.

The question is not whether bugs are special. The question is what decision the estimate supports.

How to Reset a Broken Story Point System

When story points have become political or confusing, do not try to fix everything by changing the scale.

Start with purpose:

  1. Name the decisions estimates should support.
  2. Stop converting points to days.
  3. Stop using velocity as a target.
  4. Re-establish a few baseline product backlog items.
  5. Estimate by comparison again.
  6. Discuss disagreement instead of averaging it away.
  7. Use velocity only as a planning input.

A reset works best when leaders, Product Owners, Scrum Masters, and team members agree on how the estimates will be used. If the organization keeps rewarding higher velocity, the team will keep finding ways to increase the number without increasing value.

When the Team Is Reluctant to Estimate

Some teams resist story points because estimates have been used against them.

That reluctance is worth taking seriously. Maybe estimates were treated as commitments. Maybe teams were compared by velocity. Maybe managers used points to pressure teams into more work. Maybe the team was asked to estimate items that were too unclear to estimate responsibly.

Do not dismiss those concerns. Make the estimating process safer:

  • Estimate only when the estimate supports a useful decision.
  • Do not punish teams for estimates that turn out wrong.
  • Do not compare teams by raw velocity.
  • Do not ask teams to estimate items they do not understand.
  • Use estimates to discuss tradeoffs, not to assign blame.

Teams are more willing to estimate when estimates are used as planning inputs rather than weapons.

When to Stop Estimating Temporarily

Sometimes the healthiest move is to pause estimation and fix the conditions around it.

Pause or narrow estimation when:

  • Velocity is being used to rank teams or individuals.
  • Every estimate is treated as a commitment.
  • The backlog is too unclear for meaningful estimates.
  • The team has no shared baseline.
  • Stakeholders demand false precision before the team has enough information.

A temporary pause should not become avoidance. Use the pause to rebuild trust, clarify backlog items, create baselines, and agree on how estimates will be used.

How Leaders Can Help

Leaders can make story points more useful by changing the questions they ask.

Less helpful questions include:

  • "Why did velocity go down?"
  • "How many points can you commit to?"
  • "Why does this team complete fewer points than that team?"
  • "Can you make this a five instead of an eight?"

More helpful questions include:

  • "What decision does this estimate support?"
  • "What uncertainty is driving the estimate?"
  • "What would help the team forecast more honestly?"
  • "What work is not visible in the current estimate?"
  • "What tradeoff should we make if this item is larger than expected?"

Story points improve planning only when the surrounding system rewards honesty.

Should Bugs Get Story Points?

Bugs create confusion because teams use velocity for different purposes.

The better question is not, "Do bugs get points?" The better question is, "What decision are we trying to support with this estimate?"

If fixing bugs consumes meaningful capacity and the team wants velocity to reflect the work it actually does, estimating bugs can be useful. If the team uses velocity only to forecast new product backlog functionality, it may choose not to assign points to bugs.

Either approach can work if the team is consistent and clear.

Do not use story points to reward or punish teams for finding defects. Use them to understand capacity, effort, and planning tradeoffs.

Common Questions

Are Story Points Bad?

No. Story points are useful when they support decisions. They become harmful when organizations misuse them.

Should We Stop Using Story Points If Velocity Is Being Misused?

Maybe temporarily, but the deeper problem is the misuse. Fix the management behavior and team agreements that turned velocity into a target.

How Do We Know If Points Have Become Days?

Listen to the conversation. If people say things like "that is three days, so it is three points," the team has converted points to time.

What Should We Do When Estimates Keep Growing?

Return to baseline items. Compare new estimates with similar past items. Also remove pressure to increase velocity.

Should Bugs Get Story Points?

Sometimes. Estimate bugs when the estimate helps with capacity, prioritization, or forecasting. Do not estimate them just to put points on everything.

Recommended Articles

Related Pages

All Articles on Common Story Point Problems