The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) | 
 enlarge | Author: Frederick P. Brooks
Publisher: Addison-Wesley Professional
Category: Book
List Price: $39.99
Buy Used: $18.06
You Save: $21.93 (55%)
New (41) Used (46) Collectible (1) from $18.06
Avg. Customer Rating:  128 reviews
Sales Rank: 4644
Format: Special Edition
Media: Paperback
Edition: 2
Number Of Items: 1
Pages: 336
Shipping Weight (lbs): 0.9
Dimensions (in): 8.9 x 6.1 x 0.6
ISBN: 0201835959
Dewey Decimal Number: 005.1068
UPC: 785342835953
EAN: 9780201835953
ASIN: 0201835959
Publication Date: August 12, 1995
Availability: Usually ships in 1-2 business days
Shipping: Expedited shipping available
Shipping: International shipping available
Condition: PREVIOUS OWNERS NAME AND OR INSCRIPTION WRITTEN IN FRONT OF BOOK Clean, nice condition. Expedited orders placed before 3 PM EST ship the SAME DAY. Automatic Upgrade to Priority Mail shipping on U.S. orders over $40. Multiple books ordered from Look at a Book in a single checkout will help you reach the $40 threshold for your free Priority Mail Upgrade! Satisfaction Guaranteed!
|
| Also Available In:
|
| Accessories:
|
| Similar Items:
|
| Editorial Reviews:
Amazon.com Review
The classic book on the human elements of software engineering. Software tools and development environments may have changed in the 21 years since the first edition of this book, but the peculiarly nonlinear economies of scale in collaborative work and the nature of individuals and groups has not changed an epsilon. If you write code or depend upon those who do, get this book as soon as possible -- from Amazon.com Books, your library, or anyone else. You (and/or your colleagues) will be forever grateful. Very Highest Recommendation.
Product Description
No book on software project management has been so influential and so timeless as The Mythical Man-Month. Now 20 years after the publication of his book, Frederick P. Brooks, Jr. (best known as the "father of the IBM System 360") revisits his original ideas and develops new thoughts and advice both for readers familiar with his work and for readers discovering it for the first time.
|
| Customer Reviews: Read 123 more reviews...
 Interesting case study November 16, 2008
The first half of the book is a case study of the development of OS/360 in the 1970s: what the problems were, what was tried, what worked and what didn't. While I (and probably many others) snicker at the state of technology then compared to what it is now, I feel that the lessons Brooks learned (and happily relays to the reader) are still relevant and valuable. You certainly will have to abstract the methodology to the current technology we have today, but managerial lessons, as I said, are still relevant, mostly because people haven't changed that much. Basically, adding more people to already-late projects makes things worse. All of the communication and documentation that goes along with large projects are 100% necessary, and the documentation should be about 90% complete before coding starts. I think a wiki would solve both of these issues in one shot, but that's me. The last half of the book is mostly an inner dialogue by Brooks about what he thinks of the lessons he preached, what other people in the industry have said about his book, and his responses to it.
I think this is a definite must-read for anyone that programs on large software projects or manages large software projects. Brooks comes right out and says at the beginning that other engineering disciplines already know about all of the project management overhead, which I agree with, because I am in one of those other disciplines. Apparently the programming people don't see it necessary to teach project management as part of a bachelor's degree program, which might explain a lot of the larger programs in the past few decades. I have to admit though, the entire computer industry, both hardware and software, has been through a tumultuous and extraordinarily rapid history. Other disciplines have a much longer history book from which to reflect and design better processes, management or otherwise.
Finally, the prose is dry sometimes awkward, which I suppose is typical of the professor types with delusions of eloquence. Despite that, I thought it was overall an easy read, though not as humorous and engaging as some of the other software books I've been through.
 Software Development September 26, 2008
1 out of 1 found this review helpful
The Mythical Man-Month: Essays on Software Engineering is a book on software project management by Fred Brooks, whose central theme is that "Adding manpower to a late software project makes it later." This idea is known as Brooks's law, and is presented along with the second-system effect and advocacy of prototyping. The work was first published in 1975, and republished as an anniversary edition in 1995 (ISBN 0-201-83595-9) with the essay "No Silver Bullet" and commentary by the author.
Brooks's observations are based on his experiences at IBM while managing the development of OS/360. He had mistakenly added more workers to a project falling behind schedule. He also made the mistake of asserting that one project -- writing an Algol compiler -- would require six months--regardless of the number of workers involved (it required longer). The tendency for managers to repeat such errors in project development led Brooks to quip that his book is called "The Bible of Software Engineering" because "everybody reads it but nobody does anything about it!"
Excellent & Highly Recommended Book August 17, 2008
1 out of 1 found this review helpful
I have read this book twice now. Once in college and once again now 5 years later. While I did not get much out of it 5 years ago, now that I have been in the industry a few years, it is a VERY good re-read.
Required Reading For Anyone Serious About Software Development June 19, 2008
30 Years later this book is still highly relevent. If your project is in trouble, don't add bodies!
seminal classic May 19, 2008
Fred Brooks, the author, is the individual primarily responsible for the IBM System/360, arguably the most successful computer software system built to this point. He is also primarily responsible for the IBM OS/360, which was not as successful. You may find that his frank and honest assessment of why one was successful and one was not provides a map of a right way to develop software and an alert system for what can go wrong. Because of this and the distilled thought and experience present in the book, it would be difficult to find a resource that could better prepare you to develop good software.
|
|
|
News 
