4 ms·
I'm intuitively on team #noestimates but trying to have an open mind/not dig in my heels. I feel like no one does a convincing job at communicating why estimat
by alecbenzer 7y ago
I'm intuitively on team #noestimates but trying to have an open mind/not dig in my heels.
I feel like no one does a convincing job at communicating why estimates matter (and how much value you get out of how precise of an estimate).
Fundamentally, an estimate (or any piece of information) is really only of value if you're going to do different things based on learning it. E.g., given an estimate, you might:
* Prioritize one project over another based on ROI.
* Know when to communicate that something might be available to users (though that's still not intrinsically valuable, you have to have some kind of marketing/sales-cycle based reason or something that it matters).
* Know when to begin supply-line stuff so that a factory is ready to build a thing as soon as possible (but no sooner, since then maybe you're holding up parts of the pipeline from doing other things? maybe?)
I feel like so often people try to underscore the importance of estimates but don't say anything remotely close to the above. A lot of times it's just "this is important/urgent". Ok, so? If it's urgent then that's even more reason to start actual work instead of spending time planning, if you can't point to a concrete thing you'll do differently having known the plan.
Even when people do talk about the actual reasons for wanting an estimate, it's always totally in the abstract. The precision of an estimate is always on a "delivery day" level, even if that level of precision is totally unnecessary for what this particular estimate was used for.
I think the real reason for this amount and kind of emphasis on estimating really has to do with:
1. Deadlines make people work harder/faster.
2. It gives people sticks with which to measure people/teams.
I think #2 is mostly straight-horseshit. #1 is maybe somewhat true, but I think it's not nearly as good as other ways of getting people motivated to work harder which have fewer negative externalities (e.g., more autonomy, instilling more of a sense of ownership).
- anon9001 7y agoWhen a team is functioning well, deadlines don't matter because of course everyone wants to get the job done, to impress their teammates and feel like they're contributing. When a team is not functioning well, all the estimation in the world won't fix it. It'll probably just make it worse. And if management decides to use estimates as a measuring stick, engineers are right to dig in, over-estimate, and push back on management in the exact same way they're being pushed by management.
- yibg 7y agoOne reason for rough estimates is for making investment decisions. If we have 10 things to do but can’t do them all how do we choose which to do? The what the thing does points to the return piece but we’d need the investment piece too to evaluate which ones are better value.
- alecbenzer 7y agoFor sure, that's what I meant by the ROI bullet. I just often feel like people want estimates that go beyond the level of precision/accuracy you'd need to make a relative ROI call. And just in general don't do a good job motivating _why_ they want the estimate.