What Is Bus Factor?
The bus factor of a project is the number of people who would have to leave — colloquially, “be hit by a bus” — before the project stalls because the knowledge needed to maintain it is gone.
How it is estimated
A low bus factor shows up in the history: parts of the code with a single author, files only ever reviewed by one person, and large areas last touched long ago by someone who has since moved on.
A bus factor of one means a single person holds critical, undocumented knowledge. Key-person risk is the same idea stated from a management point of view.
Why it matters
It is a planning input for retention, for onboarding priorities, and for technical due diligence — an acquirer wants to know how much of the value walks out if one engineer leaves.
You reduce it by spreading review, writing down the reasoning behind the code, and pairing people into the areas only one person understands.
Common questions
What is bus factor?
It is the number of team members who would have to leave before a project can no longer be maintained, because the knowledge to keep it running would be gone with them.
How do you calculate bus factor?
Look at authorship and review concentration in the git history: count how many people have meaningful knowledge of each critical area, and take the smallest such count as the project's bus factor.
How do you reduce key-person risk?
Spread code review across more people, document why the code is built the way it is, and deliberately pair engineers into the areas only one person currently understands.
Related
- Bus factor & key person risk — Know what you lose before someone quits. Mapnostics reads your git history to show who really owns each part of your codebase, and exactly what knowledge walks out the door if they leave.
- Developer onboarding — Cut developer onboarding from months to days. Mapnostics auto-generates a reading guide from your code and its history: architecture, entry points, a ranked learning path, change recipes and troubleshooting playbooks.
- Code ownership — glossary
- Technical due diligence (software) — glossary
See it in your own codebase.
Analyze my codebase →No credit card required · Free tier available