The first two weeks of a new developer's job shape how quickly they become useful and how safely they work. Many teams leave that period to chance, handing over a laptop and a vague list of links. This roadmap treats onboarding as a small project with its own board, and it includes a practice lab on google gruyere, an app created by Google with intentional flaws, which CodeRed lists at an advanced level and about one hour long.
Two sprints is long enough to learn the team's habits and short enough to adjust quickly. By the end, the newcomer should have shipped something small, asked many questions, and understood what the team expects from a finished task. Nothing here needs special software, only a shared board and a willingness to write things down.
How Do You Onboard a New Developer Across Two Sprints?
Use sprint one for orientation, access, a small first task, and a practice lab, and sprint two for a real task with a buddy. Keep both sprints short, give every item an owner and a yes or no check, and review progress at the end of each one. The newcomer then learns the work and the team habits together.
The plan below works for teams of any size.
Why Two Sprints Works Better Than One Orientation Day
A single orientation day delivers a flood of information, and most of it is gone by the following week. People remember what they use, so spreading learning across real work helps it stick. A board also gives the newcomer a visible path instead of a pile of links.
It also helps the team. Seeing how a new person moves through the work exposes unclear instructions, missing documents, and habits nobody wrote down. Those gaps are easier to fix while a fresh pair of eyes is still noticing them.
Set Up the Board Before Day One
Create a small board for the onboarding with columns for to do, in progress, and done, and fill it before the newcomer arrives. If your team is new to Scrum, the jira agile project management course at CodeRed is listed as a beginner course of about 33 minutes covering a first Scrum project setup and an introduction to Agile. Any board tool works, because the habit matters more than the software.
Write each task with an outcome, an owner, and a yes or no check, such as "Can the newcomer run the project on their own machine?" Putting the first week's tasks on the board lets everyone see what is planned and what is stuck.
Keep the board to the next two weeks only. A long list of future tasks overwhelms a newcomer, while a short list shows exactly what is expected and when.
Sprint One: Orientation and a Small First Task
Start with access and introductions, then give the newcomer one small task they can finish in a day or two. A small win builds confidence and teaches the team's process for reviewing and finishing work. Pick something real but low risk, such as fixing a typo in the documentation.
Here is the practical tip: ask the newcomer to keep a confusing things log from day one. Every time something is unclear, they write one line. Once each sprint, the team fixes the top item, whether that means improving a document, renaming a folder, or explaining a rule.
Fresh eyes notice things insiders have stopped seeing, and that value fades after a few weeks. Capturing it early improves the experience for the next hire too.
Sprint One: A Safe Practice Lab for Secure Habits
Add one learning task on web security if the team builds web applications. The Gruyere page mentions cross-site scripting and cross-site request forgery, and says some tasks involve reviewing source code written in Python. Because the lab is advanced, it suits a developer who already knows web basics, and a newer one can start with simpler material first.
Frame the task as a question with a written answer, such as "How does our own application treat information typed in by visitors?" Keep it at the concept level, aimed at understanding defenses. Use the lab only as an authorized practice environment, keep it away from machines holding real data, and never test a site you do not have written permission to test.
Sprint Two: A Real Task With a Buddy
In the second sprint, give the newcomer a real task of modest size and pair them with a buddy who reviews their work and answers questions. The buddy's job is to explain why the team does things a certain way, not only how. Keep the task small enough that a delay does not threaten the sprint goal.
Review the work together within a day of submission, not at the end of the week. Quick feedback keeps the newcomer's momentum and prevents small misunderstandings from growing.
At the end of the sprint, hold a short retrospective that includes the newcomer's view. Ask what helped, what was confusing, and what one change would make the next hire's start smoother. Write the answers on the board and assign owners.
A Note for the Person Running the Onboarding
Onboarding works best when it is treated as part of the team's work and not an interruption to it. Block the buddy's time on their calendar, keep the board current, and resist the urge to add more tasks when the newcomer seems quick. A calm pace in the first two sprints builds good habits that last long after the plan ends, and it tells the newcomer that questions are welcome.
After the second retrospective, keep the board and the confusing things log for the next hire. Update them each time someone joins, and the plan improves with every use. Within a year, the team will have an onboarding routine shaped by its own experience, and each new developer is likelier to reach useful work with fewer surprises.