@johncutlefish I’ve managed software development with no estimates. I don’t see how “why estimates” makes sense in that context. #NoEstimates clearly states that I’ve worked without estimates. Like saying “Gluten free” vs “Why gluten?”. @johncutlefish Or saying “Coke Zero” vs “Why Coke without sugar”. Coke Zero means this drink has #NoSugar. In this context it would be a bit nonsensical to say to say “this drink has Why sugar”. It can have no sugar, or less sugar, or the normal amount, or even extra sugar.

Thanks for writing and sharing your thoughts.

https://twitter.com/hamletarable/status/1012987260365672448

“Ranged estimates” are an integral part of many processes that use estimates, and have been in use for many decades. However, IMO they’re essentially the same thing as an estimate. 1/

Okay. I didn’t mean to say everyone wants a one size fits all solution - but please understand that many seem to think that it’s that simple.

1/ I’m not proposing that we need an alternative to blink estimation.

If we have a need to make the sort of decisions that blink estimation can try to inform - then there are plenty of techniquesxpeople are using. If they work well, then simply use them.

2/