Onboarding a new team member

onboarding.md

Stage	Phase	Name	Goal	Responsibilites	Outcome	Checlist
1	1	Meet the team	Get to know each other	whole team	The team should decide does the candidate is a good fit for our team or not	- personal introduction - explain the team's WoW - introduction of the team's OPEX - Tech stack - Q&A
2	1	Setup development environment	Properly set up a laptop and communication within the team	a team member	Fully working laptop with all credentials set up and team's communication in place	- the laptop is working properly - can connect to all essential applications and services - set up communication channels with a team
	2	Welcome a new team member	Greet a new member of the team	whole team	Get to know each other and show organisation and the team's culture	- get familiar with a team and everyone's responsibilities
3	1	Company onboarding procedures	Understand the vision and goals of the company	company representatives	Clear understanding whats the vision and purpose of the company	- understand the vision and goals of the company - grasps the abbreviations within the organisation
	2	Overview of the team's OPEX and Products	Get an understanding of the team's OPEX and what the team does	Product owner	Have a high overview of the products that the team owns	- understand functional products managed by the team
	3	Tech decisions and WoW overview	Understanding the decisions that the team made and how the team works in a day-to-day flow	a team member	Know what Agile methodology is used. In addition, how the system is structured and how it should be built	- getting familiar with the team's agile process - high overview of the team's domain concepts - understanding the technical decisions that the team made
	4	High overview of the applications and business flows within the team	Grasp the basics of the business flows that the team's applications have	a team member	Get an understanding of how the systems are connected and what business processes are within them	- have a high overview of the system architecture - being involved in communications within a specific domain
	5	Introduction to domain	Get involved in the applications and have a basic understanding of how the system works	a team member	Perform a whole development cycle within the application	- get a basic understanding of a specific application - complete the full development cycle for a small task
4	1	In-depth business flows and applications architecture	Understand the whole system that the team owns with their business flows and how it works within the team's applications	a team member	Get an understanding of how our systems work and how they are connected within the organisation landscape	- have an in-depth architecture overview of the systems maintained by the team - hands-on of the codebase with a few applications - have a clear picture of how the systems are connected within the organisation landscape
	2	Pair programming sessions	The new team joiner gets a better grasp of the code projects by copiloting along with team members during implementation of their tasks	team's developers	Check and collaborate with each developer during the implementation of their labour to familiarise with the way of working and team standards	- opening and navigating through code/projects - Discussing and applying best practices for coding - Make/apply tests - Executing git flow (create merge request)
	3	In-depth domain exploration	Be more involved in the applications, have a better understanding of how the system works and what systems are used/using our applications	a team member	Be more involved in the development cycle within OPEX applications	- pick up a new task - being able to create sub-tasks - complete the full development cycle for any tasks on the board - being involved in all team's communications
	4	Introduction to EOD (Engineer on Duty) role	Get more involved in the team's processes and responsibilities within the company	a team member	Understand the EOD responsibilities. Moreover, knowledge of using the procedure for investigation and presenting to the team the outcome	- being able to pick up any tasks from the incident or questions channels - understand the concepts and connections of other systems that are involved with our domain
5	1	Getting grip on the domain	Getting knowledge of the products that the team managed and exploring other applications that communicate with the team's applications	new team member	A clear understanding of how the system works	- communication with stakeholders - provide the summary to the team after the communication within the business - actively participate in all team meetings
6	1	Sub (shadow) Epic leading	Understanding and performing the fully epic leading process with one of the team members	a team member	Understanding the whole process of the epic leading	- a clear understanding of what should be done at what stage - understand the stakeholder's requests - being able to perform the investigation that requires communication with a business
7	1	Epic leading	Understanding and performing the fully epic leading process independently	new team member	Being able to pick up any epics from the very beginning and finalize it	- negotiate and explain the possible consequences of the different approaches with stakeholders - design and present to the team solutions that need to be implemented