
Lessons from IBM's OS/360: why adding people to a late software project slows it.
Why adding people to a late software project makes it later.
Brooks managed the development of IBM's OS/360, one of the largest software projects of the 1960s, and wrote these essays about why it went as it did. The central proposition, now called Brooks' law, is that adding manpower to a late software project makes it later, because the new people must be trained by the existing ones and because communication paths grow as the square of team size.
The conceptual integrity argument is the book's other main contribution. Brooks holds that a system must proceed from a single mind or a small number of agreeing minds, that consistency of design matters more than the sum of good individual ideas, and that this requires separating architecture from implementation. He advocates the surgical team structure, in which one person does the design and others support.
Other essays cover the second system effect, in which an architect's second project accumulates all the features omitted from the first and becomes bloated; the argument that a programmer should plan to throw the first version away because they will anyway; the observation that scheduling is where most projects fail and that estimates are compressed by the desire to meet a date; and the recommendation to document design decisions formally.
The twentieth anniversary edition adds No Silver Bullet, in which Brooks argues that no single development produces an order of magnitude improvement in software productivity, because the essential difficulty is the complexity of the problem rather than the accidental difficulty of the tools. The examples are from 1960s mainframe development and much of the technical context is gone. Brooks himself retracted some positions, including on the surgical team. The law about late projects and the conceptual integrity argument remain accurate.
Anyone managing software projects who wants the original statement of why adding people fails and why design consistency matters more than individual quality.
“Arguably the only classic book in our field. If you haven't read it, shame on you.”
Chosen by shared topics, the entries that hold them, and the people who recommended both.
Managing people, teams and projects for an effective organisation.
“If you've ever seen the performance of an all-star sports team suffer due to poor coaching, you'll appreciate this book. It doesn't matter how many "coding superstars" you've got when none of them can talk to each other, or agree on anything. No developer, however talented, can work effectively when constantly being barraged with minor interruptions.” — Jeff Atwood
Source: Recommended Reading for Developers — Coding Horror
Recommended by: Jeff Atwood, Drew Houston, Marc Andreessen
How to plan and run software development to keep schedules under control.
Recommended by: Mohnish Pabrai
How to lead a company through layoffs, near-death crises and the decision to sell.
“…books I've recommended, highlighted to death, or forced on friends.” — Andrew Wilkinson
Source: Andrew Wilkinson's Bookshelf, neverenough.com
Recommended by: Andrew Wilkinson, Balaji S. Srinivasan and 34 others
Essays on software development from a popular programming blog.
Recommended by: Ev Williams
How to find, interview and hire good software programmers.
Recommended by: Ev Williams