nav-try-button

large_rocket-take-off.jpg

medium_rocket-take-off.jpg

small_rocket-take-off.jpg

thumbnail_rocket-take-off.jpg

rocket-take-off.jpg

Curious about the rise of the #NoEstimates approach in agile development? Smart Guess explores the origins of this movement, how it started with a simple experiment back in 2012, a short blog post, and a 60-character tweed! This post will cover how the #NoEstimates idea was born. Discuss why it took off and inspired conversations. Furthermore, we will look into where the discussion stands today, years later.

## Why did the #NoEstimates discussion take off?
Thinking through this question, the discussion took off because (share your feedback if something is missing): 

1. **Polarizing Idea.** The idea of taking on software development without any estimates was and still is, for many, highly controversial. Since we started building software around 1950, estimating has been standard practice. So just hearing *No Estimates* in the context of software development was and still is a surprising and polarizing idea for many 
2. **#NoEstimates hashtag** perfectly captures the idea and grabs the attention
3. **Twitter and participation** in the discussion have been critical in spreading the word
4. **Estimates are tricky.** As with any tool, there are ways to use estimates correctly and incorrectly. In particular, estimates are tricky because the team needs to use them correctly. Also, they need to be presented so that they are interpreted correctly. Many have first-hand experiences where estimates were poorly applied. Therefore many are open to new ways of working 
5. **Humans are inspired by polarizing content.** We humans are more easily *inspired to anger*, see quote below, than by other emotions. 

Let's cover the last point better and put this into context with what kind of stories we humans are more likely to engage with. Recently, we heard about the [Facebook - whistleblower case from CBS - 60 minutes](https://www.cbsnews.com/news/facebook-whistleblower-frances-haugen-misinformation-public-60-minutes-2021-10-03/). In this case, Frances Haugen explained how Facebook's algorithms pick out the content we see: 

> consequences of how Facebook is picking out that content today is it is -- optimizing for content that gets engagement, or reaction. But its own research is showing that content that is hateful, that is divisive, that is polarizing, it's easier to inspire people to anger than it is to other emotions. 

So many things were aligned for the idea to get attention, and it caught fire and grabbed attention!

## Where does the #NoEstimates discussion stand today?
Today the #NoEstimates discussions have taken a different and darker tone almost nine years later. As many who take part in the debate, such as [Ron Jeffries](https://ronjeffries.com/articles/019-01ff/estimation-again/Index.html), [Your Daily Scrum podcast](https://youtu.be/YKYiFK-FJyQ?t=462) and [Peter Kretzman](https://twitter.com/PeterKretzman/status/1450867463931908103?s=20) agree on. To quote what Ron is saying about this, there is a lot of *"unproductive discussion"*, *"unreasoned-name calling,"* and "ad-hominem arguments." In my mind, this kind of discussion is simply a waste of time.

One part of what fuels this fire is #NoEstimates proponents, who have stepped in with a more aggressive black-and-white stance on the topic, claiming that estimates are always bad. Even though Woody openly shares that:

These proponents differ from Woody as they sell books and services, helping teams implement #NoEstimates. It is great teams are getting expert help on Agile practices. However, I question the value and purpose of claiming Estimates are always bad and wonder what they are trying to accomplish with this.

But that is material for another blog post. Until then, cheers!

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

Why did the #NoEstimates idea took off?

Björn Brynjar Jónsson

large_Bjorn-Brynjar-Jonsson.jpg

medium_Bjorn-Brynjar-Jonsson.jpg

small_Bjorn-Brynjar-Jonsson.jpg

thumbnail_Bjorn-Brynjar-Jonsson.jpg

Bjorn-Brynjar-Jonsson.jpg

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

Silent Estimation

Planning Poker

Solutions

Blog

Pricing

Contact Support

Documentation

Security FAQ

Support

No setup, One Click - Planning Poker you run directly from the Jira backlog. "It's the best app ❤️ we've used. **Learn more**

With Bucket Estimation, intuitive drag & drop, you got all your estimation needs  covered  🚀  **Learn more**

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

Why did the #NoEstimates idea took off?

Recent Posts

Share your thoughts

Planning Poker

Bucket Estimation

Share your thoughts: