large_tape-measure-2-small.jpeg

medium_tape-measure-2-small.jpeg

small_tape-measure-2-small.jpeg

thumbnail_tape-measure-2-small.jpeg

tape-measure-2-small.jpeg

Debunking the myth that estimates never work in Agile. Explore why some #NoEstimates proponents make false claims and learn how to avoid this pitfall.

I thought Vasco's answer below was quite positive because he accepts it's valuable to have a tool '..allowing teams to make decisions about options that come up during backlog discussions'. Because he says with a "..simple slicing heuristic.." you can achieve this value. Thereby accepting the value of the premise. To confirm this, I followed up and asked:

### #NoEstimates author in contradiction
By looking at Vasco's tweets above and the repeated tweets with the same message, Vasco completely dismisses the value of estimates. Yet in his book, chapter 5, *'1-2-3: Step by step towards # NoEstimates'*, under the heading *' Move to story points'* he says that: 
> **Story Point-based estimation gives a better understanding of how things like risk, complexity, expected dependencies for each Story**, etc. Given that a large amount of time it takes to deliver one Story is spent waiting, **Story Point estimation is more likely to help you assess the true impact of one Story in your project.**"

So Vasco clearly understands there is value in estimates, yet consistently contradicts this every time he claims estimates:
1. are helpful only for "..blaming, pressuring others, etc.." 
2. do not work "for containing costs or hitting a deadline"

This doesn't make sense, or does it? Let's touch on this question before we close. But let's first debunk Vasco's false statement many have been led to believe that: 'estimates never work.' 

## Debunking the claim that 'estimates never work'
Vasco and others repeating these claims don't realize they are logical fallacies. In the examples above, Vasco makes a [faulty generalization](https://en.wikipedia.org/wiki/Faulty_generalization). Here is the example from Wikipedia and the #NoEstimates fallacy side by side:

```
If one sees only white swans, one may suspect that all swans are white.
If one only sees estimates used with bad intentions, one may suspect all estimates are used with bad intentions. 
```

To debunk the statement' estimates never work,' we only need a single case, one example, where an estimate is used successfully to show statements making this claim are false. Let's extend the story from the #NoEstimates book, and let's introduce Carmen, the main character in the book, to the following case:

 **Case Example: Carmen and her team identify a better solution using estimates**
> Through discussion with users and stakeholders, Carmen identifies a problem the team needs to tackle. During a sprint planning discussion, it becomes clear there are different options available.

> During the initial discussions Carmen had, a solution idea was identified that stakeholders thought made sense to go ahead with. Later during planning, the development team's discussed the problem and the proposed solution, solution A. The team estimated the work might be around 13 story points. They expected it would take a bit more than one sprint to complete. The reason was that there were some known unknowns and unknown unknowns, as always. Given their information, history, and velocity, Carmen and the team knew it would likely take 1-2 sprints to complete.

> During the meeting, the team identified a different approach. Let's call it solution B. Estimating solution B; the team expects it to be around eight-story points yet provide the same value. Given their velocity, the story will likely be completed within one sprint. This is because there were no 'known unknowns' about solution B, so the team is more confident about this estimate. In other words, they expect the estimate for solution B will have less deviation than the estimate for solution A.

> Based on these findings, Carmen and the team agree to implement solution B. In addition, Carmen will validate their thinking and present a quick mockup of the proposed solution to users and stakeholders who participated in the initial discussion. To ensure they didn't miss anything during the team discussion and validate the solution delivers the value they are after.

By making this single case, based on real examples, we can see the claim that "estimates never work" is false. Cases such as these have repeatedly come up during my 20+ year career as a Software Developer, Scrum Master, and Product Owner. I am not the only one, as teams worldwide are using estimates successfully in their work.

This raises the question, why on earth are some of the key #NoEstimates proponents knowingly repeating false claims that 'estimates never work'?

## Why are #NoEstimates proponents knowingly making false claims?
Now, this is an interesting question. In one part, it has to do with spreading the #NoEstimates idea, selling books, and related consultancy services. Another factor has a darker side, as many are trapped into believing the false claims and take up the harmful and aggressive [black and white stance on estimates](https://smartguess.is/blog/black-and-white-noestimates-stance-considered-harmful/) wasting a lot of time in unproductive arguments and causing polarization in our community.

## What's next?
In the next post, we examine another fallacy often used by #NoEstimates proponents to support the same claim. Read more in our deep dive on the [#NoEstimates straw man fallacy.](/blog/no-estimates-straw-man-fallacy/)

**About Smart Guess** 
*We help teams educate stakeholders by providing actionable answers to common misconceptions about estimates. So more teams can use estimates to their advantage, and fewer are held accountable for delivering on impossible deadlines.*

Debunking the Claim That Estimates Never Work in Agile

Flow Metrics shows leadership what you actually do: identify bottlenecks, improve predictability, and protect delivery. Turn invisible work into measurable results.
> "Finally, data that proves what I've been saying all along."

*Free trial available — no credit card needed 💡*  

Stop Defending Your Value. Start Proving It.

