- Paperback: 336 pages
- Publisher: Addison-Wesley Professional; Anniversary edition (August 12, 1995)
- Language: English
- ISBN-10: 0201835959
- ISBN-13: 978-0201835953
- Product Dimensions: 6.1 x 1 x 9.1 inches
- Shipping Weight: 1.2 pounds (View shipping rates and policies)
- Average Customer Review: 301 customer reviews
Amazon Best Sellers Rank:
#8,342 in Books (See Top 100 in Books)
- #1 in Books > Computers & Technology > Hardware & DIY > Microprocessors & System Design > Microprocessor Design
- #6 in Books > Textbooks > Computer Science > Software Design & Engineering
- #15 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.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
Frequently bought together
Customers who bought this item also bought
Customers who viewed this item also viewed
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.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
You will realize that long before maybe you were even born, other people working at places like IBM had already experienced those problems and quandries. And found working solutions to them which are as valid today as they were 30 years ago.
The suggestions in this book will help you think better and better manage yourself, and be more productive and less wasteful with your time and energy. In short, you will do more with less.
Some of Brooks insights and generalizations are:
The Mythical Man-Month:
Assigning more programmers to a project running behind schedule, may make it even more late.
The Second-System Effect:
The second system an engineer designs is the most bloated system she will EVER design.
To retain conceptual integrity and thereby user-friendliness, a system must have a single architect (or a small system architecture team), completely separate from the implementation team.
The chief architect should produce detailed written specifications for the system in the form of the manual, which leaves no ambiguities about any part of the system and completely specifies the external spcifications of the system i.e. what the user sees.
When designing a new kind of system, a team should factor in the fact that they will have to throw away the first system that is built since this first system will teach them how to build the system. The system will then be completely redesigned using the newly acquired insights during building of the first system. This second system will be smarter and should be the one delivered to the customer.
Every project manager must create a roadmap in the form of formal documents which specifies milestones precisely and things like who is going to do what and when and at what cost.
In order to avoid disaster, all the teams working on a project, such as the architecture and implementation teams, should stay in contact with each other in as many ways as possible and not guess or assume anything about the other. Ask whenever there's a doubt. NEVER assume anything.
Code Freeze and System Versioning:
No customer ever fully knows what she wants from the system she wants you to build. As the system begins to come to life, and the customer interacts with it, he understands more and more what he really wants from the system and consequently asks for changes. These changes should of course be accomodated but only upto a certain date, after which the code is frozen. All requests for more changes will have to wait until the NEXT version of the system. If you keep making changes to the system endlessly, it may NEVER get finished.
Every team should have a designated tool maker who makes tools for the entire team, instead of all individuals developing and using their private tools that no one else understands.
No silver bullet:
There is no single strategy, technique or trick that will exponentially raise the productivity of programmers.
The references contained in the book are all obsolete and ununderstandable without background research. Considering this is a new edition, it really lacks footnotes explaining about all the systems mentionned, their size, their importance at the time etc. The author mentions those systems as if everyone knew what they were and did.
One of other completely obsolete comments include the phrase "we had available a computer-driven text-editing software and this proved invaluable". Although, at the time, it might have proved very useful, word processors have long become a commodity, so those kind of claims make the whole matter laughtable today.
Not to mention the very boring writting style.
I wouldn't recommend this book to anyone.
To me, the book suffers from two major problems. For one, it is very outdated, and this 'anniversary edition' updates absolutely nothing from the original printing. For a book that is now 40 years old in a sector as fast-moving as software, this is understandable, but I found it puzzling Brooks decided to simply leave the whole script intact in this 1995 re-issue. Worse, the book is consistently described as 'timeless', a word that I feel could not be further from the truth. I will not go into specifics because other reviewers have already effectively described the anachronisms (such as each programmer having a secretary), but I retain the opinion that most of the content in the book is now outdated. Whether this is because the lessons of Brooks have been effectively woven into current best-practices or if the information is simply irrelevant now I cannot say.
Additionally, the parts that Brooks does decide to update are questionable. The book itself is 19 chapters; 1-17 are things that have been re-prints of essays from then- 10-20 years ago, and 18 is simply a summary of the book that asks "is this part of the book actually true or not?". This chapter in particular was one that I could not understand. How is it that after 20 years, we are no closer to finding out if any of the information that is put forth is actually true? And why even include such a chapter, a full 20 years after-the-fact? Only in the final chapter are we updated on Brooks's thoughts. I did not find this chapter to be any more illuminating than the rest of the book.
Another issue I perceived is that Brooks seems to be exceptionally long-winded in getting his point across. True, this is a problem for many books and does not disqualify a text from being valuable. Still, one would expect a more exacting tone from a book that is so frequently lauded as the 'most important' about software process.
The one part that I did find to be interesting and thought-provoking was the essay, No Silver Bullet. The separation of accidental and essential complexity is an intriguing one, even though I disagree with the author's conclusions on that specific point. In my own work, I still think that the vast majority of my time is implementing and verifying that my solution (in code) is correct. If I could think of a solution and immediately have code that corresponds to it, I do think that my effectiveness would increase tremendously. Regardless, the topic is an interesting one that surely does provoke the 'spirited discussion' that Brooks speaks of in the preface.
All in all, my suggestion to prospective readers would be to skip the book entirely (possibly reading a summary, if they must know what the main points are) and instead read No Silver Bullet, freely available online. You will gain just as much value but save at least 5 hours.
Most recent customer reviews
This book seems pretty old, but "has million 5stars scores".Read more