| Revision as of 00:35, 17 December 2001 editHannes Hirzel (talk | contribs)500 edits Added Frederick P. Brooks; attribute it as a "classic text" of "software engineering"← Previous edit | Revision as of 00:40, 17 December 2001 edit undoHannes Hirzel (talk | contribs)500 editsmNo edit summaryNext edit → | ||
| Line 1: | Line 1: | ||
| The Mythical Man-Month is a term used by in a book describing the unique problem of software development on correction of ]. It makes special mention of the fact that unlike other engineering problems when you fall behind schedule you can't just add people to the project and expect the extra hands to resolve the problem. | The Mythical Man-Month is a term used by ] in a book describing the unique problem of software development on correction of ]. It makes special mention of the fact that unlike other engineering problems when you fall behind schedule you can't just add people to the project and expect the extra hands to resolve the problem. | ||
| Line 7: | Line 7: | ||
| The book can be considered a classic text of ]. It was republished virtually unchanged (just an addition of a chapter) after |
The book can be considered a classic text of ]. It was republished virtually unchanged (just an addition of a chapter) after 20 years. | ||
Revision as of 00:40, 17 December 2001
The Mythical Man-Month is a term used by Frederick P. Brooks Jr in a book describing the unique problem of software development on correction of schedule slippage. It makes special mention of the fact that unlike other engineering problems when you fall behind schedule you can't just add people to the project and expect the extra hands to resolve the problem.
This is largely due to the idea that while a laborer can be added to the digging of a hole, in software development everyone’s idea, not only of what the hole is, but also the best way to dig it can vary widely and dramatically, leading to the idea that the addition of personnel to a development team will actually cause the schedule to slip more as they are made aware of the particulars of this 'hole' and the method being used by the existing team to 'dig' it.
The book can be considered a classic text of software engineering. It was republished virtually unchanged (just an addition of a chapter) after 20 years.