A Case Study of Onboarding in Software Teams: Tasks and Strategies

Abstract

Developers frequently move into new teams or environments across software companies. Their onboarding experience is correlated with productivity, job satisfaction, and other short-term and long-term outcomes. The majority of the onboarding process comprises engineering tasks such as fixing bugs or implementing small features. Nevertheless, we do not have a systematic view of how tasks influence onboarding. In this paper, we present a case study of Microsoft, where we interviewed 32 developers moving into a new team and 15 engineering managers onboarding a new developer into their team -to understand and characterize developers' onboarding experience and expectations in relation to the tasks performed by them while onboarding. We present how tasks interact with new developers through three representative themes: learning, confidence building, and socialization. We also discuss three onboarding strategies as inferred from the interviews that managers commonly use unknowingly, and discuss their pros and cons and offer situational recommendations. Furthermore, we triangulate our interview findings with a developer survey (N = 189) and a manager survey (N = 37) and find that survey results suggest that our findings are representative and our recommendations are actionable. Practitioners could use our findings to improve their onboarding processes, while researchers could find new research directions from this study to advance the understanding of developer onboarding. Our research instruments and anonymous data are available at https://zenodo.org/record/4455937#.YCOQCs_0lFd.

Reading to Write Code: An Experience Report of a Reverse Engineering and Modeling Course

“…In some ways, the guided exploration that results represents a typical onboarding experience [24]. In other ways, our approach deviates.…”

Collaborative Software Visualization for Program Comprehension

“…This allows developers to understand which portion of the source code acts in which use cases. The approach can then be used for taskoriented onboarding, where developers also face small tasks to comprehend the software [22], [24]. At any time, users can invite other developers for collaborative comprehension or their mentor and ask for help.…”

Gobiernos abiertos, ciudadanía que decide. Transformación digital del mecanismo de presupuestos participativos en Bogotá

“…Para la característica de Billetera Digital, se tuvieron en cuenta aplicaciones bancarias como Nequi, y portales que permiten transacciones monetarias y ofrecen un historial de compras y pagos como MercadoLibre. A esto se le sumó una serie de perspectivas pedagógicas desde el diseño y la pedagogía de escaneo de información, como las utilizadas en Duolingo o la presencia de material de apoyo y tutoriales bajo el concepto de la experiencia Onboarding [22] para primerizos o no frecuentes.…”