Turn Jira data into insights you can act on. Spot bottlenecks, track cycle time, and forecast delivery with confidence — all inside Jira.  

> “Smart Guess gave us instant visibility into our process. It’s the first time we’ve felt in control of delivery.”  

*Now available with a free trial — no budget approval needed 🚀*

See Your Team’s Flow Clearly.

Make cycle time, throughput, and WIP visible without spreadsheets or consultants. Smart Guess Flow Analytics shows where work really gets stuck — so you can act early.  

> “We cut weeks off our cycle time after seeing where work was really getting stuck.”  

*Free 30-day trial — see your flow in action 🔍*  

Uncover Bottlenecks Before They Hurt Delivery

Try One-Click Planning Poker you run from the Jira Backlog and you will never look back.

"After trying many tools in Jira, we landed on Smart Guess. It's the best app ❤️ we've ever used!"

Now available for free — no budget approval needed! 🚀


Transform your Planning Poker

Run one-click Planning Poker directly from the Jira Backlog and never look back. Estimate faster, collaborate better, and keep everyone aligned.  

> “After trying many tools in Jira, we landed on Smart Guess. It's the best app ❤️ we've ever used!”  

*Now available for free — no budget approval needed 🚀*  

Transform Your Planning Poker

Every missed deadline has a cause. Every blown estimate has a reason. 

But without connecting the dots across sprints, you're experiencing the same problems over and over.

We'd been underestimating integrations for 18 months. It was obvious once we could finally see it.

How Many Sprints Before You Spot the Pattern?

When stakeholders push for aggressive timelines, you feel the risk. 

But _"I think this is too ambitious"_ doesn't win arguments. Data does.

_"For the first time, I could show leadership exactly why their deadline was unrealistic—with numbers, not opinions."_

Turn intuition into evidence —free trial available 📊

You Know It's a Bad Estimate. But Can You Prove It?

Two 5-point stories. One takes 2 days, the other takes 2 weeks. Your team estimated them the same—but something made them wildly different. 

Without visibility into what, you'll keep guessing.

_"We discovered our 'quick fixes' were actually taking longer than new features."_

Stop guessing, start knowing—free 30-day trial 💡

Same Story Points. Different Outcomes. Why?

Dozens of estimation sessions per team. Hundreds of data points. All of it disappears the moment the meeting ends. What if that data could actually improve your predictions?

_"Years of Planning Poker sessions—finally doing something useful."_

Turn estimation history into foresight—free trial 🎯

You Run Planning Poker Every Sprint. What Happens to That Data?

Stakeholders add urgent work mid-sprint. You know it hurts delivery—but without concrete data, you can't quantify the damage or push back effectively.

_"Now I can show exactly how much longer planned work takes when we interrupt it with urgent requests. The conversations have changed completely."_

Quantify the true cost of interruptions—free trial  🎯

How Much Did That 'Quick Request' Actually Cost?

Story points tell you relative size. They don't tell you when something will ship. The gap between estimation and prediction is where promises break.

_"We went from 'probably next month' to '85% confidence by March 15th.' Leadership finally trusts our timelines."_

From estimates to predictions—start free 📅

Your Team Estimates. But Can You Actually Predict?

Issues sit in "In Review" for days. Blockers hide in "Waiting for Info" for weeks. 

Without visibility into time spent per status, you're managing blind. 

_"We discovered issues were spending 60% of their lifecycle waiting—not being worked on."_

See the truth about your workflow—free trial 🔍

Where Does Your Team's Time Actually Go?

Every retrospective, the same question: _"Why didn't we finish?"_ Without time-in-status data, you're debating opinions instead of analyzing facts.

_"Turns out our bottleneck wasn't development—it was code review. We never would have known without the data."_

Find your real bottlenecks—start free 📊

Stop Guessing Why Sprints Slip

Every process has blind spots. Time In Status reveals the delays your workflow has normalized—the ones nobody questions anymore.

_"At sprint end, our 'quick QA pass' was averaging 3+ days. Nobody realized until we measured it."_

Uncover what you've been missing—free trial 💡

It's Been In QA For How Long?

Every status change in Jira is a data point. But without analysis, it's just noise. 

_"We identified that issues with external dependencies spent 3x longer in 'Blocked' than internal work.\"_

Make your data work for you—free 30-day trial 🎯

Turn Status History Into Process Insights

using contentList for cta messages


https://marketplace.atlassian.com/apps/1225496/

Paid app

nav-try-button

SG-full-color-black.svg

SG-full-color-blue.svg

SG-logo-black-07.svg

SG-logo-color-05-MarketPlace.svg

SG-logo-white-06.svg

SG-full-color-white.svg

See what's unpredictable. Understand why. Fix it. AI-guided insights help you spot bottlenecks, reduce variation, and make estimates that actually hold up.

Estimate smarter together. Real-time collaboration meets historical data. AI-powered insights help your team calibrate estimates based on what actually happened, not just gut feeling.

Why the ‘Estimates Never Work’ Claim Fails to Hold Up

#NoEstimates

Topics covered in the series

Popular posts

Explore More Ways to Improve Delivery

Flow Intelligence

Predictive Planning Poker