- Paperback: 336 pages
- Publisher: Addison-Wesley Professional; Anniversary edition (August 12, 1995)
- Language: English
- ISBN-10: 0201835959
- ISBN-13: 978-0201835953
- Product Dimensions: 6 x 0.9 x 9 inches
- Shipping Weight: 1 pounds (View shipping rates and policies)
- Average Customer Review: 4.4 out of 5 stars See all reviews (291 customer reviews)
Amazon Best Sellers Rank:
#9,360 in Books (See Top 100 in Books)
- #1 in Books > Computers & Technology > Hardware & DIY > Microprocessors & System Design > Microprocessor Design
- #8 in Books > Textbooks > Computer Science > Software Design & Engineering
- #18 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
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.
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) Anniversary Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2017 So Far
Looking for something great to read? Browse our editors' picks for the best books of the year so far in fiction, nonfiction, mysteries, children's books, and much more.
Frequently bought together
Customers who bought this item also bought
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.
From the Inside Flap
To my surprise and delight, The Mythical Man-Month continues to be popular after twenty years. Over 250,000 copies are in print. People often ask which of the opinions and recommendations set forth in 1975 I still hold, and which have changed, and how. Whereas I have from time to time addressed that question in lectures, I have long wanted to essay it in writing.
Peter Gordon, now a Publishing Partner at Addison-Wesley, has been working with me patiently and helpfully since 1980. He proposed that we prepare an Anniversary Edition. We decided not to revise the original, but to reprint it untouched (except for trivial corrections) and to augment it with more current thoughts.
Chapter 16 reprints "No Silver Bullet: Essence and Accidents of Software Engineering," a 1986 IFIPS paper that grew out of my experience chairing a Defense Science Board study on military software. My co-authors of that study, and our executive secretary, Robert L. Patrick, were invaluable in bringing me back into touch with real-world large software projects. The paper was reprinted in 1987 in the IEEE Computer magazine, which gave it wide circulation.
"No Silver Bullet" proved provocative. It predicted that a decade would not see any programming technique which would by itself bring an order-of-magnitude improvement in software productivity. The decade has a year to run; my prediction seems safe. "NSB" has stimulated more and more spirited discussion in the literature than has The Mythical Man-Month. Chapter 17, therefore, comments on some of the published critique and updates the opinions set forth in 1986.
In preparing my retrospective and update of The Mythical Man-Month, I was struck by how few of the propositions asserted in it have been critiqued, proven, or disproven by ongoing software engineering research and experience. It proved useful to me now to catalog those propositions in raw form, stripped of supporting arguments and data. In hopes that these bald statements will invite arguments and facts to prove, disprove, update, or refine those propositions, I have included this outline as Chapter 18.
Chapter 19 is the updating essay itself. The reader should be warned that the new opinions are not nearly so well informed by experience in the trenches as the original book was. I have been at work in a university, not industry, and on small-scale projects, not large ones. Since 1986, I have only taught software engineering, not done research in it at all. My research has rather been on virtual reality and its applications.
In preparing this retrospective, I have sought the current views of friends who are indeed at work in software engineering. For a wonderful willingness to share views, to comment thoughtfully on drafts, and to re-educate me, I am indebted to Barry Boehm, Ken Brooks, Dick Case, James Coggins, Tom DeMarco, Jim McCarthy, David Parnas, Earl Wheeler, and Edward Yourdon. Fay Ward has superbly handled the technical production of the new chapters.
I thank Gordon Bell, Bruce Buchanan, Rick Hayes-Roth, my colleagues on the Defense Science Board Task Force on Military Software, and, most especially, David Parnas for their insights and stimulating ideas for, and Rebekah Bierly for technical production of, the paper printed here as Chapter 16. Analyzing the software problem into the categories of essence and accident was inspired by Nancy Greenwood Brooks, who used such analysis in a paper on Suzuki violin pedagogy.
Addison-Wesley's house custom did not permit me to acknowledge in the 1975 Preface the key roles played by their staff. Two persons' contributions should be especially cited: Norman Stanton, then Executive Editor, and Herbert Boes, then Art Director. Boes developed the elegant style, which one reviewer especially cited: "wide margins, and imaginative use of typeface and layout." More important, he also made the crucial recommendation that every chapter have an opening picture. (I had only the Tar Pit and Rheims Cathedral at the time.) Finding the pictures occasioned an extra year's work for me, but I am eternally grateful for the counsel.
Deo soli gloria or Soli Deo Gloria -- To God alone be the glory.
Chapel Hill, N.C., F.
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top customer reviews
IMHO, Brooks has distilled fundamental truths; you might find his ideas slightly outdated; but all will agree Brooks offers at least excellent insights. To list but a few: build times determine programmer work cycle; agreement on high-level goals is essential; dev tools make a huge difference; visualizing code is a hard problem; programmers are optimists.
=== Superbly edited ===
If you've a background in editing (developmental down to line), you will be impressed by this text. "Perfection is achieved, "said Saint-Exupery, "when there's nothing left to take away"; and that is absolutely the case here. Every point is pertinent to the thesis, every sentence is necessary, every phrase concise. (I cannot say the same of Brooks's follow-on book, "Design of Design".)
=== Classy ===
Brooks was the project manager for the OS/300, a $5B endeavor that IBM bet its future on, an engineering effort of the highest magnitude, and a spectacular success. But whenever he mentions an aspect or feature where he feels OS/300 excelled, he always gives complete credit to whomever designed that aspect or implemented that feature; and whenever he mentions an area where he feels OS/300 fell short, he takes complete personal responsibility for the shortcoming.
It is dense, every sentence is necessary and relevant. The allusions, metaphors, and examples all help to paint and SHOW not TELL the author's ideas.
A cross between literary masterpiece and dialogue about software engineering, this novel will stand the test of time.
This book is wonderful no matter where you are in your career. With each reread - even if it's just a chapter or two - the words seem to have been written yesterday by someone you work with.
The first time I borrowed it from the library, this time I read the kindle version and keep a paper copy at work when I need some help to back up my philosophies on software engineering. Brooks writes in in a style so even the non-technical can understand, however I don't recommend giving it as a gift to a boss hoping to make him or her "see the light."
The core take away is that communication is key to any project's success and gets more difficult the more people involved, specifically by the formula n(n-1)/2. It also addresses many aspects of software that aren't immediately obvious such as: bugs tend to show up the longer a product is live. That runs counter to what many - especially users - think of "mature" software, but a good thing to keep in mind as you "go live" and shift all your developers to other projects.
The only quibble I have with the book is that the author sees it fit to litter the book with religious quotes and observation, about the might of God and His grace - there is a time for religion and there is a time for software engineering pearls of wisdom - and the two should not be mixed.
If you have any interest in philosophy, computer science, or good writing, this book is well worth your time. If you are interested in two or three of them, it's a must-read. This is a classic in the software development space and has been extremely influential for many years.
Mr. Brooks' writing style is impeccable; he carefully dissects and examines each topic, with the wit and wisdom merited by such a technical field, yet he does it without using a lot of double-speak or unnecessary "fluff" - not a true text but rather a collection of essays, each chapter comes across as a polished, finished product, well-focused on a single topic.
This particular edition is also highly recommended. It contains four additional chapters: No Silver Bullet, yet another influential essay by Brooks that was not in the original edition; an overview of all his points (the entire book) in an easy-to-digest format; his thoughts 20 years on from writing the original, and how the industry has changed in that time; and finally, his responses to various criticism he has received over the years specifically in response to the "No Silver Bullet" essay.
This is an excellent purchase and a great read.