Earlier quoted context omitted.
> 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.
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.
How to replace estimations and guesses with a Monte Carlo simulation
151–160 of 162 posts
Re: How to replace estimations and guesses with a Monte Carlo simulation
#152I think it's understandable why programmers dread doing estimates so much. But I believe there are multiple factors contributing to the current overall mess and the guilt should be shared among several areas -- and that includes us. Estimates are often, if not always, mistaken as commitments or deadlines. But we don't do a great job on explaining that estimates are probabilistic by nature, there are risks involved, a…
When I am leading teams, I also ask for a certainty score along with the estimate, then track them together with daily updates. Like all human processes it is not infallible but it allows more reliable planning. I always wish I had a tool that would include this in the estimate process. Hansoft got close but nobody uses it!
Re: How to replace estimations and guesses with a Monte Carlo simulation
#153Re: How to replace estimations and guesses with a Monte Carlo simulation
#154Earlier quoted context omitted.
I gotta tell you that unless you're working with absolute bozos, nobody is looking at estimates and saying "oh duh, I am betting the farm this will complete on that date." Happens all the time, and not just by bozos. Sometimes getting paid is entirely dependent on delivering when you said you would. I used to work at an animation studio and one year we worked on a series of Christmas themed TV spots. When we said we…
That's not an estimate, it's a deadline. Different concepts.
Re: How to replace estimations and guesses with a Monte Carlo simulation
#155Not to hijack the conversation, but I though some people interested in replacing estimations could find this useful. In order to replace estimation, we are trying Basecamp's Shapeup language and techniques [1] In a nutshell the thinking is reversed, instead of asking: - "how long would it take to implement X?" you ask: - "how much appetite (in weeks and people involved) do I have for this feature ?" Then you work wit…
Re: How to replace estimations and guesses with a Monte Carlo simulation
#156Earlier quoted context omitted.
That's not an estimate, it's a deadline. Different concepts.
Surely a deadline is just an estimate you bet the farm on :)
Re: How to replace estimations and guesses with a Monte Carlo simulation
#157Earlier quoted context omitted.
> 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.
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. Anot…
Re: How to replace estimations and guesses with a Monte Carlo simulation
#158I’m a big fan of the Donald Reinertsen approach: measure queue length. Simply track the time to complete each task in the team queue on average, then multiply that by the number of tasks remaining in the queue. Each team will habitually slice things into sizes they feel are appropriate. Rather than investing time to try and fail at accurately estimating each one, simply update your average every time a task is comple…
On a team of 4 or 5 people, where people go sick, take vacations, leave the company, new members join... each of these events has a big impact on those metrics. Which again, becomes a lot of work and effort wasted.
But yes, probably this is a viable option on larger teams.
Re: How to replace estimations and guesses with a Monte Carlo simulation
#159Earlier quoted context omitted.
> I gotta tell you that unless you're working with absolute bozos, nobody is looking at estimates and saying "oh duh, I am betting the farm this will complete on that date." Meanwhile, anybody working anywhere close to the retail space fell laughing off their chair. Thanksgiving won't move no matter how much you insult your co-workers. (This is not limited to retail. Many industries have fixed delivery dates and bet…
There's a difference between "it's done now, before Thanksgiving, let's bet the farm on it" and "it might be ready two days before Thanksgiving, let's bet the farm on that "... Ed: that said, given gp quote about working with bozos, there's always that anecdote from the introduction of (2nd éd) of Peopleware, about the deadline being moved, because the project was on track for meeting the original deadline... (March…
And Black Friday season is large enough (30% of annual retail) that you might well try for a farm-sized bet. Been there. Done that. Had the conversations around risk.
It is both "it must be operational by this day, or huge losses" and "we would rather not ship your effort than ship it between Black Friday and Christmas".
Re: How to replace estimations and guesses with a Monte Carlo simulation
#160Not to hijack the conversation, but I though some people interested in replacing estimations could find this useful. In order to replace estimation, we are trying Basecamp's Shapeup language and techniques [1] In a nutshell the thinking is reversed, instead of asking: - "how long would it take to implement X?" you ask: - "how much appetite (in weeks and people involved) do I have for this feature ?" Then you work wit…