Abstract: Onboarding can be difficult, especially when growing a team by 100% or more in a short period of time. How can you ensure that the practices your team believes in are spread to new hires? When growing this quickly how can you ensure that beliefs in things like test driven development, boy scout coding and incremental architecture don't get lost in the explosion? How can you mentor when half or more of your team has been around for less than a year?
This presentation will describe the specific approaches we have used to onboard new developers, and delve into what we've learned. We'll talk about some of our failures and show some of our successes. As with any development practice we'll show how we've used continuous improvement to tweak our onboarding practices, ensuring that our new members get up to speed very quickly and contribute almost immediately.
Learning Outcomes: - mob-programming is the best way to learn
- safe spaces in development can be super effective
- pair-programming alone is not enough
- embedding with a team right away is not enough
- onboarding needs to be continuously examined
Attachments:
