There is a moment every engineering leader recognizes. It arrives when someone says the words that should feel like good news but land like a verdict: "We are going to add three more developers to the team." You know what the others do not. Three more developers do not mean three times the output. They mean three times the meetings, the context to distribute, and the coordination overhead. This book is a collection of observations from nearly two decades of building software and managing teams, confirming that software project management is not a problem of methodology, but a problem of people.
This book offers a practical, honest, and unvarnished look at the real challenges of leading engineering teams. It covers the mathematics of team scaling, the psychology of estimation, the politics of code review, and the particular challenges of remote work. It is not a prescription for a single methodology, but a set of principles you can adapt to your own context. The chapters are intentionally short enough to read in a single sitting and dense enough to revisit, giving you a toolkit for navigating the complex, frustrating, and rewarding work of managing software projects.
Inside, you'll discover:
• Why adding people to a late project makes it later and how to manage team scaling
• How to practice "agile without the theater" and focus on outcomes over rituals
• The black art of estimation and how to separate forecasts from commitments
• The translation problem of technical debt and how to make it visible to business
• How to navigate code review politics and build a healthy review culture
• The manager's burden and how to transition from individual contributor to leader
• How to apply Conway's Law and when to break the rules for effective project management
The most important work you do as an engineering leader is not technical. It is about creating the conditions for people to do their best work. When you get the people part right, the technical part follows. This book is for the engineering leader who is in the middle of it, dealing with growing teams, unreasonable stakeholders, and a process that is not working. It will help you navigate the problems, because the work of managing software projects, for all its difficulties, is some of the most rewarding work there is.
