Often referred to as the "black art" because of its complexity and uncertainty, software estimation is not as hard or mysterious as people think. However, the art of how to create effective cost and schedule estimates has not been very well publicized. While the average software organization can struggle with project costs that run double their original estimates, some of the more sophisticated organizations achieve results with estimation errors as low as 5-10%. These best-in-class organizations use scientific techniques that are not cost-effective, however, making them of limited use to most software development organizations. To address these issues, Software Estimation focuses on the art of software estimation and provides a proven set of procedures and heuristics that software developers, technical leads, and project managers can apply to their projects. Instead of arcane treatises and rigid modeling techniques, award-winning author Steve McConnell gives practical guidance to help organizations achieve basic estimation proficiency and lay the groundwork to continue improving project cost estimates. This book is organized from simple tips to more advanced ideas; it does not avoid the more hairy mathematical estimation approaches, but the non-mathematical reader will find plenty of useful guidelines without getting bogged down in complex formulas.

Amazon.com® Reader Reviews (Ranked by Helpfulness)

Average Amazon.com® Rating:  Based on 38 Ratings

Title is a little misleading - 2009-11-10
Reviewer Rating:
This book is full of statistical information. If you are already a software estimator, then this book will probably help you. However, the subtitle, "Demystifying the Black Art" seems, to me, to mean that the book will help you learn to do a software estimate. Not learn how to do it better, but learn how to do it, period. That is not what this book is about. It is about doing it better. If you already know the basics of function point or line of code estimation, then this book will probably help you make *better* estimates. However, if you want to learn the "black art of estimation", then this book will not demystify anything.

I think overall it is a good book, which is why I gave it three stars. However, it is very inappropriately titled. If you already know the basics of software estimation, then there is probably not any mystery for you. This book would have been better subtitled, "Enhancing the Black Art", or "Getting your black belt in Software Estimation".

I suppose that once I learn how to estimate software this book will be more beneficial.

Very practical and useful, I DO recommend it - 2009-04-09
Reviewer Rating:
As the title goes, estimation is a kind of "black art".

I had estimated before but I wanted to gain knowledge on other classical or newer techniques, so I bought this book along "Agile Estimating and Planning (Cohn)".

In this case, I DO recommend because it excellently well structured and the content has been wisely chosen and presented, showing techniques ranging from agile ones for small projects to more formal and heavy ones for bigger and more complex projects.

It keeps on the level of detail on techniques which helps you to understand them and chose the right one for your context and it does not get lost on the detail or academical discussions.

One point very useful is the "tip" list, which is a one sencence summary of most sections. Reading them at the end is a very practical way to remember the content.

Alex Ballarin
IT Consultant
Cynertia Consulting, Barcelona, Spain

required reading for everyone in the software industry - 2009-07-04
Reviewer Rating:
"Software Estimation" by Steve McConnell provides a very broad overview of many ways to reduce the software estimation errors for your development cycle. Like all of Mr McConnell's books, he provides crystal clear writing with tons of techniques that are ready for application in the real world.

One of the many great things about "software Estimation" is the sheer number of methods he gives. From Lines of code, to function points, to similar projects, to industry estimates (broken down by sub category so that database is different from embedded devices), to t shirt sizing, to maintaining development history: he makes it clear that you have a lot of different options available to you. He takes great pains to emphasize that one size does not fit all. Additionally he gives rationales for when the estimate techniques work in a project's lifecycle.

With all the methods described, another point driven home is that software is something of an art and that you can reduce the amount of uncertainty but you can never fully remove it. None of the methods that improve estimation are silver bullets. I love that he draws the line in the sand here. Its very true and in fact he goes a step further, pointing out that on successful projects the "cone of uncertainty" converges as the project matures. The converse is also true. Wise words indeed.

The final chapter feels more like a tack on, however the message contained therein is something that needs to be stated again and again: marketing/management is not the enemy. It is important to remember that everyone has the same goals and that the battle really should be a collaboration. However good this chapter was, it still felt out of place.

There are a few niggling issues that I had. The biggest gripe is that he talks a lot about estimation software packages. In fact, he makes assumptions that the reader has knowledge of these packages. Working in start-ups, I've never even heard of these packages until this book. Its a small gripe, but it did detract. Another issue would be some of the examples on applying the various techniques towards the end of the book were far too glossy and far to dry. I think there was some good information there but you, as the reader, will need to make a few assumptions. Which, to me, is always a dangerous thing. Not as bad as fighting a land war in Asia, but still dangerous.

Overall though, as a software engineer/manager I found this book to be invaluable. The techniques are usable right away and really helped me convey the uncertainty I had in ways that I wasn't able to in the past. I think this should be required reading for anyone who works in the software industry.

A true bible about software estimation - 2009-01-17
Reviewer Rating:
No matter if you are an absolute newbie or an expert: if you have any interest about software estimation this book is your new 'must have'.

The author writes in a rigurous but clear language. It does not only introduce you to neccesary terms and concepts, it also covers a lot of estimation methods, comparisons between them and explanations in order to help the reader in the hard task of choosing and deploying a method for your current and future projects.

I have found it quite dense in some chapters... but after all its absolutely the best book about around about software estimation.

Science of software estimation - 2008-09-20
Reviewer Rating:
Steve McConnell explains how software estimation is more a science than an art. Information in this books can applied to agile development as well to the classical approach. So if You struggle (I'm sure You do) with estimation, this is excellent book for You, it doesn't matter whether You are a developer or a manager.

Browse Similar Topics

Top Level Categories:
Software Engineering

Sub-Categories:
Software Engineering > Requirements and Specifications