Onboarding gets a new developer from joining a team to shipping useful code. Stale instructions, broken setup, and long waits create avoidable waste; measure the time from the first day to the first production deployment. section 13.5
Shorten that path by improving the work around the new hire:
- Provide an automated setup script or container that creates a working environment in under thirty minutes. section 13.5
- Prepare a small, real task that can ship on day one, such as a typo fix or an edge-case test. section 13.5
- Replace stale wiki instructions with executable documentation. section 13.9
James’s first deployment
James waits for a buddy, follows outdated setup instructions, and submits his first pull request on day eight. His code reaches production on day twenty-two. Mapping those activities makes waiting and rework visible alongside the coding and review that add value. section 13.5
Table 13.2 Onboarding value stream analysis
|
Activity
|
Time
|
Classification
|
|
Reading stale wiki documentation
|
12 hours
|
Waste (defective information)
|
|
Configuring dev environment from outdated instructions
|
8 hours
|
Waste (rework, waiting)
|
|
Waiting for buddy availability
|
10 hours
|
Waste (waiting)
|
|
Waiting for first PR review
|
24 hours
|
Waste (waiting)
|
|
Actual coding on first task
|
6 hours
|
Value-add
|
|
Code review rounds (learning from feedback)
|
4 hours
|
Value-add
|
|
Meeting the team, understanding the domain
|
3 hours
|
Value-add
|
|
HR paperwork, compliance training
|
5 hours
|
Necessary non-value-add
|
|
Total
|
72 hours
|
18% value-add
|
Compare onboarding activities by time and classification to see where waste accumulates. section 13.5




