ISBN-10:
0201835959
ISBN-13:
9780201835953
Pub. Date:
08/16/1995
Publisher:
Addison-Wesley
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition / Edition 2

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition / Edition 2

by Frederick P. Brooks Jr.
Current price is , Original price is $42.99. You

Temporarily Out of Stock Online

Please check back later for updated availability.

Overview

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 labor; 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.'

Product Details

ISBN-13: 9780201835953
Publisher: Addison-Wesley
Publication date: 08/16/1995
Edition description: Anniversary Edition
Pages: 336
Sales rank: 69,676
Product dimensions: 6.10(w) x 9.15(h) x 0.95(d)

About the Author

Frederick P. Brooks, Jr., was born in 1931 in Durham, NC. He received an A.B. summa cum laude in physics from Duke and a Ph.D. in computer science from Harvard, under Howard Aiken, the inventor of the early Harvard computers.

At Chapel Hill, Dr. Brooks founded the Department of Computer Science and chaired it from 1964 through 1984. He has served on the National Science Board and the Defense Science Board. His current teaching and research is in computer architecture, molecular graphics, and virtual environments.

He joined IBM, working in Poughkeepsie and Yorktown, NY, 1956-1965. He is best known as the 'father of the IBM System/360', having served as project manager for its development and later as manager of the Operating System/360 software project during its design phase. For this work he, Bob Evans, and Erick Block were awarded and received a National Medal of Technology in 1985.

Dr. Brooks and Dura Sweeney in 1957 patented a Stretch interrupt system for the IBM Stretch computer that introduced most features of today's interrupt systems. He coined the term computer architecture . His System/360 team first achieved strict compatibility, upward and downward, in a computer family. His early concern for word processing led to his selection of the 8-bit byte and the lowercase alphabet for the System/360, engineering of many new 8-bit input/output devices, and providing a character-string datatype in PL/I.

In 1964 he founded the Computer Science Department at the University of North Carolina at Chapel Hill and chaired it for 20 years. Currently, he is Kenan Professor of Computer Science. His principal research is in real-time, three-dimensional, computer graphics-'virtual reality.' His research has helped biochemists solve the structure of complex molecules and enabled architects to 'walk through' buildings still being designed. He is pioneering the use of force display to supplement visual graphics.

Brooks distilled the successes and failures of the development of Operating System/360 in The Mythical Man-Month: Essays in Software Engineering, (1975). He further examined software engineering in his well-known 1986 paper, 'No Silver Bullet.' He is just completing a two-volume research monograph, Computer Architecture, with Professor Gerrit Blaauw. Now, 20 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice within The Mythical Man-Month, Anniversary Edition.

Brooks has served on the National Science Board and the Defense Science Board. He is a member of the National Academy of Engineering and the American Academy of Arts and Sciences. He has received the the IEEE John von Neumann Medal, the IEEE Computer Society's McDowell and Computer Pioneer Awards, the ACM Allen Newell and Distinguished Service Awards, the AFIPS Harry Goode Award, and an honorary Doctor of Technical Science from ETH-Zürich.

Read an Excerpt

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.

Table of Contents

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. 0201835959T04062001

