Verify Platform Orientation materials are up to date for CY24-Q3

[shiragoodman]

User Story

As a Governance team member supporting Platform Orientation, I want to verify that all materials for the orientation sessions are up to date and accurate so VFS teams are learning our current practices and processes.

Assignee: @shiragoodman Peer Reviewer: @it-harrison, @allison0034, @briandeconinck

Description

Earlier in 2024, Governance team pivoted Platform Orientation so that it no longer needs to be hosted live every quarter. Instead, there are recordings of the orientation session that are shared to Platform Website. In order to make sure VFS teams are still learning current practices and processes of the VA.gov Platform crew, we need to check in with all of the Platform teams and COP leads responsible for Platform Orientation content to ensure that their content is still valid.

This ticket will also cover the orientation tickets themselves (New VFS Team Member template and the New VFS Team template ) to verify that the content included within these tickets is also up to date and accurate. The work associated with verifying issue templates are up to date and accurate is applicable to ALL Platform teams/COPs and not just the teams who host orientation sessions.

Note: The General Orientation sessions will be excluded from this ticket as we have another ticket planned for rerecording the sessions and splitting them into 2.

Impacted Artifacts

Tasks

• [x] Create feedback template for Platform teams to complete so that it is easy and convenient for them to communicate their feedback, suggestions, etc.

Tasks for all Platform teams

(all teams below, as well as Platform Security, Product, Reliability, Infrastructure Services, and Service Design

• [ ] Review the New VFS Team Member template and the New VFS Team template
  • [ ] For your practice area, verify all links/references are accurate
  • [ ] For your practice area, verify there are no gaps in what new teams and team members need to know
  • [ ] Make recommendations and/or suggestions for improvement and share with Governance team, if applicable

All of the teams listed below own video content that is part of Platform Orientation. We are asking them to verify their videos are up to date/accurate in addition to the tasks above.

Tasks for Platform Support team

• [ ] Watch the Platform Support overview video and verify content is up to date and accurate
  • If not, please make it a priority to rerecord the video in an upcoming sprint and share with Governance once ready. Share guidance on recording accessible videos.

Tasks for Platform Content team

• [ ] Watch the VFS Orientation to Platform Website video and verify content is up to date and accurate
  • If not, please make it a priority to rerecord the video in an upcoming sprint and share with Governance once ready. Share guidance on recording accessible videos.

Tasks for Design System team

• [ ] Watch the Design System/Forms Library Orientation and verify content is up to date and accurate
  • If not, please make it a priority to rerecord the video in an upcoming sprint and share with Governance once ready. Share guidance on recording accessible videos.

Tasks for Backend COP

• [ ] Watch the Backend Orientation and verify content is up to date and accurate
  • If not, please make it a priority to rerecord the video in an upcoming sprint and share with Governance once ready. Share guidance on recording accessible videos.

Tasks for Frontend COP

• [ ] Watch the Frontend Orientation and verify content is up to date and accurate
  • If not, please make it a priority to rerecord the video in an upcoming sprint and share with Governance once ready. Share guidance on recording accessible videos.

Tasks for Analytics & Insights team

• [ ] Watch the Analytics Orientation and verify content is up to date and accurate
  • If not, please make it a priority to rerecord the video in an upcoming sprint and share with Governance once ready. Share guidance on recording accessible videos.

Tasks for Governance team

• [ ] Watch the Design & Research Orientation, Accessibility Orientation, and QA Orientation (General Orientation will be handled in a separate ticket) and verify content is up to date and accurate
  • If not, please create a ticket using the Governance Team Story / Task Template in gh for updating the slide deck and rerecording the applicable orientation session

Peer Review

To be completed by peer reviewer

• [ ] User story and acceptance criteria are met

Acceptance Criteria

• [x] Governance has contacted all Platform teams and asked them to review Platform Orientation materials
  • See Slack post
• [ ] For the gh templates, Governance team has received feedback from all Platform teams that the content is good as-is or the team has made recommendations for changes
  • [x] Product Team and #89485
  • [x] Infrastructure Services
  • [x] Reliability Team
  • [x] Service Design
  • [x] Governance team
  • [x] Analytics & Insights
  • [x] Platform Content
  • [x] Design System
  • [x] Platform Security
  • [x] Platform Support](https://github.com/department-of-veterans-affairs/va.gov-team/issues/88326) & https://github.com/department-of-veterans-affairs/va.gov-team/issues/89500
  • [x] Backend COP
  • [x] Frontend COP
• [ ] For the videos, Governance team has received feedback from all applicable teams that the video is accurate or the team has plans to rerecord
  • [x] Governance team
  • [x] Analytics & Insights
  • [x] Platform Content
  • [x] Design System
  • [ ] Platform Security
  • [x] Platform Support
  • [ ] Backend COP
  • [ ] Frontend COP

Team Notification

• [ ] Slack post on #platform-governance-team
• [ ] Presentation at Weekly Initiative Meeting
• [ ] No notification needed

How to prepare this issue

Refinement

• [x] Ticket has user story, description, tasks, and acceptance criteria
• [x] Ticket has been sized
• [x] Once all above items are checked, add the 'Ready' label.

  Planning

  If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly

• [x] Ticket has been discussed as a team at Planning
• [x] Ticket has been assigned to appropriate initiative or quarterly epic
• [x] Ticket has been assigned to a Sprint
• [x] Ticket has been moved to the Planned pipeline in the Governance team board
• [x] Ticket as an assignee and peer reviewer

[shiragoodman]

This ticket will be moving into the next sprint. We are still awaiting feedback from most Platform teams so we will keep this ticket open until all feedback is received.

[shiragoodman]

We will move this ticket into the next sprint in order to track teams completion of this work. Many teams shared that they were unable to prioritize this work this sprint.