New VFS Team Member Template [Chris Valarida]

djmunoz1 commented 1 month ago

Welcome and Introduction

Welcome to the Department of Veterans Affairs (VA) Veteran Facing Services (VFS) team!

As a new VFS team member, you will be working in the web ecosystem we call the VA.gov Platform (or "The Platform," for short). The tasks on this list are designed to get you up to speed on the role of Platform, making it easier for you to do your job.

Because the VA is a huge organization that serves millions, the Platform it runs on is equally big, complex, and multilayered. Most people find that even learning the basics for their own practice area entails a significant learning curve. The tasks on this checklist will help you acquire those basics as quickly and efficiently as possible.

User Story

As a new VFS team member, I need to complete onboarding activities so I can successfully work on my project and support the VA.gov Platform.

How to fill out this ticket

[ ] Add your name to the ticket title
[ ] Complete the Onboarding Checklist below
[ ] Under Get set up for your practice area, you only need to complete the items for your role
[ ] You can close this ticket when all items are completed in the Onboarding Checklist and the Platform Checklist

Onboarding Checklist

Share your info with Platform

[ ] Complete the fields below:
- Name: Chris Valarida
- Pronouns (e.g. she/her): he/him
- Role: Software Engineer
- Email: chris@themostudio.com, chris.valarida@va.gov
- GitHub handle*: cvalarida
- Start date: 7/22/2024
- VFS Team: SSiT

*Providing your GitHub handle will allow Platform to provide you access to the necessary GitHub repos.

General

[ ] Watch the General orientation recording
[ ] Update your Slack profile
[ ] Watch VA.gov overview video for an overview of VA.gov
[ ] Watch VFS Orientation for Platform Website video
[ ] Watch the Platform Support overview video
[ ] Review the Getting help from the Platform in Slack guidance
[ ] Review Welcome documentation
[ ] Review Support Overview documentation
[ ] Review the guidance on Submitting a feature request
[ ] Request Access to Tools
[ ] Confirm that you have access to the VA GitHub Organization
- Note: Membership in the VA Github Organization is a prerequisite for getting access to vets.gov-write and access to many commonly-used repositories. Platform will not be able to complete this task if you are not a member of the VA GitHub Organization.
[ ] Opt out of Google Analytics on all of your browsers on your work machines, personal machines (if you are not a Veteran yourself using the site for your own applications), and mobile devices
Norms and standards
[ ] Review guidance on the Platform Satisfaction Survey
Working on the platform
[ ] Review the Platform Principles
[ ] Review the GitHub Markdown Cheatsheet to learn the syntax for formatting documents in GitHub
[ ] Review the Digital Modernization Strategy
[ ] Review the Web Brand Consolidation documentation
[ ] Review the Collaboration Cycle documentation on Platform Website
[ ] Are you a Veteran? Consider adding your name to the Veterans willing to help VA teams with product testing document

Get set up for your practice area

Product Managers & Delivery Managers

[ ] Schedule a PM intro via Calendly with Shira Goodman (Platform Governance Team PM).
[ ] If your team is new, please complete the New VFS Team ticket. If you're joining an existing team, you can skip this step.
[ ] Watch the Analytics orientation recording
[ ] Watch the Accessibility orientation recording
[ ] Watch the QA orientation recording

Off-boarding of teammates

[ ] Review process for when a teammate leaves

Platform Checklist

The items in this checklist are for Platform to complete. If you are ready to close the ticket and the Platform Checklist section has not been completed, please reach out to Platform via the guidance provided in Getting help from Platform in Slack.

[x] New VFS team member has been added to the VFS Team Roster located in Atlas
[x] New VFS team member has been added to the vets.gov-write GitHub team

bdech commented 1 month ago

@djmunoz1

@cvalarida is not a member of the VA GitHub Organization which is a pre-requisite to being added to Atlas and vets.gov-write. Please refer to this guidance on Platform Website to get access to the VA GitHub Organization, and follow up in this ticket when you have been added to the VA GitHub Organization.

I am going to remove the platform-tech-team-support label for now. Once Chris has joined the VA GitHub org, please re-add the label, and tag me.

djmunoz1 commented 1 month ago

Hi tried this yesterday @bdech but the link is broken. I'll ping platform support, thanks

bdech commented 1 month ago

Hi Dawn, I see that Chris is now part of the VA GitHub org. I can start actioning this request. Can you please elaborate on the team name provided? There is a lot of acronyms in the VA space and I'm not familiar with this one, SSiT.

djmunoz1 commented 1 month ago

Hi @bdech sure, the team was renamed last year under Tom Black as PO -- SSiT == Secure Sign-In Transition.

bdech commented 1 month ago

Do you know what the team name was before the change? I'm not able to find Secure Sign-in Transition in Atlas. Could it possibly be under login.gov adoption?

djmunoz1 commented 1 month ago

yep, that's the previous name.

bdech commented 1 month ago

Platform Checklist complete

bdech commented 1 month ago

Hey Dawn,

Chris is all setup and ready to go.

One thing I wanted to note. Since the team name has changed we will want to update Atlas with that information. Can you or possibly your PO fill out this New VFS Team Ticket so can ensure we have the most up-to-date information on the team.

Thanks.

djmunoz1 commented 1 month ago

GM, we checked in with the PO and filled out the new form #89293. Please let me know if anything further is needed or there are certain tasks the team should own.

bdech commented 1 month ago

Thanks Dawn. I have updated the team information in Atlas.

department-of-veterans-affairs / va.gov-team