Task: Communicate the Requirements Management Plan
The standard project deliverables are defined within requirements management plan.
Disciplines: Requirements Management Discipline
Purpose
The requirements management plan is used to set expectations of project deliverables to stakeholders. It is also used to document any exceptions in the event that it is determined that a deliverable is not needed.
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    		Optional:
    • None
    Outputs
      Main Description

      A requirements management plan is useful to the entire project team for:

      • Defining the requirements prioritization process
      • Defining the standard project deliverables for which the BA is responsible
      • Noting any project deliverables that will be excluded
      • Setting expectations of how requirements will be managed
      Steps
      Review the requirements management plan with stakeholders
      • Schedule a meeting via conference call or face to face to review the requirements management plan.
      • Review list of standard project deliverables.
      • Explain to stakeholders that if the team agrees that a standard deliverable is not needed, it will be necessary to record the decision in the RMP and obtain stakeholder signoff.
      In the event that any standard deliverables are to be excluded, secure signoff from project Stakeholders
      • If any deliverables are to be excluded, proof of the stakeholder’s approval is to be obtained electronically or hard copy.
      • Stakeholder approvals must be stored within the project’s SharePoint site.

      Version and Release

      Unified Life Cycle (ULC): 5.1, November 3, 2014
      Phase Gates: 1.1, May 27, 2014
      Process Engineering Process (PEP): 1.1, May 27, 2014