Software Estimation: Demystifying the Black Art and over one million other books are available for Amazon Kindle. Learn more

Vous voulez voir cette page en français ? Cliquez ici.


or
Sign in to turn on 1-Click ordering.
or
Amazon Prime Free Trial required. Sign up when you check out. Learn More
More Buying Choices
Have one to sell? Sell yours here
Start reading Software Estimation on your Kindle in under a minute.

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Software Estimation: Demystifying the Black Art [Paperback]

Steve McConnell
5.0 out of 5 stars  See all reviews (2 customer reviews)
List Price: CDN$ 41.99
Price: CDN$ 26.32 & FREE Shipping. Details
You Save: CDN$ 15.67 (37%)
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Only 5 left in stock (more on the way).
Ships from and sold by Amazon.ca. Gift-wrap available.
Want it delivered Tuesday, September 23? Choose One-Day Shipping at checkout.

Formats

Amazon Price New from Used from
Kindle Edition CDN $17.27  
Paperback CDN $26.32  
Save Up to 90% on Textbooks
Hit the books in Amazon.ca's Textbook Store and save up to 90% on used textbooks and 35% on new textbooks. Learn more.
Join Amazon Student in Canada


Book Description

Feb. 22 2006 0735605351 978-0735605350 1

Often referred to as the “black art” because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact, generating accurate estimates is straightforward—once you understand the art of creating them. In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation—distilling academic information and real-world experience into a practical guide for working software professionals. Instead of arcane treatises and rigid modeling techniques, this guide highlights a proven set of procedures, understandable formulas, and heuristics that individuals and development teams can apply to their projects to help achieve estimation proficiency.
Discover how to:

  • Estimate schedule and cost—or estimate the functionality that can be delivered within a given time frame
  • Avoid common software estimation mistakes
  • Learn estimation techniques for you, your team, and your organization * Estimate specific project activities—including development, management, and defect correction
  • Apply estimation approaches to any type of project—small or large, agile or traditional
  • Navigate the shark-infested political waters that surround project estimates

When many corporate software projects are failing, McConnell shows you what works for successful software estimation.

Frequently Bought Together

Software Estimation: Demystifying the Black Art + The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) + Code Complete (2nd Edition)
Price For All Three: CDN$ 85.99


Customers Who Bought This Item Also Bought


Product Details


Product Description

About the Author

Steve McConnell is recognized as one of the premier authors and voices in the development community. He is Chief Software Engineer of Construx Software and was the lead developer of Construx Estimate and of SPC Estimate Professional, winner of Software Development magazine's Productivity Award. He is the author of several books, including Code Complete and Rapid Development, both honored with Software Development magazine's Jolt Award.


Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index
Search inside this book:

Customer Reviews

4 star
0
3 star
0
2 star
0
1 star
0
5.0 out of 5 stars
5.0 out of 5 stars
Most helpful customer reviews
2 of 2 people found the following review helpful
Format:Paperback
A friend had referred this book to me while I was researching estimation process and tools for my company. I found that many other books tended to be either too high level (basic stuff that we all know) or very scientific and thus hard to digest, but this book was a comfortable read and describes the topic is a fair amount of understandable detail.

I highly recommend it.
Was this review helpful to you?
0 of 7 people found the following review helpful
5.0 out of 5 stars Delivery service Jan. 22 2010
Format:Paperback
Placing order is easy, relaible and delivery is as per given time. Quality of the item is very good.
Was this review helpful to you?
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com: 4.6 out of 5 stars  53 reviews
59 of 61 people found the following review helpful
5.0 out of 5 stars Software Estimation as an Art July 4 2006
By Erik Gfesser - Published on Amazon.com
Format:Paperback|Verified Purchase
McConnell immediately differentiates between software estimation as a science and software estimation as an art within the first pages of the introduction to this work - he explains that while software estimation research is currently focused on improving estimation techniques so that project results are achieved within +/- 5% of esimated results, the techniques of which are best included in commerical software estimation tools that are used to pursue the science of estimation for very large projects, the typical software organization struggles to avoid estimates that are incorrect by 100% or more, and Software Estimation discusses the estimation techniques comprising, although not limited to, the art of estimation that will reduce estimation error to about 25% or less, which is what the vast majority of software projects need. This book is absolutely the best software estimation text I have read to date. As Joel Spolsky mentions on the back cover of the book, the vast majority of software project managers still think that estimates are based on multiples of a gut feel. This philosophy completely ignores the vast body of research and hands-on experience of the last few decades. McConnell explains with sufficient depth all of the ways to create "ball park" estimates, and if there is one chapter of this book that you read, Chapter 4 "Where Does Estimation Error Come From?" is the one that I recommend - the explanation of the Cone of Uncertainty is so well explained that anyone can understand it. Although I have never read Code Complete by the same author, I did purchase Rapid Development several years ago - and I must say that McConnell (or at least his editors) has vastly improved his writing skills. This book is less than half the size of Rapid Development, and while I fell asleep while reading that book I was able to conduct a cursory reading of over half of Software Estimation in one evening and immediately apply some of its concepts on a work project the following day. A great modern follow-up to The Mythical Man-Month by Brooks and an excellent primer to reading SEI's Estimating Software-Intensive Systems by Stutzke on the science of estimation.
43 of 48 people found the following review helpful
5.0 out of 5 stars Finally, an excellent source for estimation of software projects May 31 2006
By Tom Carpenter - Published on Amazon.com
Format:Paperback
I must admit, I was very surprised to see an excellent source on software development time and cost estimation from Microsoft Press. However, when I saw that the author was Steve McConnell, the author of Code Complete (which I thought was a great book) I knew that this book would have something to offer.

His definition of the purpose of software estimation is important: "The primary purpose of software estimation is not to predict a project's outcome; it is to determine whether a project's targets are realistic enough to allow the project to be controlled to meet them."

From this premise, the author continues to prove that software estimation is about determining if you can control a project to bring it in reasonably close to the organization's targets. In addition to this, Mr. McConnell's arguments for overestimation being better than underestimation are rather good and have convinced me to continue using my risk time and budget items that I've been using and recommending to others.

In chapter 4, the author identifies four main sources of project estimation errors:

-Inaccurate information about the project being estimated
-Inaccurate information about the capabilities of the organization that will perform the project
-Too much chaos in the project to support accurate estimation (that is, trying to estimate a moving target)
-Inaccuracies arising from the estimation process itself

That last one presents the need for me to give a little more information. The author suggests that bias and subjectivity of the estimator cause major estimation errors in the estimation process. This is proven through exercise case studies of time estimation in training classes. The author found that the more "control knobs" (impacting factors considered when estimating the project) used in the estimation process the greater the probability of variance in the estimates. He attributes this to bias and estimator subjectivity and it makes a lot of sense.

In the end, this book will make you a better estimator and project manager and I highly recommend it.

Tom Carpenter, Author: Wireless# Certification Official Study Guide, CWSP Certification Official Study Guide, Project Management for the IT Pro, and Foundations of Effectiveness
47 of 54 people found the following review helpful
5.0 out of 5 stars Develops a concrete approach for software estimation April 14 2006
By calvinnme - Published on Amazon.com
Format:Paperback
This is Steve McConnell's latest published effort on software engineering. The book is divided into three parts: estimation concepts, techniques, and challenges respectively. The first part of the book, on concepts, is just a broad overview designed to convince the software engineer of the value of estimation and how, done incorrectly, it can mess up what would have been a successful project. The second part, on techniques, is the meatiest part of the book. Here the author combines tried and true computational techniques with your own judgement and reminds you to get the expert opinion of other people too when estimating a project. Finally, the third and last part of the book, on challenges, talks about how you must think "out of the box" when you confront a software project whose size, effort, and schedule may be hard to quantify completely. Finally, McConnell points out the importance of politics and group dynamics in general in estimation. This is important, as many software engineers and project managers tend to be lone wolves that want to go off in a corner and solve problems by themselves. I highly recommend this book to all software engineers and particularly to software project managers. Amazon does not show the table of contents, so I do that here:

