Nils Buntenbeck retweetledi

Demanding an estimate guarantees the estimate will not be useful to the business and will always drive costs up.
Software engineers all know that estimates are useless. It's literally impossible for them to be accurate when you also need to build the most valuable software, because we learn as we work, and every scope change changes the estimate. Also, many of the things we do cannot be estimated because they involve discovery.
Software engineers also know that managers will treat their estimates as promises. Bad managers demand estimates so they can pass the blame to the programmers when the project fails, which it always does, given a fixed scope and budget. In other words, any project that _can_ be estimated will fail because you'll be building the wrong thing. Giving an estimate puts your head on the chopping block.
Software engineers are not dumb. They will wildly pad the estimate to protect their necks. If they know you will negotiate the estimate, the starting bid will be even higher. Since they can't be seen as lazy, Parkinson's Law will kick in, and they'll find something unnecessary to do to fill the time. That's expensive.
Wildly inaccurate estimates are of no value for planning, either. Estimates make you arrive at the market later.
Given all this, could we please drop the charade and just get the work done?
English


















