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.
A cutover and rollback strategy documents the approach on how the project will transition from a current/legacy system to new/updated system with minimal disruption. It provides a clear understanding of the approach that will be taken if problems are encountered, or if deployment/transition fails. Define cutover steps, timing, roles, and contingency actions to ensure a controlled transition. Outline the methodology, timeline, and tasks required to transition from old systems to new. Include go/no-go decision criteria as well as the checkpoints required to ensure successful deployment.
For Programs
Develop the enterprise cutover strategy and rollback framework.
For Programs with Agency Sub‑Projects
Agencies contribute local cutover stages, staffing plans, and rollback criteria. Program team consolidates into an enterprise-level cutover and rollback strategy.
For Projects
Finalize project‑specific cutover steps, timing, and contingency actions.
WaTech available template: Cutover and Rollback Strategy