Effective team onboarding in Agile software development: techniques and goals

I. INTRODUCTION AND BACKGROUND

• Team onboarding is the procedure by which new employees move from team outsiders to insiders; its duration may depend on the support provided and newcomer characteristics.The study focuses on optimizing that support for a given context.Source: §I · p. 1
• Poorly designed onboarding can cause newcomer anxiety and reduced team productivity; the study treats explicit techniques as a way to pursue desired onboarding goals.A planned set of techniques over a duration is termed an onboarding program design.Source: §I · p. 1
• The study asks practitioners about techniques they value and their perceived contributions to goals drawn from a literature review, using a Repertory Grid instrument.The goals are fixed by the researchers, while participants supply techniques and assess their relationships to goals.Source: §I · pp. 1–2
• The authors expect their goals and evidence-based technique-selection mechanism to support better-informed onboarding design and planning and broaden practitioner awareness of support options.They also expect these contributions to result in more effective onboarding, happier onboarders, and more productive teams.Source: §I · p. 2

II. RELATED RESEARCH

• Prior software-team onboarding studies include Google and Microsoft examples; their findings on team support, socialization, mentoring, and pair programming align with techniques valued in this study.The cited studies examined Google’s onboarding process for new graduates and Microsoft’s onboarding of new graduates.Source: §II · p. 2
• Bauer and Erdogan model onboarding as adjustment in role clarity, self-efficacy, insider acceptance, and cultural knowledge; this study identifies more granular goals for Agile software teams and investigates techniques to support them.Source: §II · p. 2

A. Research objectives, aims and questions

• The study’s objective is insight into practitioners’ perceptions of onboarding-technique efficacy and which practices they consider valuable for supporting onboarding goals.The stated aims cover goals, techniques, perceived technique contributions, and onboarding duration.Source: A. Research objectives, aims and… · pp. 2–3
• RQ1 asks which onboarding goals are relevant to software development teams, with a subset representing desired outcomes from the organization’s perspective.RQ2 asks which contemporary onboarding techniques are useful in team software development and could inform program design.Source: A. Research objectives, aims and… · p. 3
• RQ3 asks which onboarding techniques contribute strongly to achieving each goal, as a basis for selecting techniques for a desired goal set.The selection purpose is stated in the research approach.Source: A. Research objectives, aims and… · p. 3
• RQ4 asks about likely onboarding duration because its uncertain endpoint matters for aligning expectations and planning.Duration was assessed using participants’ recollections of how long it took them to feel productive and onboarded.Source: A. Research objectives, aims and… · p. 3

B. Literature Search (RQ1)

• Searches of Google Scholar, ACM Digital Library, and IEEE Xplore for 2007–2017 returned 202 candidate articles, of which 20 empirical onboarding papers remained after screening.The search covered onboarding-related terms alongside software and software-development terms.Source: B. Literature Search (RQ1) · p. 3
• Researchers extracted and open-coded literature passages on onboarding outcomes, adjustments, challenges, and goals, identifying eleven goal areas organized into five themes.Two authors coded and categorized independently, then discussed discrepancies to reach consensus.Source: B. Literature Search (RQ1) · p. 3
• The resulting goals were used as Repertory Grid column headings and explained to participants in the interview protocol.Source: B. Literature Search (RQ1) · p. 3

C. Participant Selection

• Participants were recruited through researchers’ networks based on organizational proximity, software development, Agile small-team work, and willingness to participate.Fourteen initially accepted from ten organizations, but three did not proceed.Source: C. Participant Selection · p. 3
• The final sample comprised eleven participants from eight organizations: eight developers and three testers, with all new to their software product domain.Seven were new to both organization and role, five were recent graduates, and ten were new to Agile work.Source: C. Participant Selection · p. 3
• The organizations spanned SME sizes and several industry sectors, and all participants said their teams used Scrum.Most organizations had 20–100 employees; two had more than 200 and one had fewer than ten.Source: C. Participant Selection · pp. 3–4

D. The Repertory Grid design

• The Repertory Grid used predetermined onboarding goals as elements and participant-elicited techniques as constructs, with a 7-point scale for perceived contribution.Scale values ranged from 1 for no contribution to 7 for very high contribution, with 4 as the midpoint.Source: D. The Repertory Grid design · p. 4

E. The Interview Protocol

• In interviews, participants recalled a recent onboarding experience, identified valuable activities, and rated each technique against each goal while explaining their thinking.Goals were explained using standard literature-derived definitions; interviews lasted 45 to 60 minutes.Source: E. The Interview Protocol · p. 4

F. Data Analysis

