A novel approach for estimating Truck Factors
Open accessThe DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Truck Factor (TF) is a metric proposed by the agile community as a tool to identify concentration of knowledge in software development environments. It states the minimal number of developers that have to be hit by a truck (or quit) before a project is incapacitated. In other words, TF helps to measure how prepared is a project to deal with developer turnover. Despite its clear relevance, few studies explore this metric. Altogether there is no consensus about how to calculate it, and no supporting evidence backing estimates for systems in the wild. To mitigate both issues, we propose a novel (and automated) approach for estimating TF-values, which we execute against a corpus of 133 popular project in GitHub. We later survey developers as a means to assess the reliability of our results. Among others, we find that the majority of our target systems (65%) have TF ≤ 2. Surveying developers from 67 target systems provides confidence towards our estimates; in 84% of the valid answers we collect, developers agree or partially agree that the TF's authors are the main authors of their systems; in 53% we receive a positive or partially positive answer regarding our estimated truck factors.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
An exploratory study of the pull-based software development model
Gousios, G., Pinzger, M., & Deursen, A. V. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568260 · Cited by 628
Cited by
Widder, D. G., Zhen, D., Dabbish, L., & Herbsleb, J. (2023) · 2023 ACM Conference on Fairness, Accountability, and Transparency · doi:10.1145/3593013.3594012 · Cited by 94
The Signals that Potential Contributors Look for When Choosing Open-source Projects
Qiu, H. S., Li, Y. L., Padala, S., Sarma, A., & Vasilescu, B. (2019) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3359224 · Cited by 75
Turnover-induced knowledge loss in practice
Robillard, M. P. (2021) · Proceedings of the 29th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3468264.3473923 · Cited by 29
(2022) · doi:10.1145/3510003.3510121 · Cited by 19
Linåker, J., Link, G., & Lumbard, K. (2024) · Proceedings of the 18th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/3674805.3686667 · Cited by 14
Modeling interconnected social and technical risks in open source software ecosystems
Schueller, W., & Wachs, J. (2024) · Collective Intelligence · doi:10.1177/26339137241231912 · Cited by 13
Bhuiyan, M. H. M., Kumar, M. K. B., & Staicu, C.-A. (2026) · Proceedings of the 2026 IEEE/ACM 48th International Conference on Software Engineering · doi:10.1145/3744916.3787766 · Cited by 5
Metadata
- Authors
- Avelino, G., Passos, L., Hora, A., & Valente, M. T.
- Venue
- 2016 IEEE 24th International Conference on Program Comprehension (ICPC)
- Publisher
- IEEE
- Published
- 2016-05
- Pages
- 1-10
- OpenAlex
- W2344103814
- Cited by
- 109
- References
- 1
- FWCI
- 7.98
- Type
- conference paper
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.