By: Frederick P. Brooks Jr.
Publisher: Addison-Wesley Professional
Pub. Date: August 02, 1995
Chapter 18 : Propositions of the Mythical Man-Month: True or False?
In this chapter, Brooks briefly reviews the main points for each chapter and adds a few annotations here and there.
Overall I've already written about everything here, so I'll make comments in my discussion section.
Chapter 19 : The Mythical Man-Month after 20 Years.
Brooks asks the question, "Why has Mythical Month persisted," and continued to sell after 30 years (40 years now). He claims that its longevity is attributable to the fact that Mythical Man Month is primarily concerned with team management and development and that many of the dilemmas addressed are sociological issues whereas the technology is merely a stage the issues play out on.
Brooks goes on to list portions of the book that are still true today:
The Central Argument: Conceptual Integrity and the Architect - Conceptual integrity is needed for productively deliver quality software products and an architect is needed to ensure that integrity.
The Second-system effect: Featuritis and Frequency-Guessing - Programs made to be general can suffer from "featuritis" (or feature creep) that lowers overall quality and consideration should be taken to avoid it. Brooks recommends guessing at frequencies of use for different functions and features.
Next, Brooks discusses several large changes in the industry since the book was first written:
The Triumph of the WIMP Interface -
WIMP stands for Windows, Icons, Menus, Pointers. Brooks points out this as an outstanding example of understanding the concept of the system and designing according to the concept. The WIMP concept was built of the metaphor of the work desktop and what operations it needed. Cut, paste, copy, type, use of hands, nouns and commands, etc... The WIMP interface also provided a way to cater to novice users and power users by allowing more efficient "power commands" (via keyboard) to be discovered with the mouse menus. Brooks also makes a bold prediction that voice navigation will replace the WIMP paradigm.

Brooks goes on to rescind his statement that managers should plan to "thrown one away." He does this because he had based the statement on the assumption that development would proceed along a waterfall development methodology where feedback and illumination into the inconsistencies in the system would occur when one was built already. Instead, under an incremental model, throwing a system away is unnecessary because early feedback occurs early and inconsistencies revealed in early prototypes and releases.
Brooks admits that he was wrong in disagreeing with Parnas' ideas to conceal the inner workings of modules on the basis that modularization allows higher level conceptualization of the design of the program and can even lead to increased code reuse.
Brooks provides some data found since the original publication that indicates that the man-month is indeed mythical and is encouraged that the industry is looking toward improving the people and social institutions rather than the tools to increase productivity.
Next Brooks observes the largest change: The microcomputer revolution that brought computing to the common man for cheap and empowers them to both be creative and provide demand incentives to quality generalized software.
Brooks goes on to note that OS systems can now be listed on two hands and that reuse has been facilitated by "metaprogramming" where third party developers provide the flexibility for individual programs by programming additional functionality. Brooks claims that metaprogramming directly addresses the essential difficulties of software engineering.
Brooks closes by claiming that software engineering (if it should be called that) is still in its infancy and that perhaps more unifying concepts and theories will be developed that will pull it out of the tar pit.
Discussion :
The last chapter that addresses the changes is an essential addition for the modern reader and unifies the book quite nicely.
Brooks description of featuritis complements Coopers description of feature creep but it seems that they recommend different reasons for why it occurs. Brooks also resembles Brooks (or perhaps its the other way around) in that they both call for a position in the team that emphasizes design before coding. I suspect Brooks has read his Mythical Man Month...
Brooks description of the triumph of "WIMP" is slightly amusing since I have personally have grown up in a world where that is all that has existed (mostly). It is difficult to imagine doing "desktop work" that consists of cutting and pasting of actual physical documents and honestly, it's a bit eye opening and I'm glad I live in the age that I do. I brought up that last point to my girlfriend who was with me at the time and asked her to imagine copying and pasting documents and she asked, "What do you mean," and "people actually did that?!"
Although it's obvious the terms came from using paper, that realization just doesn't hit most people and it really is a sign of how the times have changed and how people think about the objects they use on a day to day basis (that is to say, almost none).
It is also exciting to note the change brought about by the microcomputer revolution, and once again, I'm grateful for the time I live and study computer science in.

