Browse the Knowledge Hub211 resources
The Mythical Man-Month: is it worth reading?
The 1975 essays that named Brooks law, and the most durable observations about why software projects run late.
We earn nothing from any link on this page. No affiliate links anywhere in this library.
- published
- 1995
- key ideas
- 3
- reading path
- 1
The Mythical Man-Month
Essays on Software Engineering
by Frederick P. Brooks Jr.
- Publisher
- Addison-Wesley
- Year
- 1995
- Edition
- Anniversary edition, adding the No Silver Bullet essay and a retrospective.
- ISBN
- 9780201835953
Useful when you are: Senior / lead, Manager
Verdict
Should you read it?
Read it if
You want the historical foundation of software project management, and to recognise how little the underlying problems have changed.
Skip it if
You want actionable current practice. The specifics describe 1960s mainframe development and are of historical interest only.
The argument
What it argues
Adding people to a late project makes it later, because the communication overhead of integrating them exceeds their contribution in the time available. Brooks law is the most quoted observation in software management and is routinely ignored.
The surrounding essays cover conceptual integrity in design, the second-system effect where an architect second project is over-engineered, and the distinction between essential and accidental complexity in the No Silver Bullet essay.
For a quality audience the relevant thread is that schedule pressure is the root of most quality compromise, and that the usual response to a late project makes both worse.
Key ideas
Ideas worth taking from it
- 01
Brooks's law
Adding people to a late software project makes it later. Nearly fifty years old and still being rediscovered every year by someone.
- 02
Essential and accidental complexity
Some complexity is inherent in the problem and some is an artefact of our tools. No Silver Bullet argues that only accidental complexity can be removed by better tooling, which sets a ceiling on what any new technology can deliver.
- 03
Conceptual integrity
A coherent design by few minds beats a feature-rich one by many. An argument for architectural authority that remains contested.
Criticism
What has dated, and what it gets wrong
Genuinely dated in everything except the observations about people, which is a narrow but valuable band. Brooks himself revisits and corrects several positions in the anniversary edition, which is more honest than most authors manage. Read the essays on Brooks law and No Silver Bullet and skip the implementation material.
Reading paths
On our reading paths
Leading a quality team
Book 2 of 4 · QA and engineering managers
Why adding people to a late project makes it later, and other lessons every planning meeting seems to relearn.
1. Peopleware- 2. The Mythical Man-Month (this book)
3. Team Topologies
4. The Manager's Path
Keep reading
What to read next
Reads well with
Reading about quality is cheaper than learning it in production.
QAble runs QA for products in BFSI, gaming, healthcare and SaaS, with engineers who have read these and argued about them. Start with a free QA audit.