Re:Algorithmically Estimating Developer Time
by DougWebb on Friday July 08, 2011 @01:58PM
(#2743423)
I wrote a blog post a while back (http://webbindustries.com/archives/2010/10/index.html#e2010-...) about Big Design Up Front and why it doesn't work. This touches on what you're describing; accurate estimation is possible when you're in a 'Manufacturing' mode and creating one more of something you've created many times before, but it's not possible when you're in 'R&D' mode creating something new or investigate a previously unknown bug.
The theory behind BDUF is that you can come up with an accurate design, then come up with an accurate estimate for constructing the design, then go build it. It doesn't work because most software development is done in R&D mode, which you can't design or estimate accurately.
Now, how well these methods work depend on the project.
If you're writing a CRUD webapp from scratch and you've got a good framework (RoR, symfony, etc.) you can probably estimate with high precision.
If, on the other hand, you've got some A.I. software that fell off a UFO and your mission is to get it working as part of a larger system, it's hard to estimate.
Maintenance work is hard to estimate for a number of reasons: for one thing, an existing system has a large number of requirements baked into it that you're not aware of. It helps a lot if the last guy left you so some tests but you can't always choose that. ;-)
Even "predictable" projects can become unpredictable if your 'client' changes requirements too much, or if the requirements aren't well specified to begin with. That's one reason I don't do fixed price jobs for low rollers -- I'd rather do anything else, like milk cows on somebody's dairy farm.