Why it's Impossible to Estimate Software Development Time
blog.hut8labs.com
blog.hut8labs.com
Waving you hands while telling a story IS NOT A PLAN!
People can't even seem to do basic wire frames. It's ridiculous. How on earth are you going to be able to make an estimate on something for which there isn't even a basic plan? And I'm not even talking about a spec here, just even a higher level plan that describes the project from a user point of view, proposed functionality, features, expectations, budget, etc.
I get it, making a plan is difficult and boring work, but you know what? If you can't make a freaking plan you certainly won't be able to build a product. The plan is there to gain insight in the problems you're going to run into. Let's solve all of the shit we can solve before we start writing code so that when we do run into issues, they are genuine issues.
Between psychological (biases) and neurological issues (like 5 +/- 2) and mathematical limits, estimation is pretty hopeless.
AKA you can't estimate pieces, but you can still say this will be done in 3 months, and then you manage scope etc. so it's done in 3 months.
Or: you can't estimate how long this will take, but you can set a "how long" given flexibility in the "this".