Software Estimates
A great post from Pawel Brodzinski on estimation for software development:
OK, but what about majority of cases when we need some kind of real estimate? For example all those fixed price projects where estimates are basically a part of risk management, as the better the estimate is the smaller are chances that the project goes under water. I can’t deny that we need to have something better than wild-ass guess then.
Yes. Assessing the cost and make sure the schedule is right. The main two reasons estimates are needed in fixed price projects. Its’ also part of the planning process that helps identify the skills needed.
In other words, no matter the method, if you are just guessing how much something is going to take, you will likely to end up with way worse results when compared to a method, which uses your track record.
This is also about having estimates from people who are actually doing or have actually done the job. We are not machines and every development team works/is different. Everybody is different and I always found that programmatic ways of estimating work could not be the best tools out there.