# Brooks' Law

> Software project management principle stating that adding manpower to a late project makes it later, highlighting the communication overhead and ramp-up time costs of expanding team size.

- **URL:** https://en.wikipedia.org/wiki/Brooks's_law
- **Category:** Practices
- **Tags:** Project Management, Team Management, Productivity
- **Updated:** 2026-03-14 18:50
- **Canonical page:** https://timetrack.ever.works/it/items/brooks-law

## Details

## Overview

Brooks' Law is an observation about software project management coined by Fred Brooks in his 1975 book "The Mythical Man-Month." It states:

> "Adding manpower to a late software project makes it later."

## Core Concept

### Communication Overhead

Each additional person brings fixed hours (typically 40/week), but communication paths expand exponentially:

**Communication Paths Formula:** n(n-1)/2

Where n = number of team members

**Examples:**
- 3 members: 3 communication paths
- 6 members: 15 communication paths  
- 9 members: 36 communication paths
- 12 members: 66 communication paths

At some point, each additional person becomes a net loss.

### Ramp-Up Time

Brooks identified that new team members:
- Require education about existing work
- Divert resources from productive workers
- Need time to become productive
- May introduce new errors during learning

## Supporting Research

### 2012 Empirical Analysis
Study of over 1,000 projects identified:
- **3-5 members**: Optimal team size for peak productivity
- **Up to 7 members**: Comparable performance
- **9+ members**: Significantly lower productivity

### 2015 CHAOS Report
Project success rates by size:
- **Small projects**: 61% success rate
- **Large projects**: 11% success rate
- **Grand projects**: 6% success rate

(Success = on time, on budget, meeting requirements)

## Implications for Time Tracking

### Planning Assumptions
- Man-months are not interchangeable units
- 9 women cannot have a baby in 1 month
- Adding people doesn't proportionally reduce time
- Must account for communication and training overhead

### Team Size Optimization
- Keep teams small (5-10 people)
- Limit WIP and parallelization
- Focus on finishing over starting
- Reduce handoffs and dependencies

### Resource Estimation
When estimating, factor in:
- Training time for new members
- Knowledge transfer overhead
- Increased coordination costs
- Potential productivity decrease initially

## When Brooks' Law Applies

### High Applicability
- Complex, interconnected systems
- Tasks requiring deep knowledge
- Late in project timeline
- High coordination requirements
- Knowledge-intensive work

### Lower Applicability
- Highly partitionable tasks
- Independent work streams
- Early in project (more time for ramp-up)
- Simple, repetitive tasks
- Well-documented systems

## Mitigation Strategies

### 1. Plan for Right Size from Start
- Start with optimal team size
- Avoid late additions
- Design for team capacity

### 2. Invest in Documentation
- Comprehensive onboarding materials
- Clear architecture documentation
- Runbooks and procedures
- Reduces ramp-up time

### 3. Partition Work Effectively
- Modular architecture
- Clear interfaces
- Minimal dependencies
- Enables parallel work

### 4. Limit Team Growth
- Add people only when necessary
- Consider alternatives first
- Assess true capacity gain

## Related Concepts

- **The Mythical Man-Month**: Brooks' seminal book
- **Two-Pizza Team Rule**: Amazon's small team principle
- **Conway's Law**: System design mirrors organization
- **Ringelmann Effect**: Individual productivity decreases in larger groups

## Modern Relevance

The principle remains highly relevant in:
- Agile methodologies (emphasis on small teams)
- DevOps practices (reduce handoffs)
- Microservices architecture (small, autonomous teams)
- Remote work (communication challenges amplified)

## Key Takeaways

1. More people ≠ faster completion
2. Communication overhead grows exponentially
3. Ramp-up time is significant
4. Small teams are often more effective
5. Plan team size carefully from project start
6. Late additions rarely help schedule

---

_This Markdown mirror is generated by Ever Works for AI agents. The canonical HTML page is at https://timetrack.ever.works/it/items/brooks-law._