The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) Frederick P. Brooks
Publisher: Addison-Wesley Professional

In the 20th anniversary edition, Brooks reflects on how the articles have aged and comments on other developments since the original publication date. It is classic book, written in 1975 but still very relevant. Available: http://www.pearsonhighered.com/educator/product/Mythical-ManMonth-The-Essays-on-Software-Engineering-Anniversary-Edition/9780201835953.page. Computer scientist Frederick P. This is the inaugural edition of Code Reads, a weekly discussion of some of the central essays, documents and texts in the history of software. This week we're talking about Frederick Brooks's . One note: The current edition of The Mythical Man -Month, called the “Anniversary Edition” (Addison Wesley brought it out in 1995 to mark the book's 20-year milestone), includes the full original text and four additional chapters. The Mythical Man-Month Essays on Software Engineering. I will start with classic book of software engineering – The Mythical Man-Month: Essays on Software Engineering first which was first published in 1975 by Fred Brooks. Some important points from the book * How does a project get to be a year late? In the 2nd chapter that carries the same title as the book, Brooks argues that the man-month is a myth and that man-power cannot be directly interchanged for time as many managers in that time (and still today) assume. He thus states Brook's Law, that adding Co., August 1995. The Mythical Man-Month: Essays on Software Engineering by Frederick P. This article is the namesake of the book and vies with No Silver Bullet as the most well-known of Brooks' work. One of the best books on project management. Brooks joined the Computer Science faculty at the University of North Carolina where in 1975 he penned “The Mythical Man-Month: Essays on Software Engineering†in which he describes the This book is undeniably the most widely read text on the subject of software project management and, although some of the examples are dated, many of the lessons remain highly relevant today – and unfortunately still often unheeded. The short summary is that software projects are often late because, as an industry, we don't do a good job of No Silver Bullet – Essence and Accident in Software Engineering.