Home▸Articles▸Computer Science

Brooks's Law: The Team-Scaling Paradox

A fundamental principle in software project management, Brooks’s Law highlights the challenges of adding more developers to a late software project.

mysimulator teamUpdated June 2026≈ 3 min read▶ Open the simulation

What is Brooks's Law

Brooks’s Law, named after Frederick P. Brooks Jr., states that adding more people to a late software project will make it later. This law captures the essence of how team scaling can introduce significant overhead and inefficiencies.

The core idea is that as teams grow, communication channels multiply exponentially, leading to bottlenecks and delays in information flow and decision-making.

Why It Happens

The primary reason for this phenomenon lies in the increased complexity of managing a larger team. More people mean more interactions, which can lead to misunderstandings and inefficiencies.

Additionally, new hires require time to ramp up on existing codebases and understand project requirements, further delaying progress.

live demo · related simulation● LIVE

Real-World Examples

Brooks’s Law is widely observed in software development projects. For instance, a large-scale open-source project might initially see rapid progress but slow down as more contributors join, leading to coordination issues and delays.

Another example can be seen in the agile methodology, where teams are encouraged to keep small and focused to maintain efficiency, highlighting the importance of Brooks’s Law.

Implications for Project Management

Understanding Brooks’s Law is crucial for effective project management. It emphasizes the need for careful team scaling and communication strategies to avoid delays.

Managers must balance the benefits of adding more resources with the potential costs of increased overhead, ensuring that projects remain on track.

Frequently asked questions

Does Brooks's Law apply only to software development?

No, while it is most famously observed in software development, Brooks’s Law can also apply to other collaborative fields such as research and engineering projects.

Can adding more resources ever speed up a project according to Brooks's Law?

Adding more resources might initially speed up a project but often results in increased communication overhead and newcomer ramp-up costs, potentially slowing down the overall progress.

How can teams mitigate the effects of Brooks’s Law?

Teams can mitigate these effects by improving communication tools, fostering a culture of collaboration, and ensuring that new hires are well-integrated into existing projects through effective mentoring programs.

Is there any way to avoid Brooks's Law altogether?

While it is challenging to completely avoid the effects of Brooks’s Law, proactive planning, clear communication, and strategic team management can help minimize its impact.

Try it live

Everything above runs in your browser — open Brooks's Law Team-Scaling Simulator and change the parameters while it is running. Nothing is installed, nothing is uploaded, the whole model lives in one tab.

▶ Open Brooks's Law Team-Scaling Simulator simulation

What did you find?

Add reproduction steps (optional)