This initiative was added to the Q4 QA Standards plan on 9/13
Problem Statement
Currently the QA practice area has no clearly defined standards for the Collaboration Cycle, which leaves the QA Standards team without a good framework to provide feedback during Collaboration Cycle reviews, and leaves VFS teams without a way to understand what VA.gov's expectations are for them in this area.
How might we provide VFS teams with better guidance for meeting quality standards and better ensure a quality experience for our end users?
Hypothesis or Bet
By defining, documenting and communicating standards for key quality assurance practices on the VA.gov platform for review in the Collaboration Cycle, we believe that VFS teams will have a better understanding of the Platform expectations for quality assurance practice. Additionally, VFS teams will be able to plan more effectively for how to meet QA practice area standards throughout their development lifecycle.
We will know we're done when... ("Definition of Done")
We have a documented list of standards that VFS teams can use to assess their products prior to Collab Cycle reviews
Collab Cycle reviews utilize these standards to measure whether a product is meeting quality standards
Known Blockers/Dependencies
Governance team sign-off for the updated documentation.
Coordination of phasing in the QA standards for the overall CC Experience Standards
[ ] (if applicable) Post to #vsp-service-design for external communication about this change (e.g. VSP Newsletter, customer-facing meetings)
... measurable
[x] Measurements for the standards are tracked from both before/after launch to determine if there is an improvement in compliance to those measurements based on the release
PRODUCT_NAME: Documentation is the primary work product from this initiative. Documentation will be integrated into Collaboration Cycle Experience Standards documentation as well as Quality Assurance / Testing documentation on the Platform Website.
This initiative was added to the Q4 QA Standards plan on 9/13
Problem Statement
Currently the QA practice area has no clearly defined standards for the Collaboration Cycle, which leaves the QA Standards team without a good framework to provide feedback during Collaboration Cycle reviews, and leaves VFS teams without a way to understand what VA.gov's expectations are for them in this area.
How might we provide VFS teams with better guidance for meeting quality standards and better ensure a quality experience for our end users?
Hypothesis or Bet
By defining, documenting and communicating standards for key quality assurance practices on the VA.gov platform for review in the Collaboration Cycle, we believe that VFS teams will have a better understanding of the Platform expectations for quality assurance practice. Additionally, VFS teams will be able to plan more effectively for how to meet QA practice area standards throughout their development lifecycle.
We will know we're done when... ("Definition of Done")
Known Blockers/Dependencies
Projected Launch Date
3/29/22 (End of Sprint 74)
Launch Checklist
Is this service / tool / feature...
... documented?
... measurable
When you're ready to launch...
Required Artifacts
Documentation
PRODUCT_NAME
: Documentation is the primary work product from this initiative. Documentation will be integrated into Collaboration Cycle Experience Standards documentation as well as Quality Assurance / Testing documentation on the Platform Website.Testing
NOT APPLICABLE
Measurement
TODOs