zlacker

>>mattjh+(OP)
I don't get the fight against estimates. An estimate is an estimate. An estimate can be wrong. It likely is wrong, that's fine, it doesn't have to be perfect. There is a confidence interval. You can communicate that.

Very often something like "6-12 months" is a good enough estimate. I've worked in software a long time and I really don't get why many people think it's impossible to give such an estimate. Most of us are developing glorified CRUD apps, it's not rocket science. And even rocket science can be estimated to a usable degree.

Really you have no idea if feature X is going to take 1 day or 1 year?

>>mmcnl+Ee1
I think there are range of situations causing anti-estimate sentiment, each team is different, each tram has different levels or combination of these:

- manager’s refusal to acknowledge any uncertainty

- unclear requirements/expectations/system under change

- changing requirements

- negative consequence (“penalties”) for inaccurate estimate

I’m now also in the environment where I give ranges, but not everybody is.