Cover of The Mythical Man-Month

The Mythical Man-Month

by Frederick P. Brooks Jr.

Published 1995·348 pages
SoftwareDevelopmentEngineering Management
Find on Goodreads →

Why It Matters for Leaders

"The Mythical Man-Month" is crucial for Engineering Leaders as it addresses the challenges of project management and team dynamics, emphasizing that adding more personnel to a late project often exacerbates delays. An actionable takeaway is the importance of effective communication and realistic scheduling to prevent common pitfalls in software development.

Who Should Read This

Engineering leaders who need to push back on "just add more people" thinking. Classic insights on why software projects are late and what to do about it.

What's Inside

1. Mythical Man-Month: Challenges the assumption that time spent on a project correlates directly with the number of people working on it.

2. Communication Overhead: As team size increases, communication complexity grows, leading to inefficiencies.

3. Brooks's Law: "Adding manpower to a late software project makes it later."

4. Concept of Second-System Effect: New systems often become overly complex due to the inclusion of all desired features.

5. Estimation Techniques: Emphasizes the importance of realistic time and resource estimation in project management.

Share: