Tell HN: My rule of thumb for initial estimation
I think it was Fred Brooks Jr in "The Mythical Man Month" who said that when planning a project he spent 1/3 of the time on design, 1/6 of the time coding, 1/4 of the time on component testing, and 1/4 of the time on system integration and testing.
I've found these estimates to be remarkably accurate and use them all the time. If I think something will take a day of coding, it usually takes a week of work to get it properly done. That's not one day from midday Tuesday to midday Wednesday because I turn it into 3 mini-projects and run around the design/write/test/integrate cycle as fast as possible, but it's a surprisingly good predictor.
I now use it when estimating other people's work. If they say it will take a day, or a week, I multiply by 6. If they say it will take a month, it'll never be done.
Unless they're using the same rule ...
(
20 comments
| 48 points
| on HN
)
A large part of estimating errors comes from forgetting an area that requires work (eg: in code, deployment, documentation, staging/feedback/iterating...).
- If I think I understand everything it involves, then I take my estimate for all the bits, add them up and multiply by 4.
- If I think I understand everything it involves, have done something similar before, and gone through my list of things to do a couple of times looking for stuff I've forgotten, I can multiply it by 2 instead. If I'm unsure how long something will take I am never allowed to round down.
- If I find myself sizing something with the word 'just' in the sentence, I'm missing something big. (e.g. Then it's just a matter of recreating the error condition and making sure my error gets triggered correctly.)
- If I'm not almost finished (i.e. functionality working with some hacks, unit test passes) by halfway through the time then I'm going to miss my deadline.
- I am still mystified as to where that other half of the time goes (I have a proper 90% rule going on), but some of it is getting my code in a shape where I'm happy about checking it in - dealing with comments so they mean things to people other than me, removing ugly bits of code, checking with co-workers in places where I wasn't sure I'd made the right decision. My maximum speed on this is about 500 lines a day. Some more time is then spent getting things back working again, because I'll have broken things in the process. And I need at least a day to get a sandbox build behaving properly, and willing to run on my hardware.
edit: formatting
- http://www.mountaingoatsoftware.com/books/1-agile-estimating... (with free chapters; also read the various presentations on the site)
- http://www.amazon.com/Software-Estimation-Demystifying-Pract...
One key point is to really understand what is risky in terms of estimating (either technically or politically or because it's too vague).
At some point, you can really become accurate as long as the scope is well understood.
In my case, the Fred Brooks technique does not apply: my last customer iteration was 70% infrastructure, 20% code, 10% pm. The one before was 70% code, 10% infrastructure, 10% documentation, 10% pm.
It's full of great light and heavyweight techniques I use all the time in my day to day running a fixed fee software development company (which basically thrives or falls on the quality of our estimation and the risk pricing to go with it).
There are many techniques for estimating how long software development tasks will take primarily because they all suck. Estimating takes time, and is almost always wrong. Some people even advocate figuring out how off your estimates are, to improve your future estimates, so you can be a better estimator. What?
I think it's best to stop estimating and start shipping.
In short, sometimes estimation matters. Knowing when it does and doesn't matter is a different question and a different skill. Perhaps for you it never matters, but before you diss someone as heavily as you just did, I suggest you consider that some people have different circumstances than yours.
Once you add development managers, project managers (who are often re-estimating for you, adding or reducing a number to align with some other expectation) and a product owner who's only hearing numbers rather than the details, it's a very lossy conversation.
How many estimates have you given where you wish you could have said "but if we just do it like this, it'll only take x% of the time", and how well was that communicated to your client?
I just think software estimating as a way of holding a conversation about a product under development is unproductive at best, and often leads to an inferior product .
Your final line was:
My point is that when I need a broad plan of what to implement, how much scope to include, when something will be ready by, and how many people will be required, I need to estimate. Sometimes I need to do that before I get down to the nitty-gritty of the real design, real implementation and real details, so I need some rule of thumb to let me give broad ROM estimates.One of our major customers recently asked for a feature and my sales colleague asked how long it would take. We didn't really know what the customer thought they wanted, so I went into a huddle with my lead programmer and together we sketched a reasonable feature that seemed to match the requirement, and estimated about 4 days of actual coding. I went back and replied that it would be 5 weeks of work on this feature (4 x 6 days) and that, given other commitments, that would be about 3 months elapsed time (one programmer working 1/2 time). So that's 5 weeks NRE on this feature, 3 months to delivery.
The feature was priced accordingly, and when the customer upped the priority we put a programmer on it full time. It was delivered to site and signed off 6 weeeks later.
Sometimes you need to estimate.
So, what was your point?
ADDED IN EDIT: I am, by the way, quite serious about that question. For me, in my circumstances, I really, really need to estimate in broad outline and get it roughly right. I'd like to see a clear exposition of why you think what I do is wrong. Could you perhaps write a more considered piece on your blog and link to it?
When you say "a day of coding," what fraction of a normal workday are you able to spend actually writing code?