Purpose
To provide a standardized onboarding workflow for developers joining a new project, ensuring they gain quick context, secure access, and technical setup without delays.
This avoids wasted cycles, missed dependencies, and knowledge silos.
Scope
- Applies to all developers (Frontend, Backend, Mobile, Full-stack) joining any new or existing project.
- Used by Project Leads, Developers, and DevOps/Infra team members.
- Covers knowledge orientation, environment setup, and access provisioning.
Objectives
- Ensure developers get project context within Day 1–3.
- Provide secure access to repositories, tools, and communication channels.
- Establish a ready-to-code environment by the end of the onboarding cycle.
- Reduce dependency on ad-hoc lead explanations.
Step-by-Step Process
Step 1 – Pre-Onboarding Prep (By Lead/PM)
- Share Project Onboarding Kit (Doc 2 – Template).
- Assign a tech buddy/mentor for the first sprint.
- Confirm developer is added to:
- Git repo (read + write as per role).
- Project management tool (Jira/ClickUp/Linear).
- Slack/Teams channels.
- Documentation hub (Confluence/Notion/MIC).
Step 2 – Project Orientation (Day 1)
- Intro session covering:
- Project goals & client context.
- System architecture overview (Doc 2 of Architecture Epic).
- Current sprint & backlog priorities.
- Share Dev Starter Repo README (Doc 10).
- Provide access to Designs (Figma/Zeplin) and API contracts if available.
Step 3 – Environment Setup (Day 1–2)
- Developer sets up:
- Local environment using Setup Guide (Doc 3/4 depending on stack).
- IDE extensions & linting configs.
- Access to dev/staging databases & APIs (with read-only first).
- Run sample build to confirm setup works.
Step 4 – Access & Security Alignment
- Access provided via Access Request Workflow (Doc 7).
- 2FA enabled on all critical tools.
- Developer acknowledges Tool Access Policy (Doc 8).
- Lead verifies access in Access Log Tracker (Doc 12).
Step 5 – First Task Assignment (Day 2–3)
- Assign low-risk starter task:
- Bug fix, documentation update, or small feature enhancement.
- Tech buddy reviews PR → ensure familiarity with Branching & Merge Strategy (EPIC 3).
- Feedback loop: Document challenges faced in setup → update Project Setup Readiness Checklist (Doc 9).
Step 6 – Integration into Team Rituals
- Developer joins:
- Standups, sprint planning, retros.
- Squad syncs with lead.
- Developer starts logging time/effort via project tool.
Roles & Responsibilities
| Role | Responsibility |
| Project Lead | Provides context, approves access, assigns first task |
| Tech Buddy | Guides developer through setup, first sprint |
| Developer | Completes setup, acknowledges policies, executes starter task |
| DevOps/Infra | Grants repo, CI/CD, staging access |
| PM/HR Ops | Ensures onboarding kit & documentation delivery |
Governance
- Onboarding SLA: All new devs must be project-ready within 3 working days.
- Access Logs: Every tool access must be logged in tracker.
- Feedback Loop: Challenges faced → fed into onboarding kit updates quarterly.
- Escalation: If setup blocked >24 hrs → escalate to Project Lead & Infra Team.