Estimating the amount of effort needed to create software can be a difficult problem. It depends on a clear understanding of what the software should do, the objectives of the users and the skill of the programmers writing and testing the code. When outsourcing it is tempting to just “throw it over the wall (or ocean)” and let estimation be the problem of the offshore vendor.

But how can judge the quality of their ability to estimate? Even if the write your software for a fixed price bid can you tolerate a huge delay in its completion?

Now Steve McConnell has a new book out called Software Estimation: Demystifying the Black Art that I am presently reading. It is a terrific overview of various methods of estimating the effort needed to write software.

I recommend to clients that they become familiar with these techniques. And if you do throw your project over the ocean at least ask what technique was used to come up with the estimate.

To learn more about the book, check out the transcript of a chat with McConnell printed in the CIO magazine blog.

Bookmark to: