Mcconnells Software Estimation Demystifying the Black Art P 4445

• Home
• My Books

Open Preview

See a Problem?

We'd love your help. Let the states know what's incorrect with this preview of Software Estimation by Steve McConnell.

Thanks for telling usa about the problem.

Friend Reviews

To see what your friends idea of this book, delight sign upward.

Community Reviews

 · 929 ratings  · 58 reviews

Start your review of Software Estimation: Demystifying the Black Art

Apr 19, 2013 Marek rated it liked information technology

"Software Estimation - Demystifying the Black Art" is a boring book. I read it because I wanted to accept tools to hash out the field of study, and I recollect this books accomplishes that.

To me, the beginning and last chapters which dealt with conceptualizing the problem space in general were the well-nigh interesting. The bulk of the book consists of dissimilar techniques to actual estimation, which I suppose would open up upward by actually trying to apply the methods described.

Overall I found the book to be interesting, a

"Software Estimation - Demystifying the Black Art" is a boring book. I read it because I wanted to accept tools to discuss the field of study, and I think this books accomplishes that.

To me, the commencement and concluding capacity which dealt with conceptualizing the problem infinite in general were the almost interesting. The bulk of the volume consists of different techniques to actual estimation, which I suppose would open up by actually trying to apply the methods described.

Overall I found the book to exist interesting, although somewhat tedious and more than geared toward estimating large projects on a high level. For a developer being asked for characteristic-level estimates it gives some tools for presentation and discussion, but not much more.

...more than

Jan 31, 2015 Ha Truong rated it it was amazing

An splendid book on software estimation.

Not like other books that scare readers at the first glance with sophisticated math equations, this book naturally comes with the practical methods (what, how, why and caveats). Information technology also provides enough of tips and diagrams to describe the definitions and methodologies.

Too, it states issues in reality and how to fix such every bit the interpretation tin can exist impacted by the executives or the marketers, the estimator should defend and brand an appropriate commitment

An first-class volume on software estimation.

Not like other books that scare readers at the kickoff glance with sophisticated math equations, this book naturally comes with the practical methods (what, how, why and caveats). Information technology also provides plenty of tips and diagrams to depict the definitions and methodologies.

Besides, information technology states bug in reality and how to fix such equally the interpretation tin exist impacted past the executives or the marketers, the estimator should defend and make an advisable delivery (concluding chapter)

...more

Oct 26, 2021 Bartosz rated it it was amazing

The most straightforward book I've establish on this subject field. Works groovy as a reference, and a textbook. Highly recommended to anyone who wants to upwards their estimation game.

May 21, 2009 Allisonperkel rated it it was amazing

"Software Estimation" past 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'southward books, he provides crystal articulate writing with tons of techniques that are ready for awarding in the real world.

