money & economicsWikipedia

Adding people to a late software project makes it later, a law from 1975

the gist

Brooks's law says that adding manpower to a late software project makes it later. Fred Brooks coined the idea in his 1975 book The Mythical Man-Month. New people need training, and the existing team must spend time explaining the work to them, which pulls productive hours away from the job. Communication also grows fast: a team of n people has n(n-1)/2 possible pairwise channels, so each extra member adds more coordination than the last. Brooks argued that under certain conditions a newcomer adds to the time needed rather than shortening it.

how it works

Coordination costs grow faster than headcount. Every new person must learn the codebase, and every existing member must share context with them. When a project is already behind schedule, these onboarding and communication costs can outweigh the extra labour, so the finish date moves later instead of earlier.

so what

The law is one of the most cited lessons in software engineering and explains why deadline crises often get worse when more developers are rushed in. It has shaped how teams plan, staff and split work into independent modules. It also applies to any complex collaborative project where coordination costs rise with headcount.

fun fact

Fred Brooks managed IBM's OS/360 operating system project, and the lessons from that effort fed directly into his book.

more on this

From Wikipedia, the free encyclopedia · text CC BY-SA 4.0