Quantifying and mitigating turnover-induced knowledge loss: case studies of chrome and a project at avaya
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
The utility of source code, as of other knowledge artifacts, is predicated on the existence of individuals skilled enough to derive value by using or improving it. Developers leaving a software project deprive the project of the knowledge of the decisions they have made. Previous research shows that the survivors and newcomers maintaining abandoned code have reduced productivity and are more likely to make mistakes. We focus on quantifying the extent of abandoned source files and adapt methods from financial risk analysis to assess the susceptibility of the project to developer turnover. In particular, we measure the historical loss distribution and find (1) that projects are susceptible to losses that are more than three times larger than the expected loss. Using historical simulations we find (2) that projects are susceptible to large losses that are over five times larger than the expected loss. We use Monte Carlo simulations of disaster loss scenarios and find (3) that simplistic estimates of the 'truck factor' exaggerate the potential for loss. To mitigate loss from developer turnover, we modify Cataldo et al.'s coordination requirements matrices. We find (4) that we can recommend the correct successor 34% to 48% of the time. We also find that having successors reduces the expected loss by as much as 15%. Our approach helps large projects assess the risk of turnover thereby making risk more transparent and manageable.
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
Joseph, D., Ng, K.-Y., Koh, C., & Ang, S. (2007) · MIS Quarterly · doi:10.2307/25148807 · Cited by 468 · cited 1×
“Developer turnover has a wide range of reasons, including job dissatisfaction from boredom or conflict, alternative job opportunities, and personal issues [17].”
Background
Cited by
Measuring Program Comprehension: A Large-Scale Field Study with Professionals
Xia, X., Bao, L., Lo, D., Xing, Z., Hassan, A. E., & Li, S. (2018) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2734091 · Cited by 326
Towards a Theory of Software Developer Job Satisfaction and Perceived Productivity
Storey, M.-A., Zimmermann, T., Bird, C., Czerwonka, J., Murphy, B., & Kalliamvakou, E. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2944354 · Cited by 90
“Retaining talent is especially important because high turnover introduces challenges with software quality when important knowledge is lost [3], [4].”
BackgroundTurnover-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
Helwig, M. (2026) · arXiv · doi:10.48550/arxiv.2609.05510
“Finally, the pre-AI software-engineering literature stated our problem first: knowledge loss under developer turnover, measured and priced [Rigby 2016; Robillard 2021]; documentation that goes stale silently [OutdatedDocs 2023]; domain knowledge thinly spread as a root cause of failure [Curtis…”
Metadata
- Authors
- Rigby, P. C., Zhu, Y. C., Donadelli, S. M., & Mockus, A.
- Venue
- Proceedings of the 38th International Conference on Software Engineering
- Publisher
- ACM
- Published
- 2016-05-14
- Pages
- 1006-1016
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W2360973814
- Cited by
- 76
- References
- 1
- FWCI
- 8.26
- Type
- conference paper
- Language
- en
- Open access
- closed
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Quantifying and mitigating turnover-induced knowledge loss: case studies of chrome and a project at avaya. https://app.cochat.ai/papers/10.1145/2884781.2884851
- The paper
- Rigby, P. C., Zhu, Y. C., Donadelli, S. M., & Mockus, A. (2016). Quantifying and mitigating turnover-induced knowledge loss: case studies of chrome and a project at avaya. Proceedings of the 38th International Conference on Software Engineering. https://doi.org/10.1145/2884781.2884851
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.