#NoEstimates (Allen Holub)

Channel:Allen Holub · Length:37:45 · Published:2015-07-06 · Views:259243

Watch on YouTube

Summary

Allen Holub's keynote arguing that estimation is harmful, particularly in Agile, and presenting planning approaches based on data and flow instead. It covers the distinction between estimation and data-driven prediction.

Why HN recommends it

Recommended in estimation and sprint debates as a well-reasoned account of where waste is and isn't in agile.

If you want a well-reasoned discussion of where the waste is and isn't, I highly recommend Allen Holub's talk #NoEstimates — HN, 2022

Software practice, open source & careers · Management, leadership & organizations

Subtitles (excerpt)

good morning everyone um my topic today is no estimates and but I what I mean by that is what that hashtag actually says which is to say we need to just stop doing all estimation now is that estimation has no value at all and I am hoping over the course of the next 45 minutes or so I can convince you that that statement is true the main problem with estimates is that estimates are always based on guesswork you're always guessing you can make a claim that estimates are based on observing past Behavior but the fact is is that what you're implementing is something that hasn't been implemented before so any kind of measurement that you've made of something that happened in the past is not going to impact what you're doing now which is to say you're always guessing now the problem with those guesses is that they're also always wrong which is something that we all know but for some reason we behave as if we didn't know that we imagine that the estimates that we come up with have some kind of validity to them even though we know deep down inside that they don't everybody that I every programmer that I know at one point or another has complained about how bosses take their estimates as if they're bolted in concrete and it's because we know that the estimates are bogus but

On Hacker News

One could write a solid critique of sprints and how they help or don't, and where time is wasted, but this article is overzealous and comes off as motivated more by anger than reasoning. If you want a well-reasoned discussion of where the waste is and isn't, I highly recommend Allen Holub's talk #NoEstimates [0]. [0] [VIDEO] — coryfklein, 2022-10
There's an interesting video by Allen Holub that I've seen on the somewhat related topic of ridding software development of estimates (#NoEstimates)[1]. He argues that they're responsible for deadlines that are impossible to meet due to them being based completely on a guess. He then goes on to talk about how we can still get predictive power without giving estimates. I found it extremely interes… — Vinalin, 2019-04
[VIDEO] #NoEstimates Yes, be agile. Yes, measure all the things. But estimation sets everyone up for disappointment. — hal-eisen, 2025-12
Planning doesn't mean estimation though; we all know it's just guesswork, and basing business decisions on guesswork is madness. On top of that it's a lot of wasted time and effort. Milestones and projections is a much more constructive approach, simply tracking the number of tasks in your backlog over time will give you an increasingly correct projection of when the project will be finished. [VI… — codr7, 2023-11
Apparently if you do zero estimating (or just count the amount of stories), it makes ZERO difference when calculating your cumulative-flow diagram. [VIDEO] Money segment is at the 26m15s mark. The wasted effort of trying to estimate stories provides zero business value in this context. — azemetre, 2022-07

Related videos