6 ms·
Unfortunately, this is only one signal among many, and it's not a reliable one. It's like saying a good gambler is one who is lucky at the slots. Sure, but...
by invalidOrTaken 7y ago
Unfortunately, this is only one signal among many, and it's not a reliable one. It's like saying a good gambler is one who is lucky at the slots. Sure, but...
You'd be better off injecting a large amount of uncertainty into your estimates, and planning around that. If that kiboshes a project, it kiboshes it. Better to fire your devs because you have nothing (feasible) to work on, than to fire them three months later because the project was late, because you have to pay them in the second scenario.
- stephencoyner 7y agoCreating a large window to account for some uncertainty is fine. My main point is in working with some less experienced engineers they'll say "This will only take 2 days" and it takes two weeks. This kills teams. I think less experienced people do this because they are excited / eager to please, but it only hurts in the long run.