Requirements Traceability Matrix: Linking Requirements to Business Value

PMBOK v8 Definition

The requirements traceability matrix is a grid that links product requirements from their origin to the deliverables that satisfy them. It 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 requirements traceability matrix appears frequently in PMI exam questions about scope management, requirements validation, and change control. Expect questions testing your understanding of what attributes are recorded in the matrix and how it connects business needs to project deliverables. Common question types include scenario-based questions asking which document to use for tracking requirement changes or verifying requirement completion.

Key Points to Remember (for the exam)

• Main Purpose: Links product requirements from their origin to the deliverables that satisfy them
• Core Function: Ensures each requirement adds business value by linking it to business and project objectives
• Critical Attributes: Unique identifier, textual description, rationale for inclusion, owner, source, priority, version, current status (active, canceled, deferred, added, approved, assigned, completed), and status date
• Additional Attributes: Stability, complexity, and acceptance criteria (help ensure stakeholder satisfaction)
• Traceability Links: Business needs/opportunities/goals/objectives → Project objectives → Project scope and WBS deliverables → Product design → Product development → Test strategy and test scenarios
• Key Output: Provides structure for managing changes to product scope
• Common Confusion: The requirements traceability matrix is NOT the same as requirements documentation—the matrix tracks and links requirements, while documentation describes them

Typical PMI Exam Example

A project manager is reviewing a change request to add a new feature. To determine which project objectives and WBS deliverables will be affected, the project manager should consult the requirements traceability matrix. This document shows the linkage from the new requirement through project objectives, WBS deliverables, product design, and test cases.

PMI Exam Traps

• Trap: Confusing requirements traceability matrix with requirements documentation

  • Reality: Requirements documentation describes the requirements; the traceability matrix tracks and links them to deliverables

• Trap: Thinking the matrix only tracks requirements during planning

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

• Trap: Assuming the matrix only contains technical requirements

  • Reality: The matrix includes business needs, opportunities, goals, objectives, and project objectives

• Trap: Believing the matrix is optional for small projects

  • Reality: The matrix helps ensure all requirements add business value and are delivered—critical for any project

Important PMI Connections

Quick Review Questions

1. What are the seven typical attributes recorded for each requirement in the requirements traceability matrix?

2. How does the requirements traceability matrix help ensure that each requirement adds business value?

3. What is the difference between requirements documentation and the requirements traceability matrix?

4. During which project life cycle phase is the requirements traceability matrix used?

5. Which document would you consult to determine what WBS deliverables are affected by a proposed requirement change?

PMBOK v8 Reference

Section 4 – Inputs and Outputs, Figure 4-3: Example of a Requirements Traceability Matrix