The Mythical Man-Month

  title={The Mythical Man-Month},
  author={F. Brooks},
The book, The Mythical Man-Month, Addison-Wesley, 1975 (excerpted in Datamation, December 1974), gathers some of the published data about software engineering and mixes it with the assertion of a lot of personal opinions. In this presentation, the author will list some of the assertions and invite dispute or support from the audience. This is intended as a public discussion of the published book, not a regular paper. 
A Quiet Revolution in Requirements Management
Fred Brooks, already famous as the author of the Mythical Man-Month [Brooks 1987], wrote an article in the American journal Computer that destroyed the hope that the software crisis could be resolvedExpand
In the 25 years since The Mythical Man-Month what have we learned about project management?
This paper discusses Brooks' The Mythical Man-Month and compares the software project management advice given there with practices employed some 25 years later, to find out the state of today’s practice. Expand
Looking back at Postgres
This is a recollection of the UC Berkeley Postgres project, which was led by Mike Stonebraker from the mid-1980's to the early 1990's, and focuses on StonebraKER's design ideas and leadership. Expand
No Name : Notes on Reuse
In the beginning, so our myths and stories tell us, the programmer created the program from the eternal nothingness of the void. Programs these days are like any other assemblage. ProgrammingExpand
No name: just notes on software reuse
This essay acknowledges that programs these days are like any other assemblage, and suggests that in fact programming has always been about reuse, and claims that Components themselves are not the most important consideration for reuse. Expand
The Software Inferno
The Software Inferno is a tale that parallels The Inferno, Part One of The Divine Comedy written by Dante Alighieri in the early 1300s, describing a journey where "sinners against software" are encountered amidst their torment, within their assigned areas of eternal condemnation, and paying their penance. Expand
Sudoku: a little lesson in OOP
A series of designs for a Sudoku application that will lead introductory students through the all-important process of trial and error and why and how the initial mistakes could have been avoided are presented. Expand
A Mathematical Model for Explaining the Mythic Man-Month
  • Yingxu Wang
  • Computer Science
  • 2006 Canadian Conference on Electrical and Computer Engineering
  • 2006
A mathematical model of the mechanisms and behaviors of group workload inSoftware engineering is created, which reveals the transformability between labor and time in software engineering projects. Expand
The Tower of Babel did not fail
Fred Brooks' retelling of the biblical story of the Tower of Babel offers many insights into what makes building software difficult; but the story contains one more important lesson that people tend to miss: one cannot accomplish impossible goals. Expand
A capstone course for a computer information systems major
The current form and organization of Humboldt State University's CIS 492: Systems Design and Implementation, the capstone course for the Computer Information Systems (CIS) major, is described. Expand


Some cost contributors to large-scale programs
It is asked whether new tools can be developed to make the program manager more effective in planning and organizing his scarce resources of talented manpower and expensive computer time. Expand
The Paper describes the work that has been underway at the System Development Corporation for almost three years directed toward the advancement of the state-of-the-art of computer programming management. Expand
Modularity the key to system growth potential
General Electric's Apollo Systems has developed several information systems over the last eight years that have shown the efficiency of a modularized approach to retrieval system design. Expand
Subjective Time Estimates in Critical Path Planning--A Preliminary Analysis
A historical analysis of activity time estimates made by a number of contractors on a large-scale systems development project is conducted using two basic hypotheses. (1) Pre-activity time estimatingExpand
Automatic Data Processing