Brook's law

(redirected from Brooks' law)
Also found in: Wikipedia.

Brook's law

"Adding manpower to a late software project makes it later," coined by Fred Brooks, author of "The Mythical Man-Month," published in 1975. The extra human communications required to add another member to a programming team is considerably more than anyone ever expects. It naturally depends on the experience and sophistication of the programmers involved and the quality of available documentation. Nevertheless, no matter how much experience they have, the additional time discussing the assignment, commitments and technical details as well as evaluating the results becomes exponential as more people are added. See laws.
References in periodicals archive ?
These dynamic forces create the phenomenon often referred to as Brooks' Law, i.e., adding more people to a late software project makes it later [15].
This has produced three kinds of results: (1) Uncovered dysfunctional consequences of some currently adopted policies (e.g., in the scheduling area); (2) Provided support for managerial decision making (e.g., on the allocation of the quality assurance effort); and (3) provided insight into software project phenomena (e.g., 90% syndrome and Brooks' Law).
One oft-cited software project phenomenon is Brooks' Law, which states that adding manpower to a late software project makes it later [15].
We have studied Brooks' Law in the context of medium-size applications-type projects in [5].
The lesson of Brooks' Law would, of course, suggest that by adding new people to the late DE-A project, management actually delayed it further.
The behavior of an individual subsystem in isolation may be very different from its behavior when it interacts with other subsystems (e.g., the lesson of Brooks' Law).