Project Management

Please login or join to subscribe to this thread

Requirement Tracebility Matrix

linkedin twitter facebook   Scheduling  
avatar
Nadim Shaikh Construction Manager| Larsen & Toubro Saudi Arabia LLC Riyadh, Riyadh Province, Saudi Arabia
Requirement Tracebility Matrix please explain in detail if possible with example
Sort By:
< 1 2 >
avatar
Tiago Romao Project Manager - PfMP | PgMP | PMP | ACP | PBA | CBAP | CSM | MSc.| Altice Portugal | Meo Sobreda, Setubal/Almada, Portugal
Requirement Traceability Matrix is a tool that permits to trace business requirements with functional and technical requirements, and vice versa (forward and backtrack).
It's important since its necessary to assure the alignment between the business department (the sponsor) and the internal and external suppliers (IT, engineering, vendors).
It's an advanced technique, difficult to put on practice without a proper tool.
I tried several times to implement it, through excel, and confess is difficult to keep the matrix updated. Even tried through an access database. It fits well in theory but in practice far for being implemented.
avatar
Anshuman Jain Senior Project Manager| TMNAS New Jersey, United States
Oct 27, 2017 5:47 AM
Replying to Nadim Shaikh
...
Requirements are mentioned in the Requirement Documentations.
Requirement Tracability Matrix is used to trace each requirements at each stage of the Project. Any change occured in the Project it can be easily traced which Requirement leads the particular change.
Is it OK? Please guide
Might not be true always. A change could add, which bring all together a new requirement that doesn't exists in the Req Tracebility Matrix. In that scenario, the RTM should help in determining its a new requirements (scope change).
avatar
alejandro vazquez Software Development Manager| Amazon Seattle, Wa, United States
In my personal practice, the Requirement Traceability Matrix is one of the documents in my list of minimus for any project.
It can be very simple. I use a simple excel matrix where columns are requirements and each row is a product.
Why is it so critical? Because it checks that you are not forgetting anything, as simple as that. As projects come to a close, you will be checking it periodically to make sure that all requirements are covered, which is especially critical as requirements and products change. For large projects, it might not be so obvious when a redesign has left a requirement unmet, or when you forget to schedule an injected requirement. If you miss a requirement you will not pass the acceptance phase, as project acceptance testing is normally done by requirement and you will not meet your customer's expectations.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"All generalizations are dangerous, even this one."

- Alexandre Dumas

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters