- Paperback: 352 pages
- Publisher: Microsoft Press; 1 edition (4 Mar. 2006)
- Language: English
- ISBN-10: 0735605351
- ISBN-13: 978-0735605350
- Product Dimensions: 18.5 x 2.5 x 22.4 cm
- Average Customer Review: 4.6 out of 5 stars See all reviews (7 customer reviews)
Amazon Bestsellers Rank:
245,774 in Books (See Top 100 in Books)
- #318 in Books > Computers & Internet > Computer Science > Programming > Software Design, Testing & Engineering > Software Architecture
- #321 in Books > Computers & Internet > Computer Science > Programming > Software Design, Testing & Engineering > Functional Programming
- #332 in Books > Computers & Internet > Computer Science > Networking & Security > Network Topics
- See Complete Table of Contents
Software Estimation: Demystifying the Black Art Paperback – 4 Mar 2006
|New from||Used from|
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Frequently Bought Together
Customers Who Bought This Item Also Bought
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
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.
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
At the beginning of the book you are bombarded with stories about how wrong estimations can be and presents you with tons of statistics, you start to think "hey! These guys didn't know anything about estimations!" but when you continue reading I started to realize that their estimations are based on pillars that I am also using... scary. At this stage I was more interested on the book.
The book is full of tips and descriptions about the different areas that you must consider on your estimations, taking into account size, effort, schedule and tons of planning parameters. This book is a recommended one to have on your bookshelf as you cannot remember all these things in one go. Another interesting area of the book is the negotiation skills, who wasn't involved in a situation where your boss tells you to introduce hundreds of features within the same timeframe? Well, this book helps you to deal with those situations.
The only reason why I don't give it 5 stars is because of the amount of stats, that actually cuts the flow of the reading on every page. But trust me, you won't regret.
I liked in particular the clear distinction the book makes between estimates, targets and commitments. Also, the political minefield associated with estimates is discussed well. Another area which I liked very much is the emphasis on clarifying the assumptions on which the estimates were based.
Having said this, the book could be even better if it would explore deeper the following topics:
1) Who are permitted to estimate? The book loosely mentions that the best estimators are those who will do the work. True, but this is a minimum requirement.
2) What exactly is estimated? It takes about 20 chapters before the author mentions that most of the rules and benchmark material refer to the design, construction and testing of software (excluding requirements gathering and project management). It would be helpful if the scope of the software development would have been described more precisely from the beginning
3) A software development project most likely will be embedded in a larger project intending to deliver a business change. The book would have benefited from exploring the relationship (regarding effort, cost, schedule) with the components of the larger project
4) The book does not mention the relationship with benefit estimation. Also, today's software engineers are expected to be able to speak the language of finance, and the book would have benefited by discussing the time value of money, capitalization etc.
Nevertheless, this is a must buy for software engineers and managers who are involved in project estimation.
Both are great reading when I'm travelling and I tend to read the Kindle version as both books (in paper) are weighty tomes.
One thing that's a bit odd with this book is that there's no Table of Contents on the Kindle Version. Hence -1 Star.
In my kindle version, there's sections Cover,Software Estimation..,Welcome,Acknowledgements,Equations,Figures,I,II,III,A,B,C,Bibliography,Steve McConnell,Index,About the Author,Copyright,Location.
In my paper version, on page iii, there's contents at a glance, and on page v there's Table Of Contents.
I wonder if this was missed in the conversion?!
I must admit that I did not throw my money away. McConnel's book is a step by step approach to software estimation based on a collection of facts and study results. He drives you through those techniques in a progressive way and compiles a list of tips that everyone shall keep handy.
The book covers major estimation techniques as well as provides directions as to when to apply them to ensure that one gets the most accurate results. The most important idea that the book conveys is that one shall always try and find something to count in order to compute and not to guess.
To make a long story short, this book's a must have.
Most Recent Customer Reviews
McConnell's books include "Rapid Development", a title that is still the best book on software development techniques that we would now call "agile" - although the book predates... Read morePublished on 30 Mar. 2012 by Amazon Customer
Steve McConnell gives a good and thorough overview of software estimation practices and especially the very critical aspect of working with stakeholder expectations, i.e. Read morePublished on 11 Nov. 2011 by Montecristo
Look for similar items by category
- Books > Computing & Internet > Computer Science > Information Systems
- Books > Computing & Internet > Digital Lifestyle > Online Shopping > Amazon
- Books > Computing & Internet > Networking & Security > Network Topics
- Books > Computing & Internet > Programming > Software Design, Testing & Engineering > Functional Programming
- Books > Computing & Internet > Programming > Software Design, Testing & Engineering > Software Architecture