3 ms·
My PM has a great way for dealing with engineer estimates: increment both the number and the unit. 1 hour becomes 2 days. 4 days becomes 5 weeks. And so forth.
by falcolas 9y ago
My PM has a great way for dealing with engineer estimates: increment both the number and the unit.
1 hour becomes 2 days. 4 days becomes 5 weeks. And so forth.
I'm actually somewhat decent at estimating well defined work, so it actually annoys him when one day is one day; but I appreciate his work when some odd stumbling block (usually political; my estimating skills crash and burn when it involves working with humans) comes up and the time doubles or triples the estimate.
- eps 9y agoIt's a very old PM joke. The original version is "double fhe number, shift to the next time unit."
- falcolas 9y agoThe best jokes have their roots in reality. Of course, when the joke works in reality, is it still a joke?
- eximius 9y agoSome of the best jokes are funny because they're true.
- whamlastxmas 9y agoA one year project is now a two decade project
- hrktb 9y agoSeems about right. A year is an eternity anyway, you shouldn’t start a project with nothing coming out of it before a year, that’s suicide on so many plans.
- user5994461 9y agoA software project that takes a year will costs a fortune (salaries are expensive). It will probably have to be maintained and running for the next decades to give enough returns to be worthwhile. So, 1 year is the time the first interns team will work on it, 10 year is the duration before the project is retired. Looks like both estimates were right.
- dahart 9y agoThe joke is for hours/days/weeks estimates, not months, years or decades. Hopefully nobody is asking an individual contributor for estimates they expect to be in years. My engineering manager at a games company I worked for told me that "three weeks" was the estimate that really meant they had no idea how long it would take, because the task was too hard to estimate. Anything longer than three weeks could, and did in fact, sometimes take six months.
- jwatte 9y agoNo it works for years, too.
- curun1r 9y agoThat sounds right because it's clear that the 1-year estimate lacks understanding and forethought. If you start a project with that large of a swagged estimate, it mostly won't ever be completed. The only way I'd even consider an estimate that large to have any basis in reality is if it was 1 year, 2 months, 6 days and 4 hours. That would mean the estimate is composed of many smaller estimates for tasks that are much closer to being understood. Large projects can always be broken down into smaller, more well-understood tasks. You can't build something large all at once. Large estimates are just an indication of a lack of discipline in planning because they mean that the project hasn't been decomposed into its constituent tasks. Large estimates are lazy and can only be right out of sheer luck. In the team's I manage, I don't let anyone start a story with an estimate of more than two days.
- EpicEng 9y ago>4 days becomes 5 weeks Are you being serious? That only works if the people consuming these estimates don't have a clue and therefore can't call BS. This would get me aughed out of my job.
- RealityVoid 9y agoThis also astounds me. I can't graps the art of these estimates. I suck at estimating deliviery times, and I'm a pretty good engineer. But I either over-estimate or under-estimate, I find it hard to be on point, there are always unexpected side effects. And I'm known as a sort of miracle worker, when they have something they can't solve, they come to me. But I HATE giving estimates. If I were to estimate things as suggested in this thread, it seems to me things would never get done. Ever. It simply boggles my mind people want and will fudge estimates on this scale.
- falcolas 9y agoPretend, for a moment, that you're working on a one week project. You're estimating that week based on the ability to use an open source project which promises to take care of a large portion of the complexity for you. Also pretend you're new enough to not realize the hollowness of that promise. It's only three days in to the project that you realize there's a mismatch between what you need and what the project provides. You start a conversation with the project's lead developer; but they're only able to have half of any given conversation in a day. How hard would it be to spend five days researching the cause and severity of the mismatch while discussing solutions with the remote developer? There's 8 days. You decide to write a patch for the open source project shepherd it through the internal and external approval process, burning up another two weeks of time. 18 days. You finally get back and finish the original project, redoing a fair bit of work to account for the changes your patch introduced. 23 days. You're interrupted throughout this process several times by fires in production that need to be fixed RIGHT NOW. 28 days. Let's make the assumption your PM did their little trick, and slated 2 months for this project. Despite your own estimate being off (through no ill-will by anybody) by about 6x, your work is still completed before it's expected, and the teams depending upon your work are happy as clams. Even if it had finished in the original 5 days, everyone would be thrilled, and you'd get more work to do. From the PM's point of view, it's a win-win situation. From your point of view, the worst you have to endure is a twinge of "don't you trust me?", offset by the relief of not having to answer "why isn't it done yet" every day from day 6 on.
- yread 9y agoI heard multiply by pi instead of increment, so 1 hour becomes 3.14... days