cloud-gov / product

Program-level artifacts, workflow and issues for cloud.gov
Creative Commons Zero v1.0 Universal
31 stars 15 forks source link

General Checklist for Onboarding Claire #3104

Closed cweibel closed 3 months ago

cweibel commented 4 months ago

New Team Member Onboarding Checklist

Special Notes


In order to get Claire productively contributing to the cloud.gov team, Brian should help Claire complete a prescribed set of tasks that will bring them up to speed and get them setup with cloud.gov.

Role-Specific Onboarding

This onboarding ticket must be completed by all new cloud.gov team members. It must be paired with a role-specific onboarding ticket. Your onboarding buddy will create both.

Instructions

Your onboarding buddy should reach out and introduce themselves to you. If you have not heard from them after a day or two, please let the team know.

  1. Try to go through the checklists in order.
  2. Make sure this issue is assigned you and your buddy in our Github Project Planning Board. We use this board to organize, prioritize, and track our work.
  3. If Brian cannot complete any of the items on their checklist personally, they are responsible for ensuring that someone with the correct access completes that item.
  4. Take notes on this onboarding process. If you notice a problem, let your buddy know by leaving a comment on this issue, or submit a fix yourself! You can propose a change to any documentation in GitHub using a pull request. The onboarding issue templates, including for this issue, are here.

Pre-requisites

Complete cloud.gov trainings

Onboarding buddy: Contact the compliance team in #cg-compliance to schedule training(s).

Getting to know cloud.gov

These items will help you come up to speed on cloud.gov and what it is, how it works, why it exists, etc. While you should take the time to go through them, please do not try and tackle it all in one shot! It can become overwhelming very quickly, so your onboarding buddy will walk through this list with you at a high level with you to help manage the work.

Team resources

You will automatically be added to one or more Google Drives: the Cloud.gov All Staff Drive and, for federal employees, the Cloud.gov Federal Employees Drive. Put all documents related to cloud.gov in the appropriate shared drive so the team can access them and meet federal records requirements. Each drive contains a folder for each squad, and each squad folder contains a "wiki" that explains how the sub-folders are structured.

Federal employees and staff contractors, expand this section: - [ ] Subscribe to [the cloud.gov team calendar](https://calendar.google.com/calendar/embed?src=gsa.gov_0samf7guodi7o2jhdp0ec99aks@group.calendar.google.com&ctz=America/Los_Angeles) (click the + in the bottom right) so you know when assorted team meetings are happening in the various squads. Tip: When you plan Out of Office time, make a calendar event for that on the cloud.gov calendar so that your teammates know you'll be away.

Slack Channels

The following cloud.gov channels are public and all team members are welcome to join:

Channels marked with (🗣️) receive a lot of messages, either from customers or bots, and you may want to mute them.

For federal employees and staff contractors:

For federal employees only:

Google Groups and Spaces

We manage calendar invites and Google Drive access using Google Groups. Some groups can also receive message from outside emails.

Federal employees and staff contractors, expand this section: Add them to the following Google Groups: - [ ] [cloud.gov Team](https://groups.google.com/a/gsa.gov/g/cloud-gov/members) so they can participate in team-wide internal communication. - [ ] Business Unit Only - Add them to the [cloud.gov inquiries Google Group](https://groups.google.com/a/gsa.gov/g/cloud-gov-inquiries/members) so they can keep apprised of prospective new clients. You will automatically be added to the Google Space [CG-PRIV](https://mail.google.com/mail/u/0/#chat/space/AAAAr60JXAc), a fallback team communication channel in the event Slack is down. They may need added to one or more of these team-specific groups: - [ ] [cloud.gov Assurance Team](https://groups.google.com/a/gsa.gov/g/cloud-gov-assurance/members) - [ ] [cloud.gov Compliance](https://groups.google.com/a/gsa.gov/g/cloud-gov-compliance/members) (external email accepted) - [ ] [cloud.gov Customer Success Team](https://groups.google.com/a/gsa.gov/g/cloud-gov-customer-success/members) Lastly, for federal employees only: - [ ] [cloud.gov Federal Employees](https://groups.google.com/a/gsa.gov/g/cloud-gov-federal-employees/members) - [ ] Make them a Space Manager in [CG-PRIV](https://mail.google.com/mail/u/0/#chat/space/AAAAr60JXAc).
hursey013 commented 3 months ago

Thank you @cannandev!