How #NoEstimate proponents use the straw man fallacy

large_new-straw-man.jpg

medium_new-straw-man.jpg

small_new-straw-man.jpg

thumbnail_new-straw-man.jpg

new-straw-man.jpg

Explore how the straw man fallacy skews the #NoEstimates debate in Agile development. Gain insights on how to navigate this discussion with your team.


So instead of refuting *'best practices'* for estimating, key #NoEstimates proponents using this tactic are only up to refuting the *'worst practices'*. Why, might you ask? Because that's an argument that can easily be won. In the example, we see a fictional case of how not to think about estimates. However, the real subject of the argument - how you would use estimates - was not discussed at all. So what we see here is, quoting Wikipedia's definition again:

> having the impression of refuting an argument, whereas the real subject of the argument was not addressed or refuted, but instead replaced with a false one.



## The Straw Man Fallacy at the Core of the #NoEstimates Book
The same fallacy is the backbone of the #NoEstimates book. Even though the book was released in 2016, it is like the story happened in 1996. Why? Because none of the Agile best practices from 1996 - 2016 are part of the 'story case' in the beginning. So the method the book refutes is the method Winston Royce talked about back in 1970 and was later called Waterfall. Furthermore, Agile methods are used to get the project back on track. More on this in the post [Methods applied in the #NoEstimates book](https://smartguess.is/blog/methods-in-noestimates-book/).

This is not the first time the #NoEstimates proponents are using the Straw man fallacy, as can be seen by searching for ["#NoEstimates strawman" on Twitter](https://twitter.com/search?q=%23NoEstimates%20strawman&src=typed_query&f=top). This raises the question of why some key #NoEstimates proponents knowingly repeat false claims when they should know better?

### Why #NoEstimates proponents are knowingly making false claims?
This is an interesting question. On one hand, some promote #NoEstimates to sell books, consultancy services, and spread the idea. On the other hand, a darker issue emerges—many genuinely believe these false claims, adopting a rigid, black-and-white stance on estimates. This leads to wasted time in unproductive debates and fuels polarization within the Agile community.

### What's next?
In the next post, I take a closer look at [The Methods Behind #NoEstimates: What the Book Reveals (and Omits)](/blog/noestimates-book-revealed/)

**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.*

How #NoEstimates Uses the Straw Man Fallacy in Agile

Even small improvements in flow save hundreds of hours. Keep your team productive, predictable, and happier with Flow Analytics built right into Jira.  

> “Our retros are now about improvements, not firefighting. Smart Guess changed everything.”  

*Free trial available — no credit card needed 💡*  

Deliver Faster. Stress Less.

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

using contentList for cta messages


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

Free 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

Forever Free. No setup. One Click—Planning Poker you run directly from the Jira backlog. Including
- **Fully featured Planning-** & [Async -Poker](/solutions/async-planning-poker/)
- **Fully configurable** [Card decks](/blog/configurable-card-decks/)
- **Role-based controls**, [Team lead, Observer, etc.](/blog/smartguess-role-based-controls-observing-leading-sharing/)

Perfect for two teams - up to 31 story estimates/week.

Everything in Free included, plus:
- **Unlimited Estimates:** No limits, no boundaries.
- **Silent Estimation:** Estimate large backlogs fast.
- **Atlassian Fortified:** Enhanced security and reliability.
- **Free Demo and Trial:** Experience the Pro Plan before committing.


Smart Guess can be used from within the Jira Backlog

large_PlanningPoker-from-Backlog-E.png

medium_PlanningPoker-from-Backlog-E.png

small_PlanningPoker-from-Backlog-E.png

thumbnail_PlanningPoker-from-Backlog-E.png

PlanningPoker-from-Backlog-E.png

Silent Estimation by Smart Guess allows teams to estimate large number of stories faster

The Straw Man Fallacy in #NoEstimates: How It Misrepresents Agile Estimation

#NoEstimates

Topics covered in the series

Popular posts

Share your thoughts

Smart Guess Free

Smart Guess Pro