We're thrilled to have you join us on this journey! πππ
Our vision is to build and maintain a best-in-class Content Management System that meets the needs of editors, application development teams, and consuming applications in order to empower our users to help Veterans.
The onboarding materials below are organized by 1) chronological time to complete (day one, week one, week two, month one); and main category (why, how, who, what). There's a lot to digest but don't worry, your delivery manager will guide you, you'll have an onboarding buddy to provide support, and we'll also introduce you to your workstream's lead to help with specific things related to your discipline (UX, DevOps, Drupal Engineering, etc). In addition, you'll have the support of the entire team, who have all gone through this process before and are eager to answer any questions that arise. Come back to this ticket any time to refresh your knowledge on a specific topic covered below.
Have fun and we look forward to getting to know you! π
Projected start date: Oct 12, 2021
Onboarding buddy (short check-in meetings the first week): @kevwalsh
[x] How do Agile 6, CivicActions, and Friends From The City work together on this project? Discuss with your delivery manager or product manager.
[x] How do you get secure access to the VA systems you need? PTEMS paperwork is through Liberty and VFS-CMS paperwork through A6. If you're not sure which you should fill out, ask your delivery manager.
[x] Let's start introducing you to the team and key stakeholders. If you're on a meeting where you don't know someone, feel free to kickstart an introduction. Everyone in the ecosystem is friendly and interested in connecting.
When?
[x] Familiarize yourself with our team's shared calendar and add in any known dates. This is where we coordinate upcoming out of office (OOO). Choose "Calendar" = OOO and "Event type" = whatever is relevant.
Week two
The goal for this week is to get you set up with the tools you need to be successful. We will pair you up with a buddy on the project that is in your same discipline to help inform which ones are relevant and which aren't. The most important thing is to get set up is SOCKS as it will give you access to our systems so try to prioritize that.
When?
[x] Check your calendar for invitations to team ceremonies.
All team members need to review the following (note that with the exception of SOCKS, most of the tools will have been setup for you or requested by your delivery manager. This list is for you to verify along the way):
[x] SOCKS proxy request to access VA network tools until you get a PIV card. This is the first priority for week two.
[x] Slack for instant messaging. Your delivery manager should have already requested this for you, but if not, view the request instructions in the link above.
[x] Update your profiles in Slack (in the A6 and DSVA workspaces), add a calendar link
[x] DM to add to appropriate Slack alias groups for the DSVA workspace
[x] @cms-engineers-group
[x] @cms-helpdesk
[x] @platform-cms-team
[x] @sitewide-cms-team
[x] @cms-devops-engineers
[x] You should be in the following slack channels:
[x] A6 workspace = #proj-vagov-team
[x] DSVA workspace = #cms-team
[x] This is a description of other channels that ought to be on your radar. Note that many are going to be dependent on which workstream you're in (DevOps, Helpdesk, UX, etc.). Feel free to join whichever you think will aid you and your work.
[x] Github for issue tracking and document sharing
[x] VA.gov request instructions - Your delivery manager should have already requested this for you so double check with them before submitting a new request.
[ ] Discuss Drupal CMS account administration process with instructional designer, delivery manager or product manager
[ ] Get access to training, staging, and prod environments with instructional designer
[ ] Discuss broken links process with instructional designer
[ ] Discuss Jira reporting with instructional designer
[ ] Discuss Knowledge Base with instructional designer
[ ] The following trainings and additional videos can be found on the Knowledge Base on the Drupal CMS prod and lesser environments that require VA network or SOCKS proxy access. They can be watched without VA network or SOCKS access at the links below.
[ ] Discuss Drupal CMS account administration process with instructional designer, delivery manager or product manager
[ ] The following trainings and additional videos can be found on the Knowledge Base on the Drupal CMS prod and lesser environments that require VA network or SOCKS proxy access. They can be watched without VA network or SOCKS access at the links below.
Welcome to the VFS-CMS Team! π
We're thrilled to have you join us on this journey! πππ
Our vision is to build and maintain a best-in-class Content Management System that meets the needs of editors, application development teams, and consuming applications in order to empower our users to help Veterans.
The onboarding materials below are organized by 1) chronological time to complete (day one, week one, week two, month one); and main category (why, how, who, what). There's a lot to digest but don't worry, your delivery manager will guide you, you'll have an onboarding buddy to provide support, and we'll also introduce you to your workstream's lead to help with specific things related to your discipline (UX, DevOps, Drupal Engineering, etc). In addition, you'll have the support of the entire team, who have all gone through this process before and are eager to answer any questions that arise. Come back to this ticket any time to refresh your knowledge on a specific topic covered below.
Have fun and we look forward to getting to know you! π
Projected start date: Oct 12, 2021
Onboarding buddy (short check-in meetings the first week): @kevwalsh
Day one
How?
Who?
What?
Week one
The goals of this week are: 1) get background paperwork completed as quickly as possible and 2) start gaining context for what we're doing and why
Why?
How?
Who?
When?
Week two
The goal for this week is to get you set up with the tools you need to be successful. We will pair you up with a buddy on the project that is in your same discipline to help inform which ones are relevant and which aren't. The most important thing is to get set up is SOCKS as it will give you access to our systems so try to prioritize that.
When?
What products do we support?
All team members need to review the following (note that with the exception of SOCKS, most of the tools will have been setup for you or requested by your delivery manager. This list is for you to verify along the way):
@cms-engineers-group
@cms-helpdesk
@platform-cms-team
@sitewide-cms-team
@cms-devops-engineers
#proj-vagov-team
#cms-team
Onboarding for Developers
Onboarding for DevOps members
adhoc-vetsgov-devops
group.Onboarding for Helpdesk members
Onboarding for Instructional Design members
Onboarding for Product Management members
Onboarding for UX members
Month one
By this point you should have enough context and access to be able to start contributing. Work with your team to identify specific issues to focus on.
Who?
What?
Month two
What additional tools do you need access to?