The #NoEstimates Movement: Should You Skip Story Points?

The #NoEstimates Movement

The #NoEstimates movement argues that story point estimation is wasteful and that teams can plan effectively by counting items and measuring throughput. Is it right for your team?

The Core Argument

Estimation takes time (often 10-20% of total team effort). If the estimates are not significantly better than simply counting items, the time is wasted.

Key claims:

1. If all stories are similarly sized (after splitting), counting them is as accurate as summing points.
2. Historical throughput data (items/week) predicts the future as well as velocity.
3. Estimation sessions can be replaced with just-in-time splitting and refinement.

When #NoEstimates Works

• Small, consistent stories. If your team reliably splits stories to 1-3 day chunks, they are roughly equal in effort. Counting works.
• Mature Kanban teams. Flow metrics (cycle time, throughput) provide forecasting without estimation.
• Stable teams with historical data. You need at least 3 months of throughput data to forecast without points.

When #NoEstimates Fails

• Highly variable work. If items range from 1 point to 21 points, counting them is misleading.
• New teams. Without historical data, you have nothing to base forecasts on.
• Stakeholder expectations. Some organizations require effort estimates for budgeting and resource allocation.
• Cross-team dependencies. Other teams may need to know relative size to plan their own work.

The Middle Ground

Many teams adopt a pragmatic hybrid:

1. Split aggressively. Make items as uniform as possible.
2. Use T-shirt sizes for large items. Quick, low-overhead sizing.
3. Count items for forecasting. Use throughput metrics.
4. Estimate only when it adds value. Complex, risky, or cross-team items.

Estimation overhead:
  Full planning poker every sprint:  ~4 hours/sprint
  T-shirt sizing + split:            ~1 hour/sprint
  #NoEstimates (just split):         ~30 min/sprint

How to Transition

If you want to try #NoEstimates:

1. Start by tracking both story points and item count for 3 sprints.
2. Compare forecasting accuracy of point-based vs count-based methods.
3. If count-based is equally accurate, gradually drop estimation.
4. Keep splitting discipline -- it is the foundation of the approach.

The right answer depends on your team, your domain, and your stakeholders. There is no universal "best" approach.