I still remember the first time I saw it happen with my own eyes. A project was three weeks behind schedule, and the engineering vice president announced that three new developers would be joining the team. Everyone in the room who had ever written production code before knew exactly what was coming. Six weeks later, the project was eight weeks behind where it needed to be. The vice president looked genuinely confused. He had done what anyone would do when a project needs to go faster. He added more people.
That scene has played out in thousands of companies across multiple decades. It was first described in 1975 by Frederick Brooks in his landmark collection of essays, The Mythical Man-Month. Brooks distilled the phenomenon into a single sentence: adding manpower to a late software project makes it later. This is a collection of essays about software project management, inspired by the structure and spirit of Brooks's original work.
Each chapter examines a specific aspect of the problem, from the mathematics of communication overhead to the psychology of team growth, from the politics of estimation to the implications of artificial intelligence on team dynamics. The essays are designed to be read in any order, though they build on each other thematically. The core argument is that software project management is not primarily a technical problem that can be solved with better tools. It is a human problem that requires understanding how people and organizations actually work.
Inside, you'll discover:
• The law that will not die and why adding people to late projects makes them later
• The mathematics of coordination and why team size matters
• The ramp-up tax and why new hires cost more than you expect
• The management incentive problem and how to fix it
• Estimation as a strategic skill, not a bureaucratic exercise
• The surgical team reborn for the AI era
• Conway's Law and the relationship between team structure and software architecture
The essays in this book draw on more than fifteen years of experience building software products and leading engineering teams across organizations ranging from five-person startups to publicly traded companies with thousands of engineers. Understanding these dynamics does not guarantee success, but it is far better than stumbling through the same mistakes that others have been making for half a century.
