Our onboarding process isn't structured to account for "project contractors" who work with the program on a specific project for a scoped amount of time. Project contractors, sometimes called deliverable contractors, are distinct from staff contractors, who are on a service contract and work with the team indefinitely on a variety of projects.
Consider the following:
Which Google Groups project contractors should be added to
This controls which meetings go on their calendar and G-Drive access, and they can see messages in the Group
Which Slack channels contractors should be added to? Should they be multi-channel guests instead of full access? (Outside our control)
If they need all onboarding links up-front, since it is a considerable volume
Since they likely do not have an Incident Response role, can we make it clearer that the IR training is for staff only?
Update the following:
Templates in github.com/cloud-gov/product
Consider keeping one file per role, but making checkboxes contractor- or fed-specific
Include a checkbox for talking to the onboarding buddy about project-specific items
Any other onboarding SOPs
Check with the business team
Check cg-compliance-docs
Lastly, and not project contractor specific, can we shrink the "reading" section of the onboarding tickets, moving some items to a reference section?
Our onboarding process isn't structured to account for "project contractors" who work with the program on a specific project for a scoped amount of time. Project contractors, sometimes called deliverable contractors, are distinct from staff contractors, who are on a service contract and work with the team indefinitely on a variety of projects.
Consider the following:
Update the following:
cg-compliance-docs
Lastly, and not project contractor specific, can we shrink the "reading" section of the onboarding tickets, moving some items to a reference section?
See also: