Requirements Management Plan as Business Analysis Plan

PMBOK v8 Definition

The Requirements Management Plan is a component of the program or project management plan that describes how requirements will be analyzed, documented, and managed. According to Business Analysis for Practitioners: A Practice Guide, some organizations refer to the requirements management plan as a business analysis plan. This plan details how requirements activities will be planned, tracked, and reported, including configuration management activities, prioritization processes, metrics, and traceability structures.

Why It Matters for the Exam

This concept appears frequently on the PMI exam because it tests your understanding of the relationship between business analysis and project management planning. Expect questions that present scenarios where you must identify the correct plan name or distinguish between requirements management and business analysis terminology. The exam tests whether you know that these terms are interchangeable in practice.

Key Points to Remember (for the exam)

• Interchangeable Terminology: Some organizations call the requirements management plan a business analysis plan – this is a direct PMBOK v8 statement from the Business Analysis for Practitioners guide.

• Core Components: The plan includes how requirements activities will be planned, tracked, and reported – these three verbs are frequently tested.

• Configuration Management: The plan addresses how changes will be initiated, how impacts will be analyzed, how changes will be traced, tracked, and reported, and the authorization levels required to approve changes.

• Prioritization Process: The plan must define the requirements prioritization process – exam questions test whether you know this is part of the plan, not a separate document.

• Metrics and Traceability: The plan specifies metrics that will be used with rationale, plus the traceability structure that reflects requirement attributes captured on the requirements traceability matrix.

• Plan Location: The requirements management plan is a component of the program or project management plan – it is not a standalone document.

• Requirement Quality: Before baselining, requirements must be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders.

Typical PMI Exam Example

A project manager is developing the project management plan for a software implementation. The business analyst asks which document will describe how requirements changes will be initiated and authorized. The project manager should reference the requirements management plan (also known as the business analysis plan), which contains configuration management activities including change initiation and authorization levels.

PMI Exam Traps

• Trap: Confusing the requirements management plan with the scope management plan

• Reality: The requirements management plan focuses on how requirements are analyzed and managed; the scope management plan focuses on how scope is defined, validated, and controlled

• Trap: Thinking the business analysis plan is a separate, distinct document

• Reality: According to PMBOK v8, some organizations refer to the requirements management plan as a business analysis plan – they are the same document

• Trap: Assuming the requirements traceability matrix is the same as the requirements management plan

• Reality: The traceability matrix is an output of collecting requirements; the requirements management plan describes the traceability structure that the matrix will follow

• Trap: Believing requirements prioritization is done informally or outside the plan

• Reality: The requirements prioritization process must be defined in the requirements management plan

Important PMI Connections

Quick Review Questions

1. What are the five components that must be included in a requirements management plan according to PMBOK v8?

2. In which document would you find the authorization levels required to approve changes to requirements?

3. What is the relationship between a requirements management plan and a business analysis plan?

4. Before baselining requirements, what six characteristics must they possess?

5. Which part of the requirements management plan describes how requirements attributes will be captured?

PMBOK v8 Reference

Section 2.49 - Business Analysis for Practitioners: A Practice Guide [2] – Requirements Management Plan components and terminology