LinuxBozo commented 8 years ago

In order to get NewPerson productively contributing to the cloud.gov team, Buddy should help NewPerson complete a prescribed set of tasks that will bring them up to speed.

Directions:

NewPerson and Buddy: Try to go through your checklists in order. Buddy: If you can’t complete any of the items on your checklist personally, you are responsible for ensuring that an appropriate person does it.

New Person checklist

[x] Take judicious notes on what about this onboarding process or cloud.gov is confusing or frustrating. If you notice a problem (especially with things like documentation), you are more than welcome to fix it! At the very least, please share this information with your buddy (or someone) at some point so we can make the team/platform better. (You can also file issues and pull-requests on the template for Onboarding issues.)
[x] Figure out who your onboarding buddy is (they should reach out to you) and make sure this issue is assigned to them)
[x] Read the team onboarding document for more context about cloud.gov
[x] Read the "What is it?" presentation for a rundown of what cloud.gov is and does
[x] Read through the Introduction section of docs.cloud.gov for a broader understanding of cloud.gov, especially as we present it to potential customers/users
[x] Read the January 2016 cloud.gov "Executive Business Case" document for greater context about cloud.gov's potential impact in government
[x] Try to deploy a sample application to cloud.gov to get familiar with the basics of the PaaS from a user's perspective
[x] Check out the roadmap to get a high-level view of recently-completed, in-progress, and upcoming features
[x] Install the ZenHub browser extension to enable you to see kanban boards, hierarchical issues, and burndown charts in GitHub
[x] Read the Delivery Process document to learn about how we work
[x] Read the Incident Response Policy to learn about our Incident Response Policy. Coordinate with your onboarding buddy to go thru Incident Response Training within 60 days of joining the team
[x] Read the Contingency Planning Policy to learn about contingency planning. Coordinate with your onboarding buddy to go thru Contingency Planning training annually
[x] Read the Configuration Management Policy to learn about configuration management. Coordinate with your onboarding buddy to go thru Configuration Management training
[x] Subscribe to the cloud.gov team calendar (click the + in the bottom right) so you know when assorted team meetings are happening in the various streams
[x] Join the cloud.gov support Google Group, so you can see how we handle non-18F support and get visibility of technical discussions happening with outside groups
[ ] Figure out what themes you're likely to work in, and complete the checklist below that relates to it
[ ] Once you've finished the remaining checklists below, make suggestions for steps that would have improved your onboarding experience as pull-requests on the onboarding checklist template used to make this issue
Atlas-specific items
[x] Bookmark the Atlas kanban board view
[x] Make sure you join the #cloud-gov-atlas channel on Slack
[x] Watch Build Your Own Private Cloud Foundry to learn about running Cloud Foundry
[x] Set up Cloud Foundry locally and push an app to it
[x] Learn about BOSH: Watch this video and see our manifests (and read this for levity)
[x] Get to know how UAA is deployed/integrated (https://docs.cloudfoundry.org/concepts/architecture/uaa.html)
[x] Get familiar with Terraform by going thru the getting started guide
[x] Learn about Concourse and try a tutorial
[x] Check out our staging and production Concourse instances, and take a look at some of our pipelines
[x] Join the Cloud Foundry Slack
[x] Get familiar with AWS in general if you're not already (TODO: We need some pointers here)
Agent Q-specific items
[ ] Bookmark the Agent Q kanban board view
[ ] Make sure you join the #cloud-gov-agent-q channel on Slack
[ ] Read about Cloud Foundry services from a user perspective
[ ] Read about implementing services
[ ] Take a look at some of our existing brokers
[ ] Learn about Concourse: Check out our staging and production instances, and take a look at some of our pipelines
[ ] Join the Cloud Foundry Slack
Liberator-specific items
[ ] See the Liberator Onboarding Checklist (Does that belong here?)
HighBar-specific items
[ ] Bookmark the HighBar kanban board view
[ ] Make sure you join the #cloud-gov-highbar channel on Slack
[ ] Read through the description of Compliance Toolkit
[ ] Watch Handling FISMA Faster and Better for important context and background on the federal regulatory context in which cloud.gov operates.
[ ] Do a cursory read of Before You Ship
[ ] Read the intro to Compliance Masonry

Buddy checklist

[x] Introduce yourself to the new team member and give them some of your background so they know who you are
[x] Make sure they're listed in the list of people working on the project
[x] Add them to the @cloud-gov-team in Slack’s Team Directory (which also adds them to the right channels)
[x] Add them to the recurring cloud.gov meetings that are relevant for them in the team calendar
[x] Setup a cloud.gov user account for them via the “send an invite” page
[x] Identify a straightforward, well-groomed story in progress that involves their skills domain, schedule a meeting with the owner for an introduction (if it's not you), and setup pairing sessions several times in the first week on the project.
[x] Identify a straightforward, well-groomed first story, ideally something they could conceivably complete in their first two/three weeks using their existing skills. Discuss the context with them, then make them the assignee for the card.
[ ] Make suggestions for how your onboarding experience could have been improved as PRs on the onboarding template.
[x] Confirm they have 2FA enabled for GitHub, and ask #admins-github to have them added to the @18F/cloud.gov team on GitHub
Atlas-specific items
[x] Ask #admins-github to have them added to the @18F/cloud-gov-team team on GitHub (For contractors: Confirm they have cleared GSA security review before doing this one!)
[x] If the new person is a contractor, ask #admins-github to have them added to the @18F/cloud-gov-contractors team on GitHub
[ ] Grant them access to the following (where applicable): AWS, New Relic, PagerDuty, StatusPage
[ ] Take them through AWS onboarding (if applicable)
[x] Give them a walkthrough of cloud.gov from an architecture and repository perspective

jbarnicle commented 8 years ago

@LinuxBozo @datn Can we close this issue?

mogul commented 8 years ago

Let's double-check that any compliance requirements were hit.

datn commented 7 years ago

@mogul points out that this issue is still open. I'm happy to close it but for 2 things:

Grant them access to the following (where applicable): AWS, New Relic, PagerDuty, StatusPage
My feedback on how onboarding could have gone better

I can pledge to do the second one; should I have faith that the first one will be done? If so, I'll close it out.

cloud-gov / cg-atlas

Ramp up Dan Shick #135

Directions:

New Person checklist

Atlas-specific items

Agent Q-specific items

Liberator-specific items

HighBar-specific items

Buddy checklist

Atlas-specific items