Notice: applying this to your agency.
The IT Project Resources are not meant to replace your agency’s internal project management practices or prescribe how you must operate. Instead, they offer concepts and tools that can strengthen delivery by providing a scalable framework for project level coordination. All project documentation should be maintained throughout each stage in alignment with agency policies and, where applicable, WaTech requirements and oversight expectations.
Develop a comprehensive Master Test Quality Assurance (QA) Plan that defines the standards, processes, and checkpoints required to ensure that all deliverables meet performance, security, accessibility, and compliance expectations. The Master Test QA Plan serves as a proactive quality control mechanism throughout the lifecycle, supporting oversight readiness, impacted parties' confidence, and successful delivery. The plan must outline the validation approach, roles, tools, processes, and acceptance criteria to ensure consistent quality across all stages.
For Programs
Establish enterprise‑level QA standards that apply across shared services, integrations, and environments. Define enterprise testing checkpoints, entry/exit criteria, and oversight alignment. Ensure QA processes support cross‑agency coordination, enterprise risk management, and statewide compliance expectations. Integrate QA activities with IV&V, TQR, and other oversight partners.
For Programs with Agency‑Led Sub‑Projects
Require each agency to define agency‑specific QA responsibilities, test coverage, and data needs. Consolidate agency QA plans into the enterprise QA framework to ensure consistency and traceability. Define how agency QA results will be reported, escalated, and incorporated into enterprise readiness decisions. Ensure agency QA activities align with enterprise testing cycles, shared environments, and oversight checkpoints. Establish expectations for agency participation in walkthroughs, defect triage, and validation sessions.
For Projects
Document project‑specific QA processes, tools, environments, and acceptance criteria. Define test types (unit, integration, regression, performance, UAT) and validation workflows. Identify QA roles and responsibilities within the project team. Ensure alignment with the Test Strategy, Requirements Traceability Matrix (RTM), and oversight expectations. Support defect tracking, prioritization, resolution, and reporting.
The Master Test QA Plan must:
- Define quality objectives and acceptance criteria.
- Identify QA roles, responsibilities, and decision‑making authority.
- Document testing processes (unit, integration, regression, performance, UAT).
- Specify tools, environments, and data requirements for validation.
- Align testing checkpoints with stage gates, governance expectations, and oversight reviews.
- Support defect tracking, prioritization, resolution workflows, and reporting.
The plan should be reviewed and approved prior to building activities and updated as needed. It must be referenced throughout testing, deployment, and stabilization to ensure consistent quality assurance practices.
WaTech available template: Master Test Plan