Requirements Traceability Matrix
A requirements traceability matrix (RTM) is a grid that links product requirements from their origin to the deliverables that satisfy them, ensuring each requirement adds business value and is tracked throughout the project.
Explanation
The requirements traceability matrix is an output of the Collect Requirements process and serves as a vital tool for managing requirements throughout the project lifecycle. It creates a bidirectional link between each requirement and its source (business need, objective, or stakeholder) as well as the WBS deliverable, design component, test case, or other artifact that fulfills it.
The RTM helps the project team ensure that every approved requirement is delivered and that no unauthorized work is added to the project. It supports impact analysis when changes are proposed, because the team can quickly identify which deliverables, tests, and objectives are affected by a change to any single requirement.
Typical attributes tracked in the RTM include a unique requirement ID, description, business need or justification, owner, source, priority, version, current status, and date completed. The matrix is a living document updated throughout the project as requirements evolve, deliverables are completed, and changes are approved.
Key Points
- •Links requirements to their origin and to the deliverables that satisfy them
- •Supports impact analysis for proposed changes
- •Ensures all approved requirements are delivered and nothing unauthorized is added
- •Updated throughout the project lifecycle
Exam Tip
The RTM provides traceability from business need to requirement to deliverable to test case. On the exam, it is the go-to tool when asked about tracking or verifying that all requirements are met.
Frequently Asked Questions
Related Topics
Collect Requirements
Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
Requirements Documentation
Requirements documentation describes how individual requirements meet the business need for the project, capturing all requirements in enough detail for them to be measured and managed.
Validate Scope
Validate Scope is the process of formalizing acceptance of the completed project deliverables by the customer or sponsor.
Control Scope
Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.