| | |  | Investigations | Home » » Software Estimation: Demystifying the Black Art (Best Practices (Microsoft)) | | | | | | | Description: | | 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. | | | Product Details: | | | Author:
| Steve McConnell | | Paperback:
| 308 pages | | Publisher:
| Microsoft Press | | Publication Date:
| March 01, 2006 | | Language:
| English | | ISBN:
| 0735605351 | | Package Length:
| 8.82 inches | | Package Width:
| 7.32 inches | | Package Height:
| 1.02 inches | | Package Weight:
| 1.59 pounds | | Average Customer Rating:
|  based on 40 reviews |
| | | | Customer Reviews: | |
Average Customer Review:
Write an online review and share your thoughts with other customers.
 Really demystifying bookAug 23, 2010
I bought the book more as a curiosity because I am very skeptical towards software estimation or anything that claims to be an "engineering" or "formal" approach on software management, because no matter what technique is used on the management side (from PMBOOK to the witchcrafted Agile), in the end someone come to us (developers) and says: "We need that for X" where X is a ridiculous and unrealistic schedule.
But, the book actually surprised me with good techniques and insights that I could transfer to me day-to-day mine-field tasks, specially when right in the beginning it states very clear the differences between estimatin and commitment.
Well, if someone will take my estimations more seriously from now on it is not my problem, but at least it helped to have them created based more on facts (and countable things) than just out of nowhere.
Hooray for the author!
If you estimate software cost and effort YOU MUST READ THISApr 28, 2010
If you have been or will start estimating software, then you must read this book. You will be introduced to many different estimation techniques, albiet some at a high level.
However, if you are serious about truely developing software estimation as a professional skill the book is loaded with references and cites to many more sources which are very detailed in nature. It is worthwhile to start here and identify the technique(s) that will work best for your organization then get into the details of actually applying.
On a different note, this book does sum up to a subtle sales pitch of Construx estimating software, which the author of the book was a critical figure in creating. However, the sales pitch doesn't get in the way of you still learning alot about the field of sotware estimation.
I have re-read some chapters, particularly towards the back of the book, countless time.
2 of 2 found the following review helpful:
 Title is a little misleadingNov 10, 2009
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.
1 of 1 found the following review helpful:
required reading for everyone in the software industryJul 04, 2009
"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.
1 of 1 found the following review helpful:
Very practical and useful, I DO recommend itApr 09, 2009
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
| | |
|
