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.
For Program and Projects
Define the processes that will be used to define, develop, monitor, and control project scope. Focus on the “boundary” of the project, what work is included and what work is excluded from scope. The processes should guide the project on the necessary work, and only the necessary work to prevent scope creep and keep the project on schedule and within budget.
This plan is critical in defining, validating, and controlling project boundaries and ensuring all required work, and only the required work to prevent scope creep.
For Programs with Agency‑Led Sub‑Projects
Coordinate scope across all agency-led sub-projects ensuring there is an understanding of roles and responsibilities for each item of scope and that all work being done by the projects is being tracked at the program level including a knowledge of dependencies and integration points so that future stages (e.g., testing) ensures thorough traceability.
For Projects
Ensure all items defined as in-scope for the project is adequately being tracked by the program. This also means making sure all items defined as out-of-scope are also being tracked by the program so that boundaries are clearly understood.
WaTech available template: Scope Management Plan