Preface

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.


Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition 3.8 out of 5 based on 0 ratings. 21 reviews.
RolfDobelli More than 1 year ago
This book is a classic for a reason. Every essay by Frederick P. Brooks Jr. addresses software engineering and proves invaluable for those interested in the history and processes of that field. getAbstract also recommends Brooks' book to anyone who plans or organizes major projects. The collection remains timely due to the clarity of his thought and the educated loveliness of his prose. When Brooks is writing about programming, he's never just writing about programming. He's writing about the complexities of life, and about how best to plan, organize and communicate the concepts you need to overcome those complexities. This 20th-anniversary edition contains new essays in which Brooks reflects on his earlier writing - especially his principles and predications - and responds to his critics. The result showcases a singular, markedly honest mind at work. To learn more about this book, go to the following web page: http://www.getabstract.com/summary/8771/the-mythical-man-month.html
JKCollins on LibraryThing More than 1 year ago
I found the essays informative, from a historical and theoretical perspective, but not a lot of help in how to improve management of projects. There are many far better books than this one for actual "how to" tips and tricks.
alspray on LibraryThing More than 1 year ago
A book about technology, first written in 1975 and yet still - astoundingly - relevant.Imagine reading along, mentally applying the lessons to your own experience when the author notes that great efficiencies would be gained if only everyone had a desktop computer... my god! This book is ancient (in terms of technology)!And that's what is both instructive and disturbing - the I.T. field is still struggling with the same issues they struggled with a quarter century ago.That aside, Brooks does a a fantastic job of discussing how software "is done", the contributions of each role on the team and how things get very complex very quickly as the size of the project scales up. His insights remain poignant and his credibility increases as many of his predictions from 1975 ring true today.And while Brooks does talk about ease of use and how important it is that the application meets the needs of the people who use it, he never mentions the role of the Usability Practitioner. Is this an oversight or an active decision or was there simply no such thing as a Usability Practitioner in 1975? I would have expected him to note the role in one of his many follow-up chapters.Speaking of which, my only critique is with the structure of the book. Brooks has returned over the years to add follow-up chapters such that its hard to distinguish what is the end of the original book and what was added later.Wisdom is a hard thing to come by. You gain it slowly by experiencing life yourself or maybe a little faster by learning from others experience. As someone working in the field of software development its incredibly helpful to be able to differentiate temporal issues from an issue that is simply innate to the work we do. I feel I'm all the wiser for the read and I wish Mythical Man Month were required reading for my colleagues
ivanlanin on LibraryThing More than 1 year ago
A great book for thought.
RobKohr on LibraryThing More than 1 year ago
The major important concept of the book is the downward curve in productivity per worker as additional employees are added to the project. The book goes through a lot to prove this and give some reasons for it (for example more permutations of communcation connections between employees).The down side is that there is just too much outdated material in this book to make it worth reading. If you fully grasp the above concepts, skip this book, otherwise you will be bored to tears. If you don't grasp these concepts, then read the book as it is the best place to start on the subject.
alienhard on LibraryThing More than 1 year ago
The book that said "nine women can't make a baby in a month": projects don't scale with warm bodies. Brilliant.
colinangusmackay on LibraryThing More than 1 year ago
While some may say this book is out dated there are still important lessons to be learned from it. I feel, however, that because the examples given to back up the arguments are now out of date it may make reading the book difficult for those who were not around at the time the original edition was published.
tjbond on LibraryThing More than 1 year ago
An excellent book on management and software development. It is remarkable how much Brooks gets right.
Miche11e on LibraryThing More than 1 year ago
I bought the 1982 edition from Abe books because I was too cheap to shell out $33 for the 2005 edition.It's a good book, but a bit dated. Many of the suggestions are now standard business practices and it is more specific to programming than is really necessary. I bought the book specifically because I was interested in using the concept "Plan to Throw One Away" at work.I laughed when the chapter started talking about the problems with scaling-up pilot chemical plants. I recall that lab VERY well. You build a pilot plant to prove that the process will work. You hope that when you scale it up, the reduced losses will make it efficient. I don't think the analogy is correct, but the lesson is a good one. Don't develop a new process without thorough testing, during which you'll probably have to throw the product away. Work the bugs out during the pilot, and then implement.
Anonymous More than 1 year ago
This is an excellent book for anyone looking to manage software projects or just to figure out where they fit in on their team. The book gives great examples of structuring both large and small teams and explains it all in simple, easy to understand processes. Written nearly 40 years it has had plenty of time to be analyzed, tested and critiqued only to show that it is just as great today as it was 40 years ago (if not better).
Anonymous More than 1 year ago
Glad to see this available in Nook.
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Ryan_the_Professor More than 1 year ago
The technical aspects are no long applicable, but the human side is still the same. It seems we humans don't change that much over time, unlike technology.