|
Agencies retain full authority over their delivery approach and may use this framework to supplement and strengthen their practices where it is beneficial to ensure successful delivery. |
For Programs: Stage 2 is where the technical rubber meets the road. This is the point in the lifecycle where strategic intent becomes engineered reality. Requirements are transformed into concrete, build‑ready specifications, and the solution architecture is shaped using industry‑standard SDLC practices and enterprise architecture principles. This stage ensures that the program or project is grounded in technical rigor, aligned with statewide standards, and designed for long‑term scalability, security, and sustainability.
For initiatives that impact external customers, agencies should ensure that customer‑centric design principles are actively applied, with deliberate attention to how end‑user needs and customer experience are incorporated into the program or project.
Stage 2 defines enterprise requirements, solution architecture, and compliance strategies to ensure the program meets business, technical, and regulatory expectations. This stage establishes the foundation for system design, integration planning, and governance alignment. Programs must demonstrate that all requirements are traceable, architecture is scalable, and compliance strategies are in place to support secure and effective implementation.
For programs that include agency-led sub-projects, Stage 2 ensures that each agency sub-project has:
- Documented functional and technical requirements that align with enterprise goals.
- Contributed to a unified architecture that supports shared services and agency-specific configurations.
- Identified compliance needs and security controls that reflect both local and statewide standards.
- Defined data governance roles, migration paths, and stewardship responsibilities.
- Developed management plans tailored to agency structures and impacted groups.
- Assessed accessibility and equity impacts to ensure inclusive service delivery.
Enterprise programs must consolidate agency-level inputs into a unified design framework that supports coordinated implementation and oversight review.
For Projects: Stage 2 defines the “what” and “how” of the solution. It captures detailed business, functional, and technical requirements and translates them into a validated design that aligns with the approved scope, budget, and timeline. This stage ensures that the solution is feasible, build-ready, and aligned with impacted group expectations and WaTech enterprise standards.
For projects under WaTech Oversight, Stage 2 is a critical checkpoint. It provides the documentation and traceability needed to support design reviews, procurement readiness, and build planning.
Stage Completion Criteria
By the end of Stage 2, the project should be able to demonstrate:
- Approved and traceable business, functional, and technical requirements
- A validated solution design that aligns with enterprise architecture and WaTech standards
- Impacted group sign-off on requirements and design artifacts
- Procurement readiness (if applicable) with finalized specifications
- Updated RAIDc logs reflecting design-phase risks, decisions, and changes
- Oversight documentation updated and uploaded to Salesforce (if required)