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.
Completion of Stage 2 confirms that the initiative has a fully defined and validated blueprint for the future solution. Requirements are complete, the design is aligned with enterprise expectations, and the effort is ready to transition from definition into technical preparation and build planning.
At this point, the initiative has:
- Approved and traceable business, functional, and technical requirements
- A validated solution design aligned with enterprise architecture, security, accessibility, and regulatory standards
- Completed cross‑agency and impacted group reviews with documented sign‑off
- Procurement readiness (where applicable), including finalized specifications and supporting documentation
- Updated RAIDc logs reflecting design‑phase risks, assumptions, issues, decisions, and changes
- Incorporated security, privacy, data, accessibility, and equity considerations into requirements and design artifacts
- Completed all required oversight documentation and submitted it through the appropriate channels
This transition marks a point where the initiative moves from defining what the solution must be to preparing how it will be built. With a clear, enterprise‑aligned design in place, the team is ready to begin the technical setup, environment preparation, and configuration planning that occur in Stage 3.