HKSM

A section of the project or program management plan that explains how requirements will be analyzed, documented, tracked, and controlled throughout the project.

Key Points

• Sets the approach for eliciting, analyzing, documenting, prioritizing, and tracing requirements.
• Clarifies roles, responsibilities, tools, and repositories (e.g., requirements backlog and traceability matrix).
• Defines baselining, change control, approval paths, and acceptance criteria for requirements.
• Describes verification and validation methods and how requirement status will be monitored and reported.

Example

On a healthcare software project, the project manager creates a Requirements Management Plan that specifies using interviews and workshops to elicit requirements, storing them in a single repository, maintaining a requirements traceability matrix, routing changes through the change control board, and validating each requirement through user acceptance testing before release.

PMP Example Question

While planning, the project manager needs to define how requirement changes will be evaluated, approved, and tracked. Which document should be developed or referenced?

1. Scope Management Plan
2. Requirements Management Plan
3. Requirements Traceability Matrix
4. Stakeholder Engagement Plan

Correct Answer: B — Requirements Management Plan

Explanation: The Requirements Management Plan outlines how requirements will be analyzed, documented, tracked, and controlled, including the process for handling requirement changes. The traceability matrix links requirements to deliverables but does not define the process.