I of the many keen things nigh "software Estimation" is the sheer number of methods he gives. From Lines of lawmaking, to role points, to similar projects, to manufacture estimates (broken down by sub cat

"Software Estimation" past Steve McConnell provides a very broad overview of many ways to reduce the software interpretation errors for your development wheel. Like all of Mr McConnell'south 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 virtually "software Interpretation" is the sheer number of methods he gives. From Lines of code, to function points, to like projects, to industry estimates (broken down past sub category so that database is different from embedded devices), to t shirt sizing, to maintaining development history: he makes it articulate that y'all have a lot of different options bachelor to you. He takes great pains to emphasize that one size does non fit all. Additionally he gives rationales for when the guess techniques work in a project'due south lifecycle.

With all the methods described, another bespeak driven habitation is that software is something of an fine art and that you can reduce the amount of doubt but y'all 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 truthful and in fact he goes a step further, pointing out that on successful projects the "cone of uncertainty" converges equally the projection matures. The antipodal is also true. Wise words indeed.

The terminal affiliate feels more like a tack on, still the bulletin independent therein is something that needs to be stated once more and again: marketing/direction is not the enemy. It is important to recall that anybody has the same goals and that the battle really should be a collaboration. However skilful 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 nearly estimation software packages. In fact, he makes assumptions that the reader has cognition of these packages. Working in start-ups, I've never even heard of these packages until this volume. Its a small gripe, merely it did detract. Another event would exist some of the examples on applying the various techniques towards the end of the book were far as well 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 ever a dangerous thing. Non as bad as fighting a land war in Asia, but still dangerous.

Overall though, as a software engineer/manager I establish this book to be invaluable. The techniques are usable correct 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.

...more

Keen insights into estimation. Some of the highlights to call out in my opinion:
- Articulate definitions and differentiation of: estimate, commitment, complexity assessment, schedule, conviction level, among others.
- The writer brings upward other topics that are usually forgotten when estimating a project, but definitely could impact it.
- The importance of being articulate about the cone of uncertainty and how to utilize it when creating/communicating estimates and confidence levels.
- Clarity into when it could Bang-up insights into estimation. Some of the highlights to call out in my stance:
- Clear definitions and differentiation of: estimate, delivery, complexity assessment, schedule, confidence level, amongst others.
- The writer brings upward other topics that are usually forgotten when estimating a project, but definitely could impact it.
- The importance of being clear virtually the cone of uncertainty and how to utilise it when creating/communicating estimates and confidence levels.
- Clarity into when it could exist a good time to add together more people to a project without actually pain information technology.
- Iterative vs sequential projects.
- Skillful references to other books to amplify other topics.

From the direction standpoint I value that the topic calls out anti patterns that organizations fall in when requesting for an estimate.
The volume definitely will give y'all a practiced tool prepare to look & create timelines and estimates from an unbiased stand up point. And it also makes yous understand how to connect the worlds of the people/stakeholders requesting the project and the teams actually estimating and executing.

My only feedback would exist that it would exist overnice to accept some more content on Agile projects. The topic is mentioned only in that location could be more virtually it. The book does recommend this other book:
https://world wide web.amazon.com/Agile-Estimati...

...more than

Jul 08, 2012 Erika RS rated it really liked it

Estimation is difficult in software and everywhere else. In this volume, McConnell provides the reader with tools to meliorate their interpretation skills. There are no silver bullets -- almost of these techniques take work and practice -- but by breaking downward the process of estimation McConnell takes it from a black art to something understandable.

The first part of the book covers fundamental concepts in interpretation. The eye of the volume is office ii which discusses many different estimation techniques, p

Estimation is difficult in software and everywhere else. In this book, McConnell provides the reader with tools to better their interpretation skills. There are no silver bullets -- most of these techniques take work and practise -- but past breaking downwardly the procedure of estimation McConnell takes information technology from a black art to something understandable.

The first role of the volume covers primal concepts in estimation. The heart of the book is part 2 which discusses many different estimation techniques, pros and cons of each, and times when a particular technique may be applicative. The concluding part of the book has farther discussion of some other issues in estimating.

Although this book is specific to software, the core insights information technology contains are also useful outside of software. My husband and I are building a house, and every bit I read this I found myself thinking "if our builder had used some of these techniques, we might have had a more authentic budget and schedule".

This book has made it onto my short list of "must read" books for developers, especially those with no previous exposure to formal discussions of interpretation.

...more

Aug 24, 2012 Michael rated it it was astonishing

Some other great volume from Steve McConnell. Obviously, subject matter expertize and lots of historical data are key to skilful estimates, just this volume is packed with real earth examples and complete explanations when you lot don't have that. Highly recommended. Another great book from Steve McConnell. Obviously, subject matter expertize and lots of historical data are key to good estimates, but this book is packed with real globe examples and consummate explanations when you don't take that. Highly recommended. ...more

When an idea is answerable with software, a stakeholder seeks a commitment from software developers to create that respond, from which all involved can make plans. To brand reasonable plans and commitments, information technology's skilful to take some time out to understand roughly what the scope of what the stakeholder wants is. This is estimation, and several unlike variables tin be estimated, among them: size (how big volition the concluding product be), effort (how much labor will go into the projection), schedule (when the When an idea is accountable with software, a stakeholder seeks a commitment from software developers to create that respond, from which all involved tin can make plans. To make reasonable plans and commitments, it's good to take some time out to understand roughly what the scope of what the stakeholder wants is. This is estimation, and several dissimilar variables tin be estimated, among them: size (how big will the final product exist), endeavor (how much labor will go into the project), schedule (when the project will be finished), and cost (how much money is needed to fund the project). Subsequently introducing interpretation terms, motivations, and principles, this book describes techniques for making estimates at various points in a project'south lifecycle and communicating them to stakeholders.

I got this book a while back, non long after discovering the author's other book Code Complete, a treasure trove of information on how to write adept code. During the pandemic, I saw charts the author was posting on social media and one of his videos virtually COVID and software interpretation, which rekindled my involvement in this topic.

Early in the book there's an illustrative examination to demonstrate what ninety% confidence is: The reader is asked to provide ranges for 10 random trivia questions. ninety% confidence means feeling sure the answer for 9 of the questions falls in your ranges. Information technology is a neat example of dubiousness, what techniques we naturally employ to gauge (one of the 3 I got right I used an analogy for the gauge), and dealing with the psychological pressure to narrow doubt ranges.

Another ideas from the book:

Best case, worst case, expected case. There's a limit on how good things tin can get. (The book mentions an Impossible Zone, where no matter how much effort you lot add together, you cannot produce the software any more ahead of schedule.) There's less of a limit on how "bad" -- ideas for new features aren't bad, but they're not always part of the original judge, commitment, or plan, and may warrant a re-judge -- things can go. (Mayhap a dev'southward piece of work, like a tailor'south, is never done.) But neither farthermost is necessarily likely. Thinking through what things would be like if everything went smoothly, and so turning to thinking if everything went incorrect, then choosing a betoken somewhere in between as an estimate has helped me come up upwards with very accurate estimates for effort.

Diseconomy of Scale. Linear relationships don't e'er hold the bigger a project gets. Bigger projects tend to require fifty-fifty more effort, take fifty-fifty more time, present even more risks (particularly more defects, which have a vicious cycle of requiring extra effort to fix), etc., than a proportionately smaller project.

Cone of Uncertainty. In the planning-production-commitment lifecycle of software, uncertainty is high earlier but tapers as the project continues and nears completion.

Accept some time out to think. Even an judge made after 15 minutes of thinking about the problem will be better than an off-the-cuff estimate.

As you can probably tell statistics plays a major role in software estimation. (And one of my personal takeaways from the pandemic, one of my main motivations for reading this book, is merely how important statistics is for decision-making in general.) I'm not a strong statistical thinker right now, but this volume has been written for a broad audience and employs applied and simple statistical techniques and rules-of-thumb over complex equations or theories.

While this book is directed at estimating software projects, I recall (with considerable translation) the same ideas could carry over into other domains. The writer himself mentions times where he used like techniques while writing Code Complete, a 1000-page book, using pages instead of KLOC (thousands of lines of code) and sections and chapters instead of feature points. The discussion in Chapter fifteen of how the author reached a better approximation of how long that book would be using formal estimation techniques than his original "gut experience" estimate is especially enlightening.

The parts nigh the end virtually projects were tougher for me to read because they were a fiddling out of my depth/experience, just information technology gave me a whole new appreciation for large-scale project management. For example, Chapter 19 talks about Space Shuttle software that was 20,000,000 lines of lawmaking, took 20,000 staff years, and had a failure probability of about fifty% -- and that's just the software! Nevertheless, that project produced code at nearly the same efficiency of an operating system project, despite being almost 10x larger than information technology in relevant areas. This example maybe also serves as a classic demonstration of the diminishing returns from Diseconomy of Scale.

The middle portion of the book (chapters 6-21) strikes me as good reference material to pull out when starting a new undertaking.

...more

This review has been hidden because it contains spoilers. To view information technology, click hither. A solid pick if you want to go some leverage the adjacent time your manager has your back against the wall trying to make you commit to some project impossible to evangelize in the preseneted timeframe.

You lot will get a expert understanding on what estimation means , how are estimates different from commitments and targets. One time yous realise this , your arroyo with non technical people from your organization will hopefully change radically

There's a lot of useful tips on topics such as interpretation errors ,

A solid option if you desire to get some leverage the next fourth dimension your manager has your back against the wall trying to brand you commit to some project impossible to deliver in the preseneted timeframe.

You will get a good understanding on what estimation ways , how are estimates different from commitments and targets. Once you realise this , your approach with non technical people from your organization will hopefully change radically

There's a lot of useful tips on topics such as estimation errors , planning , the cone of doubtfulness and many tools and approaches on figuring out how in deep shit you.are when starting a new project with the given resources or how badly the ongoing i was planned.

This one gets 3 stars since i was hoping for some end to stop scenarios like "you lot receive project 10 and yous practise Y,Z,T in this gild". I was expecting a bit of handholding and more than cohesion regarding the multiple tips and approaches you go familiar along the chapters.

...more

Mar 31, 2021 Bibek rated it liked it

I read a handful of capacity in a reading group with coworkers to run across if we could glean some insights for our own work. Information technology was useful insofar equally part one provided us with the vocabulary and mental frameworks for thinking about interpretation in full general. The meatier parts about how to actually go most estimating piece of work felt less direct relevant. The programming languages and practices referred to were somewhat dated (understandable since the book was written fifteen years ago) and the recommended technique I read a handful of chapters in a reading group with coworkers to see if we could glean some insights for our own work. Information technology was useful insofar as function 1 provided the states with the vocabulary and mental frameworks for thinking about estimation in general. The meatier parts nigh how to actually go near estimating work felt less directly relevant. The programming languages and practices referred to were somewhat dated (understandable since the book was written fifteen years agone) and the recommended techniques generally seemed more useful for large-scale organizations where the projects existence estimated take on the club of many months to years to complete. ...more

Every software engineer should read at least the first ten capacity of this book. These are the most insightful chapters that talk most what estimation is for, what to be wary of, and some basic ways of estimating. The biggest, most broadly useful takeaways boil down to a few rules of thumb and a scattering of equations, many of which are usefully collected in an Appendix.

The remainder of the book is a broad survey of techniques, but many of them are likely but applicative in a large company that has a l

Every software engineer should read at least the first ten chapters of this book. These are the near insightful chapters that talk about what estimation is for, what to be wary of, and some basic means of estimating. The biggest, most broadly useful takeaways boil downward to a few rules of pollex and a scattering of equations, many of which are usefully collected in an Appendix.

The rest of the book is a broad survey of techniques, but many of them are likely just applicable in a large company that has a lot of tape-keeping and is able to exercise things similar staff 20 person projects for several years.

...more

I would actually give this book 4.5 stars.

What I did not like:

- it's a scrap old;
- likewise much publicity for the software estimation tool the author worked on.

What I did like:

+ information technology really does its job - a listing of gotchas, suggestions and rules of thumb which seem helpful. A seasoned developer will recognize most of the suggestions as thoughts which we all become at 1 signal, and so forget. Here you can find them all in one place;
+ actually unproblematic to read and easy-going;
+ no rocket science.

I would really give this volume four.five stars.

What I did not like:

- it's a bit old;
- likewise much publicity for the software estimation tool the writer worked on.

What I did like:

+ it actually does its task - a list of gotchas, suggestions and rules of pollex which seem helpful. A seasoned programmer volition recognize near of the suggestions as thoughts which we all get at one indicate, then forget. Hither you can find them all in one place;
+ really simple to read and piece of cake-going;
+ no rocket scientific discipline.

...more than

Outset half of book could be called "Applied COCOMO 2", and the book largely presents most of its value to general SDLC practices stringing together a diversity of good sources and connecting the dots with applicative examples. For me the largest value was the smallest chapter where he takes those results and shows how to present them to stakeholders for "negotiation". Very well cited sources and arrangement skills volition allow this to be easily used equally a reference manual later. First half of book could be called "Practical COCOMO 2", and the book largely presents nearly of its value to general SDLC practices stringing together a variety of practiced sources and connecting the dots with applicable examples. For me the largest value was the smallest chapter where he takes those results and shows how to present them to stakeholders for "negotiation". Very well cited sources and organization skills will let this to exist easily used every bit a reference manual later. ...more

Solid principles that still apply today

Gets to the eye of real world software interpretation, targets, commitments and projection management challenges. Still relevant for whatsoever modern software project. Will definitely incorporate many of the tips on a daily basis.

Oct 01, 2017 Steve Fenton rated it it was amazing

McConnell is ever well researched and this is no exception. This volume covers pretty much everything to do with interpretation, including dysfunctions and abuses. A nifty handbook for interpretation.

Mar 23, 2018 Juan rated it it was amazing

This is a bones book for whatsoever software craftsman, essential after the initial steps of writing lawmaking profesionally.

Aug 24, 2018 Peter Aronson rated information technology really liked it

A solid, readable book on the various software estimation (fourth dimension, endeavor, telescopic, cost, etc.), with a ton of useful definitions and rules of pollex and advice.

This should be handed to anybody who works in software development as a must read. I program to read it many times over next years.

Accessible, comprehensive, still relevant, and a far more interesting read than one would expect from the subject area—worthy to have on a handy bookshelf.

old school book which does not really fit modern situation

Mar 29, 2020 Omar Trejo rated it it was amazing

Simple presentation of potentially complex topics with a very methodological and useful arroyo.

Aug 12, 2014 Eduard rated it it was astonishing

I read this as part of my chore. As an IT Consultant I was asked to judge several projects ranging from modest (ca. 50 workdays) up to medium (ca. 300-400 workdays) and confirm estimates on big projects (g+ workdays)
When yous depend on authentic estimates for profitable projects (especially when you are non on time & material), this is the tool to plow to. The intro and the showtime chapters confirmed many of my previously experiences from ca. 15 years of software development (including many horri I read this as role of my chore. As an IT Consultant I was asked to guess several projects ranging from pocket-size (ca. 50 workdays) up to medium (ca. 300-400 workdays) and confirm estimates on big projects (1000+ workdays)
When you depend on accurate estimates for profitable projects (especially when you are not on fourth dimension & material), this is the tool to turn to. The intro and the first capacity confirmed many of my previously experiences from ca. 15 years of software development (including many horrible results). The post-obit chapters are then more about how to apply different techniques to avoid the same traps.
What I actually appreciate about the author is that he doesn't requite y'all prescriptive solutions but instead draws on inquiry and many, many project results to support his conclusions and claims. This is a great departure from many software books I've seen over the years which claim their insights are the one and merely and solves so many of the bug other people take been experiencing.
I've had several discussions where people apartment out deny this is possible and therefore run into information technology as an argument for active development. I've found this mode of thinking is more self-serving: I don't want to take to say how long it takes, so I'll non try it at all. The book besides shows that estimating the effort to a sure accurateness is possible and which weather must exist met, to make this possible.

Decision: For anyone having to lead and organize a software projection this is a must-read, while anyone equally part of a team tin profit from knowing when your leads on the arrangement is talking bullsh*.

...more

May 18, 2014 Simon rated it it was astonishing

This volume gives a bully item clarification of what it means to estimate applied to the software engineering context. It starts off by defining what an estimate is, mutual problems with estimates, and the toll of underestimating. Information technology talks virtually estimation strategies and finally how to use them and issues that may occur when use them. At the very least for me it helps me recall about estimation more and gives me some tools to utilise while creating them. I imagine I will be going back and referenci This book gives a great item description of what information technology ways to estimate applied to the software technology context. It starts off by defining what an estimate is, mutual problems with estimates, and the cost of underestimating. Information technology talks most estimation strategies and finally how to utilize them and issues that may occur when apply them. At the very least for me it helps me retrieve about interpretation more and gives me some tools to use while creating them. I imagine I will be going back and referencing some of the chapters throughout my career. I besides recall I will print out the list of tips he has through out the book (placed in an appendix besides) and hang information technology on my wall at work as reminder to myself and others. ...more

January nineteen, 2016 Khang Nguyen rated it really liked it

Y'all can't be disappointed at a work of Steve McConnell. The volume provided a well-rounded wait into estimation as a process and set of techniques. Though the procedures are more for medium-large project, ones for pocket-size projects tin can be easily derived. Equally stated in the foreword, the book is not meant to cover the scientific discipline part of software estimate. However, every bit software has its firm root in math and estimation is an fine art with numbers, formulas are unavoidable. Readers are kind of forced to take the fo You can't exist disappointed at a work of Steve McConnell. The book provided a well-rounded look into estimation as a process and set of techniques. Though the procedures are more for medium-large projection, ones for small projects can exist easily derived. Every bit stated in the foreword, the book is not meant to cover the science part of software estimate. All the same, as software has its house root in math and estimation is an art with numbers, formulas are unavoidable. Readers are kind of forced to accept the formulas for grant, a few complicated one don't come with proper caption other than "statistical science proved that". Still a good read for small and medium software shops, besides as starter estimators. ...more than

Afterwards you piece of work for a while as a software developer or leader, y'all realize that almost every unmarried approximate you make is off by a significant amount. This book is total of applied communication that you tin can apply in your next estimate.

but the nearly of import accept outs are:
ane- you really don't understand estimates, and you lot make them wrong
2- you are not alone!

This book is very easy to ready. You could even take all the figures and images in this book, stick them on a newspaper and you got yourself a visual

After yous work for a while as a software developer or leader, you realize that almost every single estimate yous make is off past a meaning amount. This volume is full of applied advice that yous can utilise in your adjacent approximate.

only the near important take outs are:
1- y'all really don't understand estimates, and you make them wrong
2- you are not alone!

This book is very easy to ready. You could even take all the figures and images in this book, stick them on a paper and y'all got yourself a visual guide on how to brand estimates.

...more

Jan 18, 2009 steve rated it information technology was astonishing

So I plan on re-reading this book and providing a much more detailed review, merely the brusque answer is that I think near this book on a daily basis now. A lot of it falls in to the "then apparently correct that it shouldn't even need to be pointed out." But approximate what? It had never been pointed out to me before.

Anyhow, I'thousand super into this book. If you demand to provide software estimates, I highly advise yous check it out.

Steve

So I plan on re-reading this volume and providing a much more detailed review, but the brusk answer is that I think well-nigh this book on a daily basis at present. A lot of information technology falls in to the "then obviously right that it shouldn't even need to be pointed out." But estimate what? It had never been pointed out to me before.

Anyway, I'm super into this book. If you lot need to provide software estimates, I highly propose you check it out.

Steve

...more

May 05, 2015 Krishna Kumar rated it information technology was amazing

A swell introduction to software estimation techniques, this volume is about both the fine art and science of estimation. Steve McConnell discusses the various methods to derive estimates and reduce the inherent unpredictability. The author tries to keep down the level of complexity when mentioning the different scientific estimation techniques in the industry. Finally, he elaborates on specific issues and challenges in estimation, including organizational pressures.

Some nice hints and ideas are expressed along the volume. The estimation approach though is old style. Also many of the exposed techniques are based on Lines of Code, and many formulas seem not very useful. It was the first book about estimation I've read, and it'southward been useful. I'm sure though that at that place are better books on this topic Some overnice hints and ideas are expressed along the book. The interpretation arroyo though is old fashion. Besides many of the exposed techniques are based on Lines of Lawmaking, and many formulas seem not very useful. Information technology was the first volume about estimation I've read, and it'south been useful. I'k certain though that there are better books on this topic ...more

Jan 07, 2013 Stephen rated it really liked it

Solid volume that gave me a lot of what I was looking for. A lot of the tips are based on historical data, which my company doesn't have, so they're not something I tin can implement correct away. I guess I'll have to first collecting data now. The t-shirt sizing and the distinction McConnell makes between estimates, targets, and commitments are very useful. Solid book that gave me a lot of what I was looking for. A lot of the tips are based on historical data, which my company doesn't have, so they're non something I can implement right away. I gauge I'll take to start collecting data now. The t-shirt sizing and the stardom McConnell makes betwixt estimates, targets, and commitments are very useful. ...more

Goodreads is hiring!

If you lot like books and love to build absurd products, we may be looking for you lot.
Larn more »

News & Interviews

In the U.S., May is the month when we shine a item spotlight on the heritage, history, and contributions of Asian Americans and Pacific...

"The only way to reduce the variability in the judge is to reduce the variability in the project." — 2 likes

"When executives ask for an "estimate," they're often asking for a commitment or for a plan to meet a target." — ane likes

More quotes…

Welcome back. Simply a moment while we sign yous in to your Goodreads business relationship.

sawyerbrigingening.blogspot.com

Source: https://www.goodreads.com/book/show/93891.Software_Estimation

Share this post