A project becomes fragile when one person holds the knowledge needed to keep it running. The bus factor measures how many key contributors could be lost before continuation becomes impossible. It makes ownership risk visible and frames a practical tradeoff: concentrated expertise improves efficiency, while shared knowledge provides redundancy. section 16.0 section 16.2
Use the metric to expose fragile ownership and choose proportionate responses:
- List the people accountable for each project or system area. section 16.2.3
- For each area, identify how many other people know it well enough to provide a replacement. section 16.2.3
- Treat the result as a risk signal, not a rigid label: knowledge exists in degrees and can be spread partially. section 16.2.3
- Reduce fragility through design and code reviews, pair programming, open knowledge-sharing hours, documentation, hiring, reassignment, or collaboration. section 16.2.3 section 16.3
Reading the number
A bus factor of 1 means losing one specific team member could put the project in serious trouble. A bus factor of 10,000 may indicate excessive redundancy for a small-scope project, although large groups with similar responsibilities can justify higher values. Interpret the number alongside project importance, budget, deadlines, expected turnover, team seniority, and technology exposure. section 16.2.3
