QA Dashboard - Expand Product QA Dashboards

[pjhill]

Problem Statement

The MVP of Product Quality Assurance Dashboard is complete and rolled out to 10 teams. Platform needs to expand the dashboard to all VFS teams currently participating on VA.gov, and to expand the capabilities of the dashboard.

How might we expand the functionality of our QA Dashboard in ways that VFS teams find more useful than the MVP? How might we expand our dashboard offering to additional VFS teams and their products?

Hypothesis or Bet

With enhanced functionality VFS teams will be able to achieve a better assessment of their quality assurance practice for each of their products. With additional products analyzed and visualized by Product QA dashboards, more VFS teams will be able to participate in assessing their quality assurance practice on VA.gov.

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

• [ ] >90% of VFS team products have corresponding Product QA Dashboards
• [ ] E2E Testing coverage is represented
• [ ] Accessibility testing is reflected
• [ ] QA Standards are reflected

Known Blockers/Dependencies

Requires a Complete Product List

Projected Launch Date

Q2 2022

Launch Checklist

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. VSP Newsletter, 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

[mchelen-gov]

@JoeTice What is the status of this Initiative?

[JoeTice]

Hi @mchelen-gov , the status of this is Not Started - this was a potential item we were hoping to prioritize for last quarter but never got started.

[annekerr49]

@JoeTice - has anything happened on this project since 11/18?