3 ms·
A common mistake is thinking that you're not estimating. You are, you just don't have a conscious, measurable or repeatable method anymore. You're defaulting to
by jacques_chester 13y ago
A common mistake is thinking that you're not estimating. You are, you just don't have a conscious, measurable or repeatable method anymore. You're defaulting to ad hoc "expert judgement".
The second common mistake is doing The Estimate. A single estimate at the start is always going to be wildly wrong. But that's when it's most needed. That tradeoff continues throughout a project, from which it follows that there should be many estimates.
- wpietri 13y agoYes, I mean formal estimation, and the waste I'm talking about is the difference between casual and formal estimation. And the risk, too. Everybody gets that a handwave is a handwave, but a great deal of shops think that once somebody puts a number down, it turns into a fact. I totally agree that if you do need serious estimates, doing them on a rolling basis is the only way to go. I'm personally a fan of the Extreme Programming approach to that. The beginning of the project is when you know the least, so any estimate then is guaranteed to be the worst possible one.