Onboard Offboard

Onboarding and Offboarding

What is the process

• An issue created 1 time on your project's repo, that you reuse every time someone enters and exists the project
• Assigning the issue to the person being onboarded/offboarded and to the person doing the onboarding/offboarding.
• Going through the required steps and filling out the checkboxes.
• When complete, if there is no person still assigned, goes back into the icebox.

Why we need the processes

Onboarding process

• To make it easy to get someone added to your project
• Faster onboarding = reduced attrition and time spent by existing PMs
• Keep the hackforLA.org website up to date for your project page

Offboarding

• So that people who have left the project don't get unwanted emails and notifications
• Reduced risk of hacked resources
• Reduced risk of accidental deletions
• Defined process, helps the PM keep track of how many people are in the project, which aids in recruitment planning
• Keep the hackforLA.org website up to date for your project page

Templates

We need different templates for each type of member of team so that we can easily see what resources and permissions that person needs.

Product

• Title of issue: Onboard & Offboard: Product
• Preview Onboard & Offboard: Product template
• Copy Onboard & Offboard: Product template
• Examples from projects that are using the process
  • Open Community Survey

Tutorials Need for items from action list in template issue

• How to add someone to the email account for the project

Improvements Needed

• "login to team account" needs more details

Add Your Onboarding Issue Here

• https://github.com/hackforla/access-the-data/issues/130 2022-02-15
• https://github.com/hackforla/internship/issues/123 2022-02-23

Changelog

What got added to the template when

• Changelog