Write your ways of working
If you want to minimise the guesswork a new developer on the team has to do, keep everything documented. In terms of documentation, here are a few questions you should answer up front, in writing.
How do you collaborate as a team?
Do you pair-program by default or do you work independently? How do standups, story kick-offs, desk checks and other practices work? What’s the process for code reviews?
What are the different environments you have on the project?
Different teams have different environments. For example, development, QA, UAT, staging and production environments. If they\ developers need to set up access, then the instructions should be crystal clear.
How do you track project metrics?
Teams use tools such as LinearB, SonarQube or Polaris to assess themselves on several parameters. Even if your new developers don’t have experience with all your tooling, it helps to give them a lay of the land right at the start.