4 ms·

> Estimates are often, if not always, mistaken as commitments or deadlines This. This is the problem with "estimates." My solution - and this will sound bad -

> Estimates are often, if not always, mistaken as commitments or deadlines This. This is the problem with "estimates." My solution - and this will sound bad - is to over-estimate.

mateo411 5y ago
Yes, this is everyone's solution, all the way up the organizational hierarchy. Software Engineer, it will take me 2 weeks. Engineering Manager it will take us 4 weeks. Product Manager it will take them 8 weeks. VP it will be done by the end of next quarter.
- _y5hn 5y ago
  And with all the red tape and shifting priorities, they all got it wrong unless scoping down.
myth2018 5y ago
I don't judge, and I recur to this solution as well, more often than I'd like to. But it doesn't only sounds bad.. it is bad indeed, for a number of reasons. For instance, work usually expands to spend all the time available. Then, if you estimate a one-month task as four months, you will likely not win three months to spend on other tasks. You'll probably spend the whole four months on a one-month task instead. Another issue: if you are competing for a project, over-estimates will translate in higher than necessary costs, and you may end up overpricing a project and missing the opportunity. However, as I said, I don't judge and I also recur to that more often than not. On many Organizations, there aren't many other ways to deal with the matter. And that's why I say that the entire Organization looses: managers will have a good night of sleep after putting all the burden over your shoulders, but the losses are affecting every single stakeholder. It's about time for them to start behaving a bit more responsibly.
- game_the0ry 5y ago
  Fair points, but I do not triple my estimations. Its more like added buffer for unforeseen risk. And I am careful to balance my team's well-being with the demands of business.

4 ms·

> Estimates are often, if not always, mistaken as commitments or deadlines This. This is the problem with "estimates." My solution - and this will sound bad -

by game_the0ry 5y ago

> Estimates are often, if not always, mistaken as commitments or deadlines This. This is the problem with "estimates." My solution - and this will sound bad - is to over-estimate.

mateo411 5y ago
Yes, this is everyone's solution, all the way up the organizational hierarchy. Software Engineer, it will take me 2 weeks. Engineering Manager it will take us 4 weeks. Product Manager it will take them 8 weeks. VP it will be done by the end of next quarter.
- _y5hn 5y ago
  And with all the red tape and shifting priorities, they all got it wrong unless scoping down.
myth2018 5y ago
I don't judge, and I recur to this solution as well, more often than I'd like to. But it doesn't only sounds bad.. it is bad indeed, for a number of reasons. For instance, work usually expands to spend all the time available. Then, if you estimate a one-month task as four months, you will likely not win three months to spend on other tasks. You'll probably spend the whole four months on a one-month task instead. Another issue: if you are competing for a project, over-estimates will translate in higher than necessary costs, and you may end up overpricing a project and missing the opportunity. However, as I said, I don't judge and I also recur to that more often than not. On many Organizations, there aren't many other ways to deal with the matter. And that's why I say that the entire Organization looses: managers will have a good night of sleep after putting all the burden over your shoulders, but the losses are affecting every single stakeholder. It's about time for them to start behaving a bit more responsibly.
- game_the0ry 5y ago
  Fair points, but I do not triple my estimations. Its more like added buffer for unforeseen risk. And I am careful to balance my team's well-being with the demands of business.