Requirements Traceability Matrix: Ensuring Business Value Through Traceability

PMBOK v8 Definition

The requirements traceability matrix (RTM) is a grid that links product requirements from their origin to the deliverables that satisfy them. Its implementation helps to ensure that each requirement adds business value by linking it to the business and project objectives. The matrix provides a means to track requirements throughout the project life cycle, helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project, and provides a structure for managing changes to the product scope.

Why It Matters for the Exam

The RTM appears frequently in PMI exam questions about scope management, requirements validation, and change control. Expect questions testing your understanding of how the RTM connects requirements to business objectives, project scope, WBS deliverables, and testing activities. The exam often tests your ability to identify what the RTM contains versus what belongs in other documents like the requirements management plan.

Key Points to Remember (for the exam)

• Primary Purpose: Ensures each requirement adds business value by linking it to business and project objectives
• Life Cycle Function: Tracks requirements throughout the project life cycle from origin to delivery
• Delivery Assurance: Confirms that approved requirements in requirements documentation are delivered at project end
• Change Management: Provides a structure for managing changes to the product scope
• Core Content: Includes business needs, opportunities, goals, objectives, project objectives, project scope, WBS deliverables, product design, product development, test strategy, test scenarios, and high-level to detailed requirements
• Typical Attributes: Unique identifier, textual description, rationale for inclusion, owner, source, priority, version, current status, status date, stability, complexity, and acceptance criteria
• Key Distinction: The RTM is a grid (tool), while the requirements management plan describes how traceability will be structured

Typical PMI Exam Example

A project manager is reviewing requirements with stakeholders. Several new requirements have been added during the project. The project manager needs to verify that all approved requirements will be delivered. Which document should the project manager use to track these requirements from their origin to the deliverables that satisfy them? Answer: The requirements traceability matrix, because it ensures approved requirements are delivered at project end and provides structure for managing scope changes.

PMI Exam Traps

• Trap: Confusing the RTM with the requirements management plan

  • Reality: The RTM is the grid linking requirements to deliverables; the requirements management plan describes how traceability activities will be performed

• Trap: Thinking the RTM only tracks requirements during planning

  • Reality: The RTM tracks requirements throughout the entire project life cycle

• Trap: Assuming the RTM only contains technical requirements

  • Reality: The RTM includes business needs, opportunities, goals, objectives, project objectives, and test scenarios

• Trap: Believing the RTM is only for scope management

  • Reality: The RTM supports scope, quality (test strategy), and change management

Important PMI Connections

Quick Review Questions

1. What is the primary purpose of implementing a requirements traceability matrix?

2. Which attributes are typically recorded in the requirements traceability matrix?

3. How does the requirements traceability matrix support change management?

4. What is the difference between the requirements traceability matrix and the requirements management plan regarding traceability?

5. Which items are included in the requirements traceability matrix (list at least five)?

PMBOK v8 Reference

Section 4 – Inputs and Outputs (Requirements Traceability Matrix)