Requirements Traceability Matrix (RTM) is one of the most important documents a project manager uses as part of his job. In order to understand RTM clearly, first we should clearly understand what a Traceability Matrix is…
First, What is a Traceability Matrix ?
It is a document, usually in the form of a table, used to assist in determining the completeness of a relationship by correlating any two baselined documents using a many-to-many relationship comparison.
Requirements Traceability Matrix (RTM)
In simple words, it is a document that is used to track all the requirements, and check whether all the project requirements are met.
RTM is a way to link requirements to deliverables that implement requirements. In RTM, baselined requirements are mapped across different baselined data such as use cases, design, test plan and test case. It is mapping the Business requirements with technical requirements to ensure that all the requirements are met with the final deliverable. RTM ensures that various activities of the project fulfills the business requirements, and that none of the business requirements go missing from implementation.
PMBOK defines Requirements Traceability Matrix (RTM) as a grid that links product requirements from their origin to the deliverables that satisfy them.
Various attributes associated with each requirement can be recorded in RTM. The typical requirement attributes used in the RTM may include: A Unique Identifier, Textual description of of the requirement, rational of the requirement, Owner, Source, Priority, Version, Current Status, status date, complexity, Acceptance criteria, etc.
RTM 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.
RTM is used throughout the project in analyzing proposed changes to project or product scope.. i.e.. it provides a structure for managing changes to the product scope.