The Mythical Man-Month: Essays on Software Engineering

Frederick P. Brooks Jr.

Pages

322

Year

1975

Difficulty

Moderate

Themes

software engineering, project planning, team scaling, Brooks's law, organizational complexity

The most influential book ever written about why large projects fail. First published in 1975 and still painfully relevant, Fred Brooks distills his experience managing the IBM System/360 project into a set of essays that reveal the fundamental reasons why adding people to a late project makes it later, and why the hardest problems in project management are not technical but human.

Why This One

Brooks’s law, that adding manpower to a late project makes it later, is one of those insights that sounds obvious once you hear it but that organizations violate constantly. The book explains why with surgical clarity. Communication overhead grows with every person added. New team members need training from the people who are already behind. The mythical “man-month,” the idea that people and time are interchangeable, is a fantasy that has sunk more projects than any technical challenge.

The Anniversary Edition (1995) adds four chapters that revisit the original arguments two decades later, including the famous “No Silver Bullet” essay. Brooks is remarkably honest about what he got right and what he got wrong. The writing is elegant and precise, the kind of book where nearly every chapter contains a sentence you want to underline.

What to Expect

A collection of essays, not a step-by-step guide. The examples come from mainframe-era software development, but the principles apply to any complex project. The prose is dense and rewarding. At 322 pages for the Anniversary Edition, it reads quickly because the ideas are so clearly expressed. Best for anyone who has experienced the chaos of a growing team and wants to understand the structural reasons behind it.

What to Read Next

Similar authors