Succession: Measuring transfer of code and developer productivity
The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
Code ownership transfer or succession is a crucial ingredient in open source code reuse and in offshoring projects. Measuring succession can help understand factors that affect the success of such transfers and suggest ways to make them more efficient. We propose and evaluate several methods to measure succession based on the chronology and traces of developer activities. Using ten instances of offshoring succession identified through interviews, we find that the best succession measure can accurately pinpoint the most likely mentors. We model the productivity ratio of more than 1000 developer pairs involved in the succession to test conjectures formulated using the organizational socialization theory and find the ratio to decrease for instances of offshoring and for mentors who have worked primarily on a single project or have transferred ownership for their non-primary project code, thus supporting a theory-based conjectures and providing practical suggestions on how to improve succession.
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
Software Engineering Economics
Boehm, B. W. (2001) · Pioneers and Their Contributions to Software Engineering · doi:10.1007/978-3-642-48354-7_5 · Cited by 5,981
Community, joining, and specialization in open source software innovation: a case study
von Krogh, G., Spaeth, S., & Lakhani, K. R. (2003) · Research Policy · doi:10.1016/s0048-7333(03)00050-7 · Cited by 1,025 · cited 1×
“A detailed case study of what a volunteer has to go through to join two open-source projects is presented in [21].”
Background
Cited by
Don't touch my code!: examining the effects of ownership on software quality
Bird, C., Nagappan, N., Murphy, B., Gall, H., & Devanbu, P. (2011) · Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering · doi:10.1145/2025113.2025119 · Cited by 340
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
Who Will Stay in the FLOSS Community? Modeling Participant’s Initial Behavior
Zhou, M., & Mockus, A. (2015) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2014.2349496 · Cited by 141
“On the other hand, the performance of her peers is likely to affect her performance, for example, Mockus [40] found that more productive mentors lead to more productive followers.”
BackgroundSelf-citationThe Long Road Ahead: Ongoing Challenges in Contributing to Large OSS Organizations and What to Do
Guizani, M., Chatterjee, A., Trinkenreich, B., May, M. E., Noa-Guevara, G. J., Russell, L. J., Cuevas Zambrano, G. G., Izquierdo-Cortazar, D., Steinmacher, I., Gerosa, M. A., et al. (2021) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3479551 · Cited by 39
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
Metadata
- Authors
- Mockus, A.
- Venue
- 2009 IEEE 31st International Conference on Software Engineering
- Publisher
- IEEE
- Published
- 2009
- Pages
- 67-77
- OpenAlex
- W2116484544
- Cited by
- 61
- References
- 2
- FWCI
- 3.49
- 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: Succession: Measuring transfer of code and developer productivity. https://app.cochat.ai/papers/10.1109/icse.2009.5070509
- The paper
- Mockus, A. (2009). Succession: Measuring transfer of code and developer productivity. 2009 IEEE 31st International Conference on Software Engineering. https://doi.org/10.1109/icse.2009.5070509
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.