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

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)


The.Mythical.Man.Month.Essays.on.Software.Engineering.Anniversary.Edition.2nd.Edition..pdf
ISBN: 0201835959,9780201835953 | 322 pages | 9 Mb


Download The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)



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




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. “Brown writes with a winning combination of . The Mythical Man Month is an analysis by Fred Brooks of the problems involved in truly large software projects, using the example of the effort that IBM started in 1967 to build OS/360, the operating system that would go on to run most of the world's mainframe It's a great book, but it's dogma now, the conventional wisdom. The Mythical Man Month comes with a big reputation attached. The Mythical Man-Month: Essays on Software Engineering , Anniversary Edition (Peopleware: Productive Projects and Teams). If you attempt to measure less than 100% of the things .. I would recommend that you read: The Mythical Man-Month: Essays on Software Engineering written by Frederick P. A very thought provoking essay. I am looking for a book that can guide me. Definitely a MUST READ (cover-to-cover, not just Brooks Law) for serious software engineers. Book: The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition). Software engineering is not an exact science yet, mostly because it deals with people not machines. The books was originally written in 1975. Austin wrote an entire book on this subject called Measuring and Managing Performance in Organizations and came to the conclusion that unless you can measure 100% of something -- that is, every aspect of it -- then there is no point in measuring at all. The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition).