Requirements Management Plan

The requirements management plan is part of the project management plan. It specifies how require- ments activities will be conducted throughout the project. Managing requirements activities includes at least:

  • Planning activities such as:
    • Collecting/eliciting
    • Analyzing
    • Categorizing
    • Prioritizing
    • Documenting
    • Determining metrics
    • Defining the traceability structure
  • Managing activities such as:
    • Tracking
    • Reporting
    • Tracing
    • Validating
    • Performing configuration management

The requirements management plan can receive information from:

  • Project charter
  • Development approach
  • Quality management plan

It is related to:

  • Scope management plan It provides information to:
  • Requirements documentation
  • Requirements traceability matrix
  • Quality management plan
  • Risk register

The requirements management plan is an output from the process 5.1 Plan Scope Management in the

PMBOK® Guide – Sixth Edition. It is developed once and does not usually change.

Tailoring tips

Consider the following tips to help tailor the management plan to meet your needs:

  • For smaller projects you can combine the requirements management plan with the scope management plan.
  • If your project involves business analysis, you may want to incorporate information on how business analysis requirements activities and project management requirements activities will interact.
  • You can document the test and evaluation strategy in this For larger projects you may want to have a separate testing plan.
  • If you are using an agile or adaptive development approach you may want to incorporate information on how the backlog will be used to manage and track requirements.


The requirements management plan should be aligned and consistent with the following documents:

  • Development approach
  • Change management plan
  • Scope management plan
  • Release and iteration plan
  • Requirements backlog
Document element  Description
Requirements collection Describe how requirements will be collected or elicited. Consider techniques such as brainstorming, interviewing, observation, etc.
Requirements analysis Describe how requirements will be analyzed for prioritization, categorization, and impact to the product or project approach.
Requirements categories Identify categories for requirements such as business, stakeholder, quality, etc.
Requirements documentation Define how requirements will be documented. The format of a requirements document may range from a simple spreadsheet to more elaborate forms con- taining detailed descriptions and attachments.
Requirements prioritization Identify the prioritization approach for requirements. Certain requirements will be non-negotiable, such as those that are regulatory or those that are needed to comply with the organization’s policies or infrastructure. Other requirements may be nice to have, but not necessary for functionality.
Requirements metrics Document the metrics that requirements will be measured against. For example, if the requirement is that the product must be able to support 150 lb, the met- ric may be that it is designed to support 120 percent (180 lb) and that any design or engineering decisions that cause the product to go below the 120 percent need approval by the customer.
Requirements traceability Identify the information that will be used to link requirements from their origin to the deliverables that satisfy them.
Requirements tracking Describe how often and what techniques will be used to track progress on requirements.
Requirements reporting Describe how reporting on requirements will be conducted and the frequency of such reporting.
Requirements validation Identify the various methods that will be used to validate requirements such as inspection, audits, demonstration, testing, etc.
Requirements configuration management Describe the configuration management system that will be used to control requirements, documentation, the change management process, and the authorization levels needed to approve changes.