Published 1975. Key points about the book: • introduces Brooks’s Law: Adding manpower to a late software project makes it later. • discusses the concept of “man-month” as a flawed unit, emphasizing that software projects cannot be perfectly divided into independently parallel tasks. • draws on Brooks’s experience managing the IBM System/360 and OS/360 software development projects.