Goodreads helps you keep track of books you want to read.
Start by marking “The Mythical Man-Month: Essays on Software Engineering” as Want to Read:
The Mythical Man-Month: Essays on Software Engineering
Enlarge cover
Rate this book
Clear rating
Open Preview

The Mythical Man-Month: Essays on Software Engineering

4.05  ·  Rating details ·  10,306 ratings  ·  675 reviews

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 s

Kindle Edition, Anniversary Edition, 2nd edition, 336 pages
Published August 2nd 1995 by Addison-Wesley Professional (first published 1975)
More Details... Edit Details

Friend Reviews

To see what your friends thought of this book, please sign up.

Reader Q&A

To ask other readers questions about The Mythical Man-Month, please sign up.
Popular Answered Questions
Stavros Sachtouris You don't need to be experienced in anything to understand this book. To enjoy it, though, it might be necessary to be familiar with engineering or…moreYou don't need to be experienced in anything to understand this book. To enjoy it, though, it might be necessary to be familiar with engineering or project management. It doesn't have to be software or electrical engineering, any kind would do. IT people will enjoy it even more for its historical and anecdotal value.(less)

Community Reviews

Showing 1-30
Average rating 4.05  · 
Rating details
 ·  10,306 ratings  ·  675 reviews

More filters
Sort order
Start your review of The Mythical Man-Month: Essays on Software Engineering
In this classic book on the software development process, Fred Brooks demolishes several persistent myths. They never quite go away: every new generation just has to learn them over again.

The first and most dangerous of these myths is the belief that putting more people on a project means it'll be completed more quickly. Brooks includes one of the most brilliant graphs I've ever seen, plotting number of women against time required to produce a baby. Would you believe it: the graph is flat at ni
Since what I know about programming probably could be written on the back of a postcard and wouldn't be worth reading there's nothing worthwhile that I can say about the software engineering side of this collection of essays about software engineering.

Further Brooks was writing in the 60s, in part based on experience from the 50s, which I suppose means I'll be making some claim to wider applicability with regard to project management & people management and understanding the natu
Dec 05, 2015 rated it it was ok  ·  review of another edition
Except blatant sexism* it was a pretty good book. It's a series of experiences that you gradually pick up when you're working in the software industry. It's a little outdated, e.g. we don't have printed manuals anymore and we don't have to deal with the woes of constantly updating them, but a lot of wisdoms from this book are still valuable.

* the entire book never uses a female pronoun. ever. it makes it sound like engineers, managers, technical leads, clients are always only male. plus there's
David Bjelland
As far as I can tell, the core tenets of this book aren't really even up for dispute anymore. I don't mean to sound like the grumpy reader mentioned in the epilogue, complaining that the book offered "nothing I didn't know already know" (however experienced he might have been, I still doubt it), but whether from my limited experience in the industry first hand or second-hand through the various managers I've had over the years, the tenet that developers and time aren't interchangeable resources ...more
Pratul Kalia
Apr 03, 2016 rated it it was amazing  ·  review of another edition
I want to print many copies of this book.
I want to print many copies and roll them up.
I want to roll them up and take them to meetings with my clients.
I want to take them to meetings and hit them over the head repeatedly while screaming "more... than... 30... years... and you... still... don't... understand... anything... stop... making... me... write... bad... software...!"

Brian Yahn
The Mythical Man-Month starts of strong--with a solid mix of good humor, great story-telling, and even better analogies and metaphors. Most interesting, the claims Frederick Brooks made more than 40 years ago remain true today. But even so, the book has not aged well.

Chapters 5-8 and 9-15 seem wildly out of date. I give some reasoning below, but the gist is that the middle is mostly skippable. Worse is that the religious overtones get a little out of hand in this section. And to make it even
Nov 01, 2009 rated it really liked it  ·  review of another edition
Shelves: computer-books
I read this book originally in college and then re-read it after a couple years of coding professionally. While there are certainly some dated sections, such as the idea of having the analog of a surgical team to code, many of the suggestions have held against the test of time.

The two most popular are "no silver bullets" and "adding developers to a late project makes it later." The former is that no new technology/technique will make an order of magnitude difference in productivity over 10 year
Apr 10, 2017 rated it it was ok
I was underwhelmed with how badly this text has aged. The references, which made sense 15 years ago, no longer hold water, and the most-referenced-project is certainly no longer the way we write software nowadays. While the idea remains valid, I think people writing about this text are more relevant than the text itself, holding only historical value, at most.
May 09, 2019 is currently reading it
en bilinen kısmı unutmuşum:) “The bearing of a child takes nine months, no matter how many women are assigned. Many software tasks have this characteristic because of the sequential nature of debugging.”
Matt Diephouse
I'm really surprised that people still recommend this book. It's primarily concerned with very large scale software projects (i.e., an operating system), much of the "data" is anecdotal, and many of the assumptions are simply outdated. For instance, Brooks writes about (1) creating paper manuals with documentation about the system that get updated daily for the engineers, (2) strategies for time-allocation on centralized computers, and (3) about optimizing for compiled code size. Those simply ar ...more
Dec 06, 2018 rated it it was amazing  ·  review of another edition
I re-read this recently after recommending it to a colleague, mainly just for nostalgia and planning to read a few of the more popular essays, like "The Tar Pit." Instead I read the entire book again and still found it fresh and insightful, over 40 years since publication. The prose manages to be dense with ideas but brilliantly clear and often witty. Now as I read contemporary writing (blogs but even books), I deeply lament this lost art.

Aside from his bold statements, most famously
This is more of historical importance than a go-to book nowadays. Still, I'm glad to have read it.

I agree with the points made in these two reviews, especially the ones about the default male programmer and the overextended Christian viewpoint, which actually makes Brooks misstate one of his examples.

Still, I loved the positive and realistic message of "There is no royal road, but there is a road." I can stand behind both parts of this one.
Aug 07, 2012 rated it really liked it  ·  review of another edition
Interesting book with a pretty narrow focus, a collection of essays on the management and planning of good software engineering. The author instilled the mistakes and successes of his work on the IBM 360 Operating System in the 70s, and most of what he found still applies today. For example, wisdom like: more programmers make a project only late, and if you add programmers to an already late project, results will arrive even later. Have an architect and a manager, hopefully in two different pers ...more
James Oden
Oct 03, 2015 rated it it was ok  ·  review of another edition
Shelves: computer
Many times when I read a book that is dated, its pearls of wisdom are still there in clear view to be harvested and made use of. I can't say the same thing about the Mythical Man Month. I will grant that Brook's Law still holds, and managers still today stumble over this one. However much of his advice fell flat in the face of the more recent agile development movement and still more recent devops movement. In the end he was still preaching a kind of waterfall type approach to development which ...more
May 12, 2011 rated it liked it  ·  review of another edition
Shelves: non-fiction

Dr. Brooks is the founder of our department, more than enough reason to read his book.

The recent extension to our department building was named after Dr. Brooks. Apparently the money for the building came as an anonymous donation from an alumnus, on the condition that it be named after Dr. Brooks. That is the kind of respect he has won from several people.
Apr 18, 2010 rated it it was amazing  ·  review of another edition

* Estimating software project completion time is really hard. (Requirements change, software is intangible and it has to fit with idiosyncrasies of human systems)

* Aristocracy in managing projects is better. There should be one final decision maker. Metaphor is a surgical team.

* Cost of coordination and communication within large teams is often ignored. This causes poor estimation.

