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.
Stage 4 ensures that governance, integration, support, and communication strategies are fully established and that all impacted groups are prepared for go‑live activities. During this phase, the project or program team must demonstrate readiness across technical environments, business processes, vendor coordination, and impacted parties engagement.
This stage confirms that:
- Implementation roles are assigned and acknowledged.
- Cutover and rollback strategies are defined.
- QA readiness is certified.
- Vendor support and operational continuity plans are in place.
- Impacted group communication and change management plans are finalized.
For Programs
Must demonstrate that implementation roles are assigned, cutover strategies are defined, and Test QA readiness is certified. This stage also confirms that vendor coordination, impacted group engagement, and operational support structures are fully established. Programs are responsible for: Finalizing enterprise deployment strategies and cutover plans Validating system configurations across shared environments. Confirming readiness of enterprise support structures, including service desk, monitoring, and escalation paths. Coordinating readiness activities across all participating agencies and sub‑projects. Ensuring enterprise‑level risks, dependencies, and contingencies are documented and mitigated
For Programs with Agency‑Led Sub‑Projects
Stage 4 ensures that each agency sub‑project has completed its readiness activities and is aligned with enterprise expectations. Agencies must:
- Review and confirm their implementation schedule in alignment with enterprise milestones.
- Update change management and communication plans to reflect agency‑specific needs.
- Validate system interfaces and integration readiness across local and enterprise environments.
- Define vendor support expectations and escalation paths for agency‑specific deployments.
- Participate in cutover strategy planning and rollback scenario development.
- Complete operational readiness checklists and confirm support team activation.
- Submit Test QA readiness assessments aligned with WaTech oversight criteria.
- Coordinate impacted parties engagement and messaging cadence for go‑live and stabilization.
Enterprise programs must consolidate all agency‑level inputs into a unified readiness framework that supports coordinated implementation and oversight review.
For Projects
Finalize project‑specific deployment and cutover plans. Validate system configurations and confirm environment readiness. Prepare operational support structures, including help desk workflows and escalation procedures. Ensure QA sign‑off, readiness assessments, and contingency plans are complete. Confirm that all impacted parties understand their roles during go‑live.
To exit Stage 4: By the end of this stage, the program or project must demonstrate:
- A complete and validated deployment and cutover plan.
- Confirmed readiness across technical, business, and operational teams.
- Clear execution roles and communication protocols.
- Documented contingencies and rollback strategies.
- Alignment with WaTech oversight expectations.
- Confidence from impacted groups that the solution is ready for production transition.