CRITICAL ESTIMATION CONCEPTS

1 What is an "estimate"? 3

2 How good an estimator are you? 15

3 Value of accurate estimates 21

4 Where does estimation error come from? 33

5 Estimate influences 55

FUNDAMENTAL ESTIMATION TECHNIQUES

6 Introduction to estimation techniques 77

7 Count, compute, judge 83

8 Calibration and historical data 91

9 Individual expert judgment 105

10 Decomposition and recomposition 113

11 Estimation by analogy 127

12 Proxy-based estimates 135

13 Expert judgment in groups 149

14 Software estimation tools 157

15 Use of multiple approaches 165

16 Flow of software estimates on a well-estimated project 171

SPECIFIC ESTIMATION CHALLENGES

17 Standardized estimation procedures 181

18 Special issues in estimating size 197

19 Special issues in estimating effort 207

20 Special issues in estimating schedule 221

21 Estimating planning parameters 233

22 Estimate presentation styles 249

23 Politics, negotiation, and problem solving 259

A Estimation Sanity Check 271

B Answers to Chapter 2 Quiz, "How Good an Estimator Are You?" 273

C Software Estimation Tips 275
14 of 14 people found the following review helpful
5.0 out of 5 stars Most Useful Book I've found on Software Estimation Jan. 11 2007
By Kiwi - Published on Amazon.com
Format:Paperback
There's a number of books out there now on software estimation, certainly more than there were a few years ago. I've worked my way through a few of them as I found myself involved in software estimation for larger (50 person +) projects that required a little more than the seat of the pants guesstimating techniques that so many of us IT project managers use with the usual results. Doesn't matter so much on smaller projects, but on large multi-year projects inaccurate estimates can have a deterimentary effect on one's career.

The book really does demystify estimating. It does a good job in Part 1 (5 chapters) of explaining crtical estimation concepts - very important for the neophyte at more formal estimating. Part 2 (12 chapters) covers a range of "Fundamental Estimation Techniques" and does it really well. There's enough information to get you started without being overwhelming

Part 3 (Specific Estimation Challenges - 6 chapters) covers challenges you will face with your estimating and presents useful practical approaches to these. All in all, it's a very useful and practical reference book for all those involved in estimating and presented at a level that the beginner can absorb and use practically. It doesn't overwhelm with detail on any one technique, it's more an introduction to the field, but an introduction that will get you started successfully and form a basis from which you can specialize further.

Steve McConnell's a well-know author with a number of useful books published previously - "Rapid Development" and "Code Complete" in particular. He's gpt experience in the field and he writes well, the books coherent, logically structured and it won't (unlike so many technical books) put you to sleep.
23 of 26 people found the following review helpful
5.0 out of 5 stars Estimation: art or science? March 15 2006
By Ivo Michalick - Published on Amazon.com
Format:Paperback|Verified Purchase
This is a great book for software project managers, or any professional directly involved with the difficult task of predicting how long will it take and how much will it cost to develop a software project based on its initial requirements/scope definition.

Steve McConnell is an essential author in regards to software development issues, and this book delivers on its subtitle: "Demystifying the Black Art", showing the main aspects involved in software estimation and how it is possible to produce reasonably accurate estimates using techniques based on things like group work, personal experience, expert judgement, past history and a lot of common sense. Chapter Four ("Where Does Estimation Error Come From"), with its description of the "Cone of Uncertainty", is a must-read for those who want to understand how good an estimate can be, and where we make the most common errors so we can avoid them.

The book doesn't delve deep into any specific technique, what makes it more useful and easier to read, since some techniques are so complex that it takes hundreds of pages to describe them well. I believe it will become another classic, like "Rapid Development" and "Code Complete"!
Search Customer Reviews
Only search this product's reviews

Look for similar items by category


Feedback