• Aggregated repertory-grid views were intended to retain the diversity and commonality across participants’ contexts and experiences.The authors present the combined view as a richer baseline than a single participant’s view.Source: F. Data Analysis · p. 4
• The 81 elicited technique labels were reduced to 24 unique techniques, then each participant’s grid was normalized to support aggregation by onboarding goal.Duplicates and synonyms were merged before participants’ identified techniques were mapped to the final list.Source: F. Data Analysis · p. 4
• Cell scores used weighted Likert-frequency averages and were grouped into five contribution categories, assuming scores were normally distributed around the middle value.The categories were Very Low, Low, Medium, High, and Very High; the middle Likert value was 4.Source: F. Data Analysis · p. 4
• Audio recordings were used to clarify or fill gaps in field notes, but were not transcribed in full.Participants thought aloud while completing the grid, providing explanations of techniques in the recordings.Source: F. Data Analysis · p. 4
• A pilot participant’s data were excluded after feedback led to changes in the interview questions and protocol.Source: F. Data Analysis · p. 4

IV. FINDINGS

• The findings section proceeds from literature-derived onboarding goals to interviewees’ significant techniques, then to aggregated repertory-grid views.Source: §IV · p. 4

A. Onboarding Techniques Used (RQ2)

• The reduced technique list is ordered by how many interviewees identified each technique as important and grouped into three themes.The authors describe the list as a possible checklist for practitioners adapting ideas to their context; Table II presents the techniques.Source: A. Onboarding Techniques Used (RQ2) · pp. 4–5, Table II · p. 5

1) Working with people

• All but two interviewees from the same organization mentioned mentoring, which offered regular feedback and ad hoc technical or onboarding guidance.Mentors included experienced team members, senior developers, team leaders, and Scrum Masters.Source: 1) Working with people · p. 5
• Interviewees said effective mentoring requires trained mentors, recognized time for the role, and explicitly agreed expectations.Source: 1) Working with people · pp. 5–6
• Online communities were a prominent first response to technical problems, but participants did not describe how they judged source credibility.Examples included search engines, Stack Overflow, Quora, MSDN, and experts’ blogs.Source: 1) Working with people · p. 6
• Most interviewees valued peer support for questions and work tasks, while some worried about interrupting teammates too often.Support was generally reactive and self-driven; some newcomers used electronic resources instead of asking teammates or mentors.Source: 1) Working with people · p. 6

• Pair programming helped some interviewees learn the existing code, team coding practices, and other team members.Source: 2) tUndertaking Activities · p. 6
• Daily standups offered regular peer support and question-asking, while retrospectives and meetings with other teams helped newcomers understand team practices.A retrospective also provided a safe forum for a newcomer to speak; meeting other teams offered a chance to see what they did and potentially learn from them.Source: 2) tUndertaking Activities · p. 6
• Setting expectations and reviewing plans with a team lead or mentor helped address uncertainty and keep newcomers informed about team deliverables and schedules.One interviewee reviewed plans frequently at first, then less often as onboarding progressed.Source: 2) tUndertaking Activities · p. 6
• A solid product overview, including the product’s value to clients, gave newcomers context and meaning for their development work.One interviewee found a video overview of product features useful to revisit during onboarding.Source: 2) tUndertaking Activities · p. 6
• Team socializing was stressed by most interviewees as a way to build mutual trust, respect, and acceptance.Examples included team celebrations, shared lunches, and informal watercooler interactions.Source: 2) tUndertaking Activities · p. 6
• A simple initial task let newcomers apply and contextualize learning, identify knowledge gaps, and achieve a low-impact early success.One experienced, confident interviewee instead valued a complex task as an opportunity to prove themselves and gain trust and respect.Source: 2) tUndertaking Activities · p. 6
• Organized training courses on workplace technologies were the most commonly mentioned activity for improving work-ready skills and capabilities.Participants also described third-party courses, self-learning, and conferences as ways to improve skills; colleagues attending conferences could also support relationship building.Source: 2) tUndertaking Activities · pp. 6–7
• Interviewees valued induction courses and organizational rotations for introducing newcomers to policies, procedures, practices, and other parts of the organization.One participant found short periods working in different departments and branches useful for team onboarding.Source: 2) tUndertaking Activities · p. 7

3) Working with Artefacts

• Internal documentation helped newcomers understand development artefacts, including code design decisions, tests, work standards, databases, and local development tools.Sources included workflow tools, code comments and repositories, manuals, project plans, product information, and checklists.Source: 3) Working with Artefacts · p. 7
• Knowledge databases provided searchable, accessible organizational and team information, and some newcomers contributed to them to show progress and gain trust.Their contents included technical topics as well as policies and organizational structure; interviewees valued information that was up to date.Source: 3) Working with Artefacts · p. 7
• Access to a central code repository let newcomers inspect code, learn the codebase’s design and norms, and encounter new techniques; some also valued team code reviews.Source: 3) Working with Artefacts · p. 7
• Checklists served as memory aids, while a location map of people, roles, and expertise was described as invaluable early in onboarding.Source: 3) Working with Artefacts · p. 7

