2.5: Team Onboarding
What You'll Learn
By the end of this chapter, you'll be able to:
- Design a 4-week onboarding program that actually works
- Get new team members productive faster (weeks, not months)
- Create checklists that ensure nothing falls through the cracks
- Build a training path from ASPICE fundamentals to autonomous contributor
Introduction
Here's a scenario that kills projects: you hire a talented developer, hand them a laptop, point them at the wiki (which hasn't been updated in 18 months), and say "good luck." Three months later, they're still confused about the process, making mistakes that more experienced team members catch in reviews, and wondering if they made the right career choice.
There's a better way.
Effective onboarding ensures everyone understands ASPICE processes, tools, and workflows from day one. A structured program reduces ramp-up time from months to weeks—and shows new team members you actually care about their success.
The 4-Week Onboarding Program
This isn't a suggestion—it's a proven structure. Adapt the specifics to your project, but keep the progression: foundations → tools → quality → real work.
Week 1: ASPICE Fundamentals
"Why before how."
| Day | Topic | Duration | Format |
|---|---|---|---|
| 1 | ASPICE Overview & V-Model | 4h | Workshop |
| 2 | Process Groups (SYS, SWE, SUP, MAN) | 4h | Workshop |
| 3 | Work Products & Traceability | 4h | Workshop |
| 4 | Tool Ecosystem Tour | 4h | Hands-on |
| 5 | Team Workflow & Git | 4h | Hands-on |
Goal: By Friday, they understand why we do things this way—not just what to do.
Week 2: Development Tools
"Hands on keyboard."
| Day | Topic | Duration | Format |
|---|---|---|---|
| 1 | VS Code + GitHub Copilot | 4h | Hands-on |
| 2 | Requirements in Jama/DOORS | 4h | Hands-on |
| 3 | Architecture in EA/Rhapsody | 4h | Hands-on |
| 4 | AUTOSAR Basics (if applicable) | 4h | Workshop |
| 5 | CI/CD Pipeline | 4h | Hands-on |
Goal: They can navigate every tool in our stack and perform basic tasks.
Week 3: Quality & Testing
"How we catch bugs before they escape."
| Day | Topic | Duration | Format |
|---|---|---|---|
| 1 | MISRA C Compliance | 4h | Workshop |
| 2 | Unit Testing with Unity | 4h | Hands-on |
| 3 | Static Analysis Tools | 4h | Hands-on |
| 4 | Code Review Process | 4h | Workshop |
| 5 | Integration Testing | 4h | Hands-on |
Goal: They understand our quality gates and can write tests that pass them.
Week 4: Real Project Work
"Training wheels off."
| Day | Topic | Duration | Format |
|---|---|---|---|
| 1-5 | Pair Programming on Real Tasks | 8h/day | Mentored work |
Goal: They complete their first real contribution with a mentor's support.
The Complete Onboarding Checklist
Print this. Use it. Update it when you learn something new.
# New Team Member Onboarding Checklist
**New Hire Name**: ________________
**Start Date**: ________________
**Mentor**: ________________
## Pre-Arrival (Week -1)
- [ ] Hardware: Laptop, monitors, peripherals ordered
- [ ] Accounts: GitHub, Jira, Confluence, Slack created
- [ ] Access: Repository permissions, tool licenses assigned
- [ ] Documentation: Share project wiki link
- [ ] Mentor: Assigned and briefed
## Day 1: Welcome & Setup
- [ ] Welcome meeting with team (30 min)
- [ ] IT setup: Laptop configuration, accounts verification
- [ ] Install development tools (VS Code, Git, CMake, etc.)
- [ ] Clone main repository
- [ ] Successful local build achieved ← Don't skip this!
- [ ] Join team Slack channels
## Week 1: ASPICE Foundations
- [ ] Complete ASPICE e-learning course (8 hours)
- [ ] Read project ASPICE Tailoring Document
- [ ] Understand V-Model for our project
- [ ] Review work product templates
- [ ] Shadow: Attend sprint planning
- [ ] Shadow: Attend daily standup (all 5 days)
## Week 2: Tools & Workflow
- [ ] Jama/DOORS training completed
- [ ] Create first requirement (practice)
- [ ] Git workflow training completed
- [ ] Create first feature branch
- [ ] Submit first PR (documentation improvement is fine!)
- [ ] Review a teammate's PR
- [ ] CI/CD pipeline walkthrough
## Week 3: Quality & Testing
- [ ] MISRA C training completed
- [ ] Run static analysis locally
- [ ] Fix MISRA violation (practice code)
- [ ] Write first unit test
- [ ] Achieve 100% coverage on practice module
- [ ] Code review training completed
## Week 4: Productive Contribution
- [ ] Assigned to real Jira story
- [ ] Implement feature with pair programming
- [ ] Write unit tests for own code
- [ ] Submit PR for review
- [ ] PR approved and merged
- [ ] Feature deployed to integration branch
## Month 2-3: Advanced Topics
- [ ] ISO 26262 safety training (if ASIL project)
- [ ] AUTOSAR deep dive (if applicable)
- [ ] Review historical assessment findings
- [ ] Participate in sprint retrospective
- [ ] Present demo at sprint review
## 3-Month Review
- [ ] Self-assessment completed
- [ ] Manager 1:1 review
- [ ] Competency gaps identified
- [ ] Training plan for next quarter
- [ ] Fully autonomous contributor? ✅ Yes / ⚠️ Needs support
The Mentor's Playbook
Assigning a mentor isn't enough—you need to tell them what to do.
Week 1: Active Guidance
- Sit with them for at least 2 hours/day
- Answer questions before they need to ask
- Introduce them to key people (QA, architect, product owner)
- Review their ASPICE understanding at end of week
Week 2: Available Support
- Check in twice daily (morning, afternoon)
- Let them struggle a bit—but not too long
- Review their first PR together
- Celebrate small wins (first build, first commit)
Week 3: On-Demand Help
- Check in once daily
- Let them drive, you navigate
- Review their test code quality
- Start including them in technical discussions
Week 4: Pair Programming
- Work together on a real story
- You type first, then swap
- Explain your thought process out loud
- Let them make mistakes (then help fix them)
Measuring Onboarding Success
How do you know if your onboarding actually works?
| Metric | Target | How to Measure |
|---|---|---|
| Time to first merged PR | < 2 weeks | Git history |
| Time to solo story completion | < 4 weeks | Jira tracking |
| Questions per day (week 4) | < 5 | Mentor observation |
| Code review rejection rate (month 1) | < 30% | PR history |
| 3-month retention | 100% | HR data |
If someone leaves in the first 3 months, that's an onboarding failure—not a hiring failure.
Common Onboarding Mistakes (And How to Avoid Them)
❌ MISTAKE ✅ INSTEAD
"Just read the wiki" Structured curriculum with checkpoints
Throwing them into complex code Start with isolated, well-tested modules
No mentor assignment Named mentor with clear responsibilities
Assuming they'll ask questions Proactively check in multiple times/day
Same onboarding for all roles Role-specific tracks (dev, QA, architect)
No feedback loop Weekly check-ins, adjust as needed
Summary
Effective onboarding is an investment that pays dividends for years:
- 4-Week Structured Program: ASPICE → Tools → Quality → Real Work
- Hands-On Learning: 60% workshops, 40% independent work
- Mentorship: Active guidance that tapers to autonomy
- Checklist-Driven: Clear milestones and expectations
- 3-Month Goal: Fully autonomous contributor
Your Key Principles:
- 🎯 Start with why (ASPICE context) before how (tools)
- 💻 Hands-on immediately—successful build on day 1
- 👥 Pair programming accelerates learning more than any other technique
- 🔄 Regular check-ins—don't let people get stuck
- 📊 Feedback loops—improve onboarding based on experience
You've set up your project. Your tools are in place. Your team knows what they're doing. Now let's give them templates for the work products they'll create.