3 ms·
If you __really__ don't get to set the deadline, is it still reasonable to held accountable for that miss? Even if you give worst case and best case the only on
by chiefalchemist 8y ago
If you __really__ don't get to set the deadline, is it still reasonable to held accountable for that miss? Even if you give worst case and best case the only one anyone else focuses on it best case.
Personally, I prefer the 80/20 rule. That is most of the work will go fair quickly, or at least uneventful. It's the last bit that's always the killer. The devil is in the details, as they say.
When asked for an estimate we quickly identify the 80. The key is to pause and not write off the remaining 20.
p.s. Early in my career I read somewhere (I wish I couple remember where) something along the lines of:
Alomst everything takes twice as long and costs twice as much as your original estimate.
If I had $20 for every time I found that to he true, I wouldn't have time for HN. I'd be too busy counting my money.
- pythonaut_16 8y agoI also like the 90/90 rule: The first 90% of the work takes 90% of the time. The remaining 10% of the work takes the other 90% of the time. https://en.wikipedia.org/wiki/Ninety-ninety_rule https://en.wikipedia.org/wiki/Ninety-ninety_rule
- chiefalchemist 8y agoLet's no forget the new feature requests after the first 90, once they see it. And, of course, don't allow the deadline to be adjusted. Fast. Cheap. Right. Pick two :)
- s73v3r_ 8y ago"If you __really__ don't get to set the deadline, is it still reasonable to held accountable for that miss?" Not at all, but unreasonableness has never stopped management before.