13 min · 12 chaptersNarrated in your voice
Original summary · AI-drafted, human-published · added by Library
What it's about
Brooks argues, from his experience managing IBM's OS/360 operating system project, that large software projects fail not from lack of effort but from a mistaken model of how work scales. Adding people to a late project often makes it later, because communication overhead and task interdependence grow faster than raw output. The book reshaped how the software industry thinks about scheduling, team structure, and the irreducible complexity of large systems.
Reading plan
Pick a finish date and Genius lays out the days — the plan shows today's target and keeps you honest.
Read together
Start a circle and share the code — everyone sees everyone's honest place in the book. Accountability, not leaderboards.
Who it's for
- A software engineering manager who keeps missing deadlines and wants to know why adding staff isn't fixing it - A computer science student trying to understand why 'agile' and 'team structure' debates go back fifty years - Anyone leading a complex technical project who suspects their scheduling assumptions are the problem, not their people
What’s inside
- 1The Tar Pit1 min
Large software systems are hard for reasons built into the nature of software itself, not for reasons that better tools or more effort can dissolve.
- 2The Mythical Man-Month1 min
A man-month is a misleading unit of measure because it assumes people and time are interchangeable in ways that most software tasks do not allow.
- 3The Cost of Communication1 min
Team size increases coordination cost faster than it increases output, because the number of communication paths grows quadratically while people grow linearly.
- 4The Surgical Team1 min
Small teams organized around one lead designer produce more coherent and more efficient work than larger teams that share design authority equally.
- 5Conceptual Integrity1 min
A system is more useful and more reliable when its design reflects one coherent vision, even if that costs some efficiency in how the team is staffed.
- 6The Second-System Effect1 min
The system that follows a person's first successful design is at the greatest risk of being ruined by overconfidence and overreach.
- 7Making the Plan Visible1 min
A large project cannot be coordinated by good intentions alone; it needs written, shared, and constantly updated documents that make the state of the design and the schedule visible to everyone.
- 8How Schedules Actually Slip1 min
Projects rarely fall behind through one dramatic failure; they fall behind through many small, individually excusable delays that no one is positioned to notice or add up.
- 9No Silver Bullet1 min
No single tool, language, or methodology will produce an order-of-magnitude improvement in software productivity, because most of software's difficulty is essential rather than accidental.
About Frederick P. Brooks Jr.
Frederick P. Brooks Jr. managed IBM's System/360 hardware and OS/360 software projects in the 1960s, one of the largest and most troubled software efforts of its era. He later founded the computer science department at the University of North Carolina at Chapel Hill, where he taught for decades, drawing directly on his managerial failures and fixes to write this book.
What readers say
Read next
AccelerateNicole Forsgren, Jez Humble, and Gene KimSummary13 min
The Coming WaveMustafa SuleymanSummary12 min
HackersSteven LevySummary10 min
Weapons of Math DestructionCathy O'NeilSummary13 min
Where Wizards Stay Up LateKatie Hafner and Matthew LyonSummary10 min
Dealers of LightningMichael A. HiltzikSummary11 min