 See larger picture | The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)
by
Frederick P. Brooks
- Addison-Wesley ProfessionalList Price: $39.99
Price at Amazon.com: $31.19
(Save
22%)
 Availability: Usually ships in 24 hours
Shipping rates and policies |
- Average Customer Review:
Based on
129
reviews.
- Amazon.com Sales Rank: 3267
|
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.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.
Featured Customer Reviews  Sharp and thoroughly enjoyable,
December 15, 2008
When it comes to designing complex systems, some big problems cannot be tackled by simply throwing more resources at them. That's a profound and scary observation, especially to those responsible for managing these resources.
This book has had a huge impact on the discourse you read about software engineering, particularly on the web (blogs, articles). The views expressed by Mr. Brooks have reached common acceptance in those circles. I must wonder to what extent they have percolated into the workplace however.
I suggest contrasting this book with "The Cathedral and the Bazaar" by Eric S. Raymond for a different perspective on large software development and scaling issues, in the open source community. Interesting case study,
November 16, 2008
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 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 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!
You might also be interested in these items...
|
|