Enhanced descriptions from Syndetics:

Few books on software project management have been as influential and timeless as The Mythical Man-Month . With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system. Now, 20 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice, both for readers already familiar with his work and for readers discovering it for the first time.

The added chapters contain (1) a crisp condensation of all the propositions asserted in the original book, including Brooks' central argument in The Mythical Man-Month: that large programming projects suffer management problems different from small ones due to the division of lab∨ that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; (2) Brooks' view of these propositions a generation later; (3) a reprint of his classic 1986 paper "No Silver Bullet"; and (4) today's thoughts on the 1986 assertion, "There will be no silver bullet within ten years."

Table of contents provided by Syndetics

• 1 The Tar Pit
• 2 The Mythical Man-Month
• 3 The Surgical Team
• 4 Aristocracy, Democracy, and System Design
• 5 The Second-System Effect
• 6 Passing the Word
• 7 Why Did the Tower of Babel Fail?
• 8 Calling the Shot
• 9 Ten Pounds in a Five-Pound Sack
• 10 The Documentary Hypothesis
• 11 Plan to Throw One Away
• 12 Sharp Tools
• 13 The Whole and the Parts
• 14 Hatching a Castrophe
• 15 The Other Face
• 16 No Silver Bullet -- Essence and Accident
• 17 "No Silver Bullet" ReFired
• 18 Propositions of The Mythical Man-Month: True or False?
• 19 The Mythical Man-Month After 20 Years
• Epilogue
• Notes and references
• Index

Excerpt provided by Syndetics

To my surprise and delight,The Mythical Man-Monthcontinues 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 IEEEComputermagazine, 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 hasThe 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 ofThe 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. 0201835959P04062001 Excerpted from The Mythical Man-Month: Essays on Software Engineering by Frederick P. Brooks All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.

Reviews provided by Syndetics

CHOICE Review

This exciting and vital work is as valuable today as it was 20 years ago. Advances in the computer software industry, made possible by the increase in memory capacity and CPU power, make some of the original text sound old-fashioned, but the crux of the solution of the problem of software creation remains: a successful method of tackling large software development tasks is founded on the creative talent of one or two design leaders, the project management skills of a facilitator, and the fostering of a team atmosphere. The new chapters examine previous criticisms in an evenhanded manner and underscore the correctness of the earlier edition's conclusion that modular programming is essential to reducing development time. The controversial principle--that the designer of a module should be in ignorance of the other modules--is discussed, and the admission by Brooks that he has been persuaded to change his mind on this issue is an indication of his flexibility. Perhaps it is this generosity of spirit that makes this book such a fine learning experience. Undergraduate through professional. D. A. Dobbin Maine Maritime Academy