Support -- Launch readiness tooling and process for applications

[gunsch]

Description

As a VFS app creator, I need a clear set of criteria for the steps I need to take in preparation for launching on VA.gov.

Problem

We currently have the DSVA handbook that helps guide VFS app creators through launching products on VA.gov, but after going through our initial set of VFS teams we've found some gaps and inefficiencies in the Pre-launch activities guide.

Goal

• Empower DSVA to make clear determinations about letting products go live on VA.gov by providing VFS teams with well-written criteria for what they need to accomplish before launch.
  • This should encompass standards, reviews, and other requirements that an application team needs to meet before releasing an application publicly for use by veterans. These might include things such as coding standards, technical reviews, automated monitoring and testing, etc.

AC

• [ ] Define checklist of requirements for application launches, with details solicited from stakeholder VSP teams
• [ ] For each requirement, audit the process we currently have in place, establishing MVP processes where missing.
• [ ] Develop a process for iterating on these requirements over time, and how updates are applied to existing/future application teams
• [ ] For each requirement, document a roadmap for any automated tooling or infrastructure needed to support enforcement of that requirement and/or accelerated application team development toward that requirement

[rroueche]

Adjusted the title of this, bc I think this Epic is super important, and the related tickets I think are beyond MVP level.

[rroueche]

I think this is a Super Epic that encompasses a lot of work we're already working on:

• Onboarding
• The product development checklist
• How we incorporate the checklist into incremental check-ins (not a pre-launch thing)
• A potential go/no go meeting where we look at the things that should absolutely block launch and empower DSVA to say yes/no officially
• A handoff of those ^ things to Tools and Operations teams so they can build it into the Merge and Feature Flag tools, so that it's not up to DSVA to say no, but rather folks really can't go live if certain criteria aren't met.