B. Mapping Onboarding Techniques to Onboarding Goals

• Mentoring and Peer Support were perceived as contributing highly to all onboarding goals, while nine other techniques had high contributions to six or more goals.The authors advise balancing broad contributions against implementation costs, such as mentor training and time, and considering techniques with narrower contributions for particular goals.Source: B. Mapping Onboarding Techniques to… · p. 7
• The aggregated mapping was proposed as a guide for selecting onboarding techniques and goals suited to an individual’s characteristics and team situation.The authors suggest selecting context-appropriate goals and then using the technique-to-goal mapping to identify techniques to consider.Source: B. Mapping Onboarding Techniques to… · p. 7

• One experienced developer felt confident after a month and needed an additional month for full control of their work.Source: C. Duration of Onboarding (RQ4) · p. 7
• A newcomer with little or no work experience generally needed one or more extra months to feel onboarded.One graduate described three weeks to learn languages and techniques, then about another month and a half to finish regular tasks while still needing help; another still felt outside the team after four months.Source: C. Duration of Onboarding (RQ4) · pp. 7, 9
• Interviewees perceived onboarding as taking 2–6 months overall, but the authors state that this estimate needs further research.They also found that task capability was the main front-of-mind indicator of completion, while only a few mentioned understanding team processes or feeling part of the team as expected outcomes.Source: C. Duration of Onboarding (RQ4) · p. 9

A. Onboarding Techniques

• The technique results can broaden practitioners’ options and help organizations consider onboarder perspectives when implementing practices such as mentoring.The authors note that effective onboarding also requires recognizing the organizational effort involved in implementing techniques.Source: A. Onboarding Techniques · p. 9

1) Socialization opportunities

• Organizations may need to organize social opportunities and allocate time and money to support them as an organizational norm.Interviewees considered team social events significant for developing relationships and trust.Source: 1) Socialization opportunities · p. 9

2) Access to high quality knowledge artefacts

• Effective information access depends on relevant, timely, low-effort, and accurate knowledge artefacts, with safeguards against inadvertent modification.Interviewees reported outdated or erroneous documentation; newcomers may also need search and credibility-evaluation training, and information sources may need mapping when complex.Source: 2) Access to high quality knowledge… · p. 9

3) Access to formal training

• Organizations may need to fund and schedule formal training and arrange course registration to address onboarders’ skill gaps.Training may address gaps anticipated before onboarding or discovered during it.Source: 3) Access to formal training · p. 9

4) Proactive feedback and knowledge sharing

• Onboarding-related people need preparation, time, and aligned availability to provide useful advice, feedback, and knowledge sharing.Interviewees valued feedback on onboarding progress and work quality; expertise maps can help locate knowledge but require ongoing maintenance.Source: 4) Proactive feedback and knowledge… · p. 9

1) Provide psychological safety

• Most interviewees found onboarding more effective when they would not be blamed or punished for mistakes or slower work.The team and organization need to promote learning from mistakes and continuous improvement.Source: 4) Proactive feedback and knowledge… · p. 9, 1) Provide psychological safety · p. 10

B. Contextualized Onboarding Design

• Contextualized onboarding selects goals and then techniques with high contributions to those goals, drawing on Tables I and III and Fig. 2.The selection can account for newcomer, project, and team circumstances.Source: B. Contextualized Onboarding Design · p. 10
• Relevant contextual factors include work and Agile experience, organizational familiarity, team relationships, role, product expertise, team duration, and available resources.The scenarios include newcomers ranging from graduates to experienced employees and from temporary teams to long-term teams.Source: B. Contextualized Onboarding Design · p. 10
• For an experienced Agile employee unfamiliar with a product and tool, suggested techniques include socializing, documentation, product overview, plan review, and standups.A training course on the unfamiliar tool may also be effective.Source: B. Contextualized Onboarding Design · p. 10

VI. CONCLUSION

• Twenty-four diverse onboarding practices were identified, and interview data suggested organizations may support a new team member for around 3 months.The study also synthesized eleven categories of onboarding goals from literature.Source: §VI · p. 10
• The Repertory Grid Technique aggregated interviewees’ perceptions of how much each onboarding technique contributes to each onboarding goal.The proposed mapping is intended to guide selection of techniques for a particular goal profile and onboarding context.Source: §VI · p. 10

VII. LIMITATIONS AND THREATS TO VALIDITY

• The study claims some generalizability to developers and testers in Agile teams, but effectiveness of personalized technique-goal mapping needs further evaluation.Interviewees represented diverse organizational contexts and individual experiences.Source: §VII · p. 10
• The technique list is unlikely to be exhaustive, and categorizing goals and techniques involves unavoidable subjectivity despite mitigation steps.Two researchers coded independently and aligned results; representatives from some participating organizations also reviewed the code set, categories, and results.Source: §VII · p. 10