A Novel Approach for Estimating Truck Factors.¶
Avelino, G., Passos, L., Hora, A., & Valente, M. T. (2016). A Novel Approach for Estimating Truck Factors. Proceedings of the 24th IEEE International Conference on Program Comprehension (ICPC), 1-10.
Cited by¶
11 citations across 11 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Center Of Gravity
- Organisational change: the unspoken cultural keystone — a founder, the one engineer who owns the deploy pipeline, an unwritten norm — whose departure redirects the whole organisation.
This sourceDefines and measures the truck/bus factor — the minimal number of key developers whose departure incapacitates a project — quantifying key-person dependence and concentrated tacit knowledge (65% of 133 popular projects have a truck factor ≤ 2).
Supported in partVerified against the work's full text
The paper supports key-person dependence in software projects (low truck factor, knowledge silos) but not cultural keystones, founders, unwritten norms or organisation-wide redirection.
“If such knowledgeable personnel abandon the project, the sys- tem’s lifecycle is seriously compromised”
- Organisational change: the unspoken cultural keystone — a founder, the one engineer who owns the deploy pipeline, an unwritten norm — whose departure redirects the whole organisation.
Domain-specific¶
- Bus Factor
- These proxies systematically under-detect tacit assets — the knowledge in someone's head that no commit or runbook captures — which means the real bus factor is almost always lower than a surface audit suggests.
This sourceAn automated code-authorship-coverage heuristic for estimating truck factors in 133 GitHub systems, validated by surveying their developers.
Supported in partVerified against the work's full text
“we can conclude that code authorship is an effective proxy”
- These proxies systematically under-detect tacit assets — the knowledge in someone's head that no commit or runbook captures — which means the real bus factor is almost always lower than a surface audit suggests.
Mechanisms¶
- Cross-Training and Role Shadowing
- Its strength is that it attacks the most stubborn dependency of all — the single indispensable person — and lowers the bus factor, the number of people who could vanish before critical work stalls.
This sourceDocuments the single indispensable person; lowers the bus factor; the number of people who could vanish before critical work stalls.
- Its strength is that it attacks the most stubborn dependency of all — the single indispensable person — and lowers the bus factor, the number of people who could vanish before critical work stalls.
- Embedded Specialist Review Lane
- A real anchor names the fragility: the bus factor, the number of people who would have to be lost before a capability stalls; a bus factor of one is a classic single point of failure.
This sourceDefines truck or bus factor as the minimum number of key developers whose loss would incapacitate a project, making a value of one a single-person continuity risk.
- A real anchor names the fragility: the bus factor, the number of people who would have to be lost before a capability stalls; a bus factor of one is a classic single point of failure.
- Handoff Checklist
- Without the list, the most valuable things would have walked out with her — not the documented protocols, which anyone can find, but the bus-factor knowledge held in one person's head.
This sourceDefines truck factor as project-critical knowledge concentrated in so few developers that their departure could incapacitate the project.
- Without the list, the most valuable things would have walked out with her — not the documented protocols, which anyone can find, but the bus-factor knowledge held in one person's head.
- Knowledge Base Refresh
- It is the direct antidote to a dangerously low bus factor — the risk that essential know-how sits with one person.
This sourceDefines truck factor as a measure of concentrated project knowledge and vulnerability to developer turnover.
- It is the direct antidote to a dangerously low bus factor — the risk that essential know-how sits with one person.
- Role Rotation Pilot
- The network now knows its bus factor
This sourceDefines a truck factor of one as a project whose viability depends on a single key contributor and estimates which files concentrate that knowledge.
- The network now knows its bus factor
- Role-Substitution Rotation
- It directly attacks a low bus factor: the small number of people whose sudden absence would stall a critical function.
This sourceDefines truck factor as the small number of key developers whose departure would leave a project in serious trouble.
- It directly attacks a low bus factor: the small number of people whose sudden absence would stall a critical function.
- Specialist Queue
- Its failure mode is specialist scarcity turned bottleneck: the lane is real but under-capacitied, so it becomes the slowest, most fragile path in the system, and if all competence sits with one or two people
This sourceDefines truck factor as concentrated knowledge in very few developers that threatens project continuity if they leave.
- Its failure mode is specialist scarcity turned bottleneck: the lane is real but under-capacitied, so it becomes the slowest, most fragile path in the system, and if all competence sits with one or two people
- Succession and Stewardship Plan
- The number of people who would have to vanish before the institution stalls — its bus factor — is exactly what a good plan raises.
This sourceDefines the bus or truck factor as the number of key people whose loss would stall a project.
- The number of people who would have to vanish before the institution stalls — its bus factor — is exactly what a good plan raises.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 2 of 11 citations: 2 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:e7eb1eb78ab4 · see in the full table