liveBook · Manning

Bus factor

Bus factor is the minimum number of key contributors whose unavailability would seriously impair a project or make essential work difficult to continue or maintain.

How 2 Manning books explain it

Machine Learning System Design

Bus factor is the number of key contributors whose loss could prevent a project or system from continuing effectively.

How it is used
Guides ownership and maintenance decisions by exposing how dependent a project is on particular contributors.
How deep it goes
Defines a count-based risk metric, explains its efficiency-redundancy tradeoff, and qualifies it with partial knowledge and contextual judgment.
Examples
Uses bus-factor values of 1 and 10,000, plus reviews, pairing, open hours, and documentation as risk-management examples.
What you can do after
Diagnose ownership fragility, calculate a project bus factor, and select knowledge-sharing or staffing responses.

Read how Machine Learning System Design explains bus factor →

"Looks Good to Me"

The minimum number of knowledgeable team members who would have to become unavailable before a project stalls because of insufficient knowledge.

How it is used
Evaluates a team’s dependence on specific developers and motivates knowledge-sharing practices.
How deep it goes
Defines the risk and recommends several knowledge-sharing practices without providing a measurement formula or checklist.
Examples
Uses code reviews, team meetings, informal discussions, and pair-programming sessions as knowledge-transfer examples.
What you can do after
Apply it through code reviews and shared-development practices to build a more resilient, competent, and cohesive team.

Read how "Looks Good to Me" explains bus factor →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.