IxDF Developer Docs

Appearance

Offboarding: Team Lead checklist ​

Meta ​

This is a document for Dev Team Lead to properly offboard a developer. There is also a copy for developer. The workflow is simple: a Team Lead asks a developer to go through developer offboarding checklist and then checks how it’s completed by following the current document/checklist.

Checklist ​

Legend:

  • 🚼 Should be initiated/done by a developer leaving us, but required to be re-checked by team lead.
  • 💣 Critical action.

Actions:

  1. 💣 Ask the developer to follow developer’s offboarding guide.
  2. 💣 Make sure to coordinate with Mads who will ask someone from the MEx team to help with the offboarding. They will use the playbook from the IxDF - PeopleAndCulture - Offboarding Dropbox directory.
  3. 🚼 Make sure the team member finishes up all PRs (or reassigns them).
  4. 🚼 Make sure the team member reviewed all PRs assigned to them as reviewer.
  5. 🚼 Reassign GitHub issues to other developers. Update them if there is something to add: More context, current state, etc. The more context you provide, the better.
  6. 🚼 Remove the person’s old/stale branches from GitHub (by first checking that they don’t have associated PRs).
  7. Remove the team member’s contact info from the codebase (use full-text search by their name and nickname).
  8. The person should let Mads remove them from Dropbox. It’s essential to not touch any files since it may risk deleting those folders from everyone’s account!
  9. 💣 Remove the team member’s SSH keys from our servers.
  10. 💣 Remove the team member from various servers/services, etc. Make sure that we don’t forget any! Here are some examples:
    • Laravel Forge (team member account)
    • DigitalOcean (team member account), plus remove SSH keys
    • PHPStorm (license)
    • Laracasts (remove from a team, use a shared madssoegaard account)
    • Mailtrap (inbox)
    • Algolia (team member account)
    • Stripe (test-only account, log in using development-usa@interaction-design.org)
    • all other services like Slack, Dropbox, LastPass, Google Analytics, Figma, Google Search Console, etc., will be handled by MEx/Mads, and a representative of the Member Experience team (see the point below).
  11. Remove the team member from all calendar events.
  12. Do what we call a “partial overhaul” of the credentials, which is described in credentials-overhaul.md. In other words, we need to change ALL the credentials that the team member has had access to - but NOT the credentials that the team member has NOT had access to. If the team member has had access to a given LastPass shared folder, then we must change ALL the credentials in that given LastPass folder. We do NOT need to change credentials for services that the person has NOT had accessed to (hence, the name “partial overhaul”. Please note: If you feel that the team member has "dodgy ethics" a bit, then we should do a so-called “Complete Overhaul”. Please go to credentials-overhaul.md.
  13. 🚼 Ask for the team member’s constructive feedback: We want to become better 🙃!
  14. Finally, check with Mads to make sure he has asked someone to do all the actions in \IxDF Dropbox\IxDF - Staff - Hiring - Onboarding documents and legal templates\IxDF Offboarding\IxDF Offboarding - Offboarding Checklist for Admins.docx. This includes all the services/platforms like Slack, Dropbox, LastPass, Google Analytics, Figma, Google Search Console, etc.

🦄