S2: Requirements Management Plan

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 Programs and Projects

The Requirements Management Planning S establishes the structured approach the project will use to identify, document, analyze, trace, prioritize, and control requirements throughout the project lifecycle. This work results in the development of the Requirements Management Plan (RMP), which defines the processes, tools, roles, and governance needed to ensure requirements are consistently managed and aligned with project objectives.

Once created and approved, the RMP serves as the guiding framework for all requirements-related activities. It outlines how requirements will be captured, how changes will be evaluated and approved, and how traceability will be maintained through artifacts such as the Requirements Traceability Matrix (RTM). The plan ensures that requirements remain visible, validated, and connected to design, development, testing, and acceptance activities. The RMP is used continuously by the project team to support decisionmaking, maintain alignment with impacted parties, and ensure that all requirements are delivered as intended.

For Programs with Agency‑Led Sub‑Projects

Ensure agency-delivered projects under the program align with the RMP and RTM.

WaTech available template: Requirements Management Plan