[Forms System] Q3 2022 Initiative: Prepare to transition Forms Library Team deliverables and handoffs

[taylorkaren]

Problem Statement

There is a potential for a contract transition to take place in mid-September, 2022, that will require the Forms Library Team to transition the work done to date on the new VA Forms System Core (VAFSC) and hand off ongoing support work for the current Forms Library.

How might the Forms Library Team plan for a smooth transitions, should it be needed, and also plan for continuing to work on all things forms should the transition not be needed?

Hypothesis or Bet

The hypothesis/bet for this initiative is that by identifying at the beginning of Q3 the VAFSC deliverables and current Forms Library handoffs that would be needed in a transition scenario, we will be able to work towards having those items in a good state to transition as of September 1, 2022.

See the Q3 FLT Roadmap Brainstorm Mural board for details on VAFSC Deliverables and current Forms Library Handoffs.

Definitions:

• VAFSC Deliverables: VAFSC code and artifacts that are in a known state and could be picked up at the time of transition or at a later time to continue work on the system.
• Current Forms Library Handoffs: Ongoing activities for the current Forms Library that would need to be assumed at the time of transition so that there is no gap in providing support for this system.

We will know we're done when... ("Definition of Done")

• A transition is needed AND the VAFSC Deliverable and current Forms Library Handoff items on the Q3 FLT Roadmap Brainstorm Mural board have been transitioned to the designated team(s) who will be taking over the work.

Known Blockers/Dependencies

• This work is dependent on the need for a transition of work to take place prior to the September 11, 2022, Spike team contract expiration. If a transition does not need to take place, this initiative will not be applicable.

Projected Launch Date

• Should a transition be needed, work should be completed by September 9, 2022, as that is the last business day prior to the September 11, 2022, Spike team contract expiration.

Launch Checklist

Guidance (delete before posting)

This checklist is intended to be used to help answer, "is my Platform initiative ready for launch?". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given Platforminitiative. All links or explanations can be provided in Required Artifacts sections. The items that can be skipped are marked as such.

Keep in mind the distinction between Product and Initiative --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. VSP Product Terminology for details.

Is this service / tool / feature...

... tested?

• [ ] Usability test (TODO: link) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it.
  • [ ] ... and issues discovered in usability testing have been addressed.
  • Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing.
• [ ] End-to-end manual QA or UAT is complete, to validate there are no high-severity issues before launching
• [ ] (if applicable) New functionality has thorough, automated tests running in CI/CD

... documented?

• [ ] New documentation is written pursuant to our documentation style guide
• [ ] Product is included in the List of VSP Products
  • List the existing product that this initiative fits within, or add a new product to this list.
• [ ] Internal-facing: there's a Product Outline
• [ ] External-facing: a User Guide on Platform Website exists for this product/feature tool
• [ ] (if applicable) Post to #vsp-service-design for external communication about this change (e.g. customer-facing meetings)

... measurable

• [ ] (if applicable) This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it.
  • For help, see: Analytics team
• [ ] This change has an accompanying VSP Initiative Release Plan.

When you're ready to launch...

• [ ] Conduct a [go/no-go] (https://vfs.atlassian.net/wiki/spaces/AP/pages/1670938648/Platform+Crew+Office+Hours#Go%2FNo-Go) when you're almost ready to launch.

Required Artifacts

Documentation

• PRODUCT_NAME: directory name used for your product documentation
• Product Outline: link to Product Outline
• User Guide: link to User Guide

Testing

• Usability test: link to GitHub issue, or provide reason for skipping
• Manual QA: link to GitHub issue or documented results
• Automated tests: link to tests, or "N/A"

Measurement

• Success metrics: link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping
• Release plan: link to Release Plan ticket

TODOs

• [ ] Convert this issue to an epic
• [ ] Add your team's label to this epic
• [ ] Add this initiative to the Digital Experience Product Board using these instructions

[raywangoctova]

@humancompanion-usds Can you add/tag Q3 FY22 to the milestone for this issue? This is required by Jeff for the DE product board.

[humancompanion-usds]

Transition to the Design System Team is complete.