Study guide
9.2 Requirements Traceability Matrix
CAPM Certified Associate in Project Management Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & CAPM Exam Overview
1.1 About the CAPM Exam 1.2 PMBOK 7th Edition Overview 1.3 Exam Content Outline (ECO) 1.4 CAPM vs. PMP: Understanding the Differences
2 Chapter 2: Project Life Cycles and Processes (Domain 1, Tasks 1-2)
2.1 Projects, Programs, and Portfolios 2.2 Project Life Cycle Phases 2.3 The Five Process Groups 2.4 The Ten Knowledge Areas
3 Chapter 3: Project Management Planning (Domain 1, Task 2)
3.1 The Project Management Plan 3.2 Scope Management and the WBS 3.3 Schedule Management 3.4 Cost Management and Earned Value 3.5 Quality Management
4 Chapter 4: Project Roles, Responsibilities, and Ethics (Domain 1, Tasks 3-4)
4.1 Project Roles and Responsibilities 4.2 Leadership and Emotional Intelligence 4.3 Risk Management Fundamentals 4.4 PMI Code of Ethics and Professional Conduct 4.5 Problem-Solving Tools and Techniques
5 Chapter 5: Resource, Communication, and Stakeholder Management (Domain 1, Tasks 2-3)
5.1 Resource Management 5.2 Communications Management 5.3 Stakeholder Management 5.4 Procurement Management 5.5 Issues, Risks, Assumptions, and Constraints
6 Chapter 6: Predictive, Plan-Based Methodologies (Domain 2)
6.1 When to Use a Predictive Approach 6.2 WBS, Work Packages, and Activity Definition 6.3 Predictive Project Controls and Artifacts 6.4 Critical Path and Schedule Calculations
7 Chapter 7: Agile Frameworks and Methodologies (Domain 3, Tasks 1-3)
7.1 When to Use an Adaptive (Agile) Approach 7.2 The Scrum Framework 7.3 Kanban, XP, and SAFe 7.4 Agile Planning, Estimation, and Metrics 7.5 Agile Project Controls and Artifacts
8 Chapter 8: Business Analysis Roles and Stakeholder Communication (Domain 4, Tasks 1-2)
8.1 Business Analysis Roles and Responsibilities 8.2 Stakeholder Communication in Business Analysis 8.3 Business Case and Needs Assessment
9 Chapter 9: Requirements Gathering and Product Roadmaps (Domain 4, Tasks 3-4)
9.1 Requirements Gathering Approaches 9.2 Requirements Traceability Matrix 9.3 Product Roadmaps
10 Chapter 10: BA Methodologies and Requirements Validation (Domain 4, Tasks 5-6)
10.1 Business Analysis in Predictive and Agile Approaches 10.2 Acceptance Criteria and Requirements Validation 10.3 Business Analysis Tools and Techniques Summary
9.2 Requirements Traceability Matrix
Key Takeaways Explain This Topic AI
The Requirements Traceability Matrix (RTM) links every requirement from its business origin through design and deliverables to its test cases
Traceability enables impact analysis — when a change is proposed, the RTM shows which deliverables, tests, and stakeholders are affected
Forward traceability links requirements forward to design and tests; backward traceability links them back to business needs; bi-directional combines both
The RTM prevents both scope creep/gold plating (no deliverable without a requirement) and missed scope (no requirement without a deliverable)
In agile, traceability flows through the product backlog: business objective → epic → user story → acceptance criteria → test
Last updated: June 2026
What Traceability Means
The Requirements Traceability Matrix (RTM) is a grid that links each requirement throughout the project life cycle. Traceability is the ability to follow one requirement from its source (a business need) through its implementation (a deliverable) to its verification (a test case). A well-maintained RTM guarantees four things the CAPM exam repeatedly tests:
Every requirement has a documented business justification.
Every deliverable maps back to an approved requirement.
Every requirement is verified by at least one test.
The full impact of any proposed change can be assessed quickly.
The RTM is created during the requirements phase and is kept current throughout the project — it is a living document, not a one-time artifact.
RTM Structure
A typical RTM contains these columns:
- Column Purpose
- Requirement ID Unique identifier (REQ-001)
- Description What the requirement states
- Source / Business Need The objective or stakeholder it traces to
- Priority High / Medium / Low (often MoSCoW)
- Status Active, approved, in progress, deferred, deleted
- Design Reference Design element that addresses it
- Deliverable Project output that fulfills it
- Test Case ID Test that verifies it
- Test Status Not run, passed, failed
- Owner Person accountable for it
- Worked Example
- Req ID Description Source Priority Design Test Case Status
- REQ-001 Log in with email/password BR-01 High DD-03 TC-001 Approved
- REQ-002 Password reset via email BR-01 High DD-04 TC-002 In progress
- REQ-003 Profile dashboard BR-02 Medium DD-07 TC-005 Approved
- REQ-004 Export data to CSV BR-03 Low DD-12 TC-008 Deferred
Reading the matrix: REQ-001 and REQ-002 both trace to business requirement BR-01 , so a change to BR-01 immediately flags two requirements, two design elements, and two tests for review. REQ-004 is Deferred , so it is intentionally out of the current release but still tracked — it has not been lost.
Types of Traceability
- Type Direction Question it answers
- Forward Requirement → design → test "Is every requirement built and tested?"
- Backward Requirement → business need "Does every requirement have a valid reason to exist?"
- Bi-directional Both "Is there complete coverage from need to verification?"
Trap: Candidates flip forward and backward. Forward = toward the future (design and tests, downstream). Backward = toward the origin (business need, upstream). If a stem asks how to confirm a requirement is actually justified by a business goal, the answer is backward traceability.
- Using the RTM: Impact Analysis, Scope Validation, Coverage
- Impact analysis
When a change request arrives, the analyst reads the RTM to see exactly what is affected before the change control board decides:
Which requirements change.
Which design elements and deliverables must be reworked.
Which test cases must be updated or re-run.
Which stakeholders to notify.
This is why the RTM is the analyst's first stop in integrated change control — it converts a vague "can we just add this?" into a concrete list of consequences.
Scope validation (prevents gold plating and missed scope)
- Risk How the RTM catches it
- Gold plating A deliverable exists with no traced requirement → flag and remove
- Missed scope A requirement exists with no deliverable → flag and build
- Untested work A requirement with no test case → add a test
- Coverage analysis
The RTM answers three coverage questions: are all requirements covered in the design , verified by tests , and linked to business needs ? Gaps in any column are corrective-action triggers.
Traceability by Delivery Approach
Approach How traceability is maintained
Predictive Formal RTM document updated at each phase gate; detailed links from business → system requirements → tests
- Agile Backlog hierarchy provides traceability; less paperwork but the links still exist
- Hybrid Formal RTM for compliance/regulatory items; agile backlog for the rest
- The Product Backlog as a Traceability Tool
In agile, the product backlog is the traceability mechanism. The chain runs: Business Objective → Epic → User Story → Acceptance Criteria → Test
- Agile artifact Traceability role
- Epic Links a feature group back to a business objective (backward)
- User story States the requirement in user terms
- Acceptance criteria Defines how the story is verified
- Definition of Done Ensures every story meets quality standards
- Automated tests Verify acceptance criteria, closing forward traceability
Trap: A common wrong answer claims "agile projects do not need traceability." They do — it is simply embedded in the backlog structure and acceptance criteria rather than a separate spreadsheet.