Stage 1 (S1): Exit Criteria

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 1 confirms that the initiative has established the foundational structure, scope, and governance needed to move into detailed requirements and design. Core planning elements are in place, impacted parties are aligned on objectives, and the effort is positioned for disciplined execution in Stage 2.

At this point, the initiative has:

  • Defined and approved its scope, objectives, and boundaries
  • Established governance, roles, and decision‑making pathways
  • Completed initial planning artifacts, including high‑level schedules and resource expectations
  • Identified impacted parties and impacted groups, along with engagement and communication needs
  • Documented early risks, dependencies, and constraints
  • Confirmed alignment with enterprise expectations at a conceptual level
  • Validated readiness to begin structured requirements work
  • Governance and decision‑making structures are defined, including roles, responsibilities, and escalation pathways.
  • Scope and objectives are documented and approved, with clear boundaries, assumptions, and constraints.
  • Initial planning artifacts are complete, including the project charter, high‑level schedule, and resource estimates.
  • Intake and prioritization activities are finalized, confirming alignment with enterprise strategy and leadership expectations.
  • Impacted parties and impacted group identification is complete, with engagement and communication expectations established.
  • High‑level risks, dependencies, and constraints are captured, and initial RAIDc entries are documented.
  • Program or project alignment with enterprise standards is confirmed, including architecture, security, accessibility, and data expectations at a conceptual level.
  • Readiness to begin detailed requirements work is validated, with agreement on the approach, tools, and participation needed for Stage 2.

This transition marks a point where the initiative moves from conceptual planning into formal definition. With foundational alignment secured, the team is prepared to begin the disciplined requirements and design activities that shape the future solution in Stage 2.