* If a project is delayed - rescheduling or reducing scope is recommended. Addin
Jan 31, 2016 rated it liked it
Fascinating series of essays about building software and managing teams. Some bits really resonated, especially about the craft of software engineering. Brooks said that the hardest part about learning to program is adjusting to the necessity of perfection, which I think is still true today. He also had the most apt description of what it feels like to actually write code, and the differences between the essential work of building software and the "accidental" work imposed by poor tools, process ...more
Senthil Kumaran
This is a master piece of software engineering. Many people have read this one because this one is an extremely approachable account. When I read this book in 2007, I felt how much of value this one book brought which was written more than 20 years ago brought even then. Since then, I have heard many people talk and swear by this book. I have one gripe against the readers and people who talk about this. They use this book to support their stances and most often these people do not possess the ki ...more
Jan 02, 2009 rated it it was amazing  ·  review of another edition
I have read it as part of my PhD, since it's part of the classical books of software engineering. Yet the book tackles very important issues not only about management but how people interact during software development. I've recognised myself in many situations described by the author (even that I'm not part of a software development team).
One might wonder, as I did, how many of the concepts explained by the author apply to current technology of the 21st century, but the author tackles tha
May 14, 2016 rated it it was amazing  ·  review of another edition
Everybody should read this book, not just programmers or project managers. It's easy and fun. There are 9 chapters, but you only need to read 3 of them. You'll know which ones. When he starts slinging equations, skip over those parts. He uses cooking metaphors where most software books use building construction metaphors. The unconscious gender bias, typical of the time, is almost funny. He keeps saying how many "men" does it take to do a project.

I'm frequently surprised at how many
Nov 07, 2011 rated it really liked it  ·  review of another edition
Shelves: tech-books
Even for an inexperienced undergraduate student like me, this book made a lasting impression and left me pondering on the various human dynamics involved in software engineering. Definitely a must-read.

Warning: It does get a little dry at times, and most of the examples are very outdated,but the principles explained are timeless.
John Mehrman
Sep 12, 2017 rated it it was amazing  ·  review of another edition
Originally written in 1975, prior to the PC explosion in the mid-1980s, Brooks book is still relevant today. The same systems management "rules-of-thumb" and potential pitfalls still exist in largely the same form. Many of his bigger lessons expand beyond just software development and apply to program management as a whole. A must read for anyone in that develops complex systems.
May 28, 2017 rated it it was amazing  ·  review of another edition
I just leave my rating at here and dont say anyfuckinthing.
Thomas Dietert
May 02, 2019 rated it it was amazing  ·  review of another edition
In the context of this history of software engineering and management best practices for effectively building software systems and managing all sizes of projects and teams, this book is invaluable. I recommend every software engineer who is interested in building software systems at a meta-level (technical/social systems that help you build software systems), or wants to gain insight into these processes. Remarkably, only the specific methods and tools mentioned have changed since this book was ...more
Amy Jones
So much of this book is quaint. The descriptions of documentation that needs to be printed out to be shared, computer systems that can barely run the programs that are being built...with all of the technical advances, you’d think we’d be further along in our understanding of how to build this stuff. O the contrary, teams still fall subject to the same issues that are described and the advice given is just as applicable.
Feb 10, 2018 rated it liked it
First part of the book is the original from 1975. Most of the general ideas listed by the author are interesting, but he's focusing on very large teams (developing operating systems, compilers etc) working with now very outdated technology, solving very different set of problems. Luckily, it was quite short. 2/5.

Second part of the book is a summary of the original book and reflections of the author after 20 years. This was much easier to read since thoughts from 1995 are more relatab
Feb 05, 2019 rated it it was amazing  ·  review of another edition
The best book I’ve read in software project management is from 1975.
Alison Rowland
Jan 19, 2018 rated it liked it
Obviously, this is a classic. However, it's so much a classic, that I think most of its ideas have already entered into modern software engineering practices. I ended up skimming a lot of this.
Apr 03, 2019 rated it it was amazing  ·  review of another edition
A very insightful book on how to approach software development. This book has few gems which stay with you for the result of your life.
Emil A Eklund
Oct 20, 2017 rated it really liked it  ·  review of another edition
Read it a long time ago and it really should be required reading for all eng-managers and pms.
« previous 1 3 4 5 6 7 8 9 next »

Readers also enjoyed

  • Peopleware: Productive Projects and Teams
  • The Pragmatic Programmer: From Journeyman to Master
  • Code Complete
  • Design Patterns: Elements of Reusable Object-Oriented Software
  • Refactoring: Improving the Design of Existing Code
  • Joel on Software
  • Clean Code: A Handbook of Agile Software Craftsmanship
  • Coders at Work: Reflections on the Craft of Programming
  • Working Effectively with Legacy Code
  • The Cathedral & the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary
  • Head First Design Patterns
  • The Clean Coder: A Code of Conduct for Professional Programmers
  • Hackers & Painters: Big Ideas from the Computer Age
  • Patterns of Enterprise Application Architecture
  • Programming Pearls
  • Domain-Driven Design: Tackling Complexity in the Heart of Software
  • Designing Data-Intensive Applications
  • Structure and Interpretation of Computer Programs (MIT Electrical Engineering and Computer Science)
See similar books…

Goodreads is hiring!

If you like books and love to build cool products, we may be looking for you.
Learn more »
“As time passes, the system becomes less and less well-ordered. Sooner or later the fixing cease to gain any ground. Each forward step is matched by a backward one. Although in principle usable forever, the system has worn out as a base for progress. ...A brand-new, from-the-ground-up redesign is necessary.” 10 likes
“Adding manpower to a late software project, makes it later.” 10 likes
More quotes…