Welcome to Project Management Questions!

You can ask any question on Project Management and you can rest assured that real Project Managers will answer your shortly!

Benefits of a requirements traceability matrix

0
votes
I know what an RTM (Requirements Traceability Matrix) is, I know that it's like a matrix in an Excel sheet for checking if we are meeting the project requirements or not. But why bother doing this? We already know if we are meeting the requirements by checking for "done" tasks in the project schedule. I just don't understand what's the benefits of an RTM, when we the information learned by the RTM can be easily learned elsewhere, and without the extra work.

Please explain!
asked 8 years ago by anonymous

1 Answer

0
votes
Just because a task is "done" does not necessarily mean you have met the original requirement. Sometimes you might not meet all the requirements, but the tasks are still done done - eg you had a task to run a test and it failed to meet the spec but maybe you agreed with the customer that this was acceptable in the end. The RTM looks more at the output of tasks, rather than if the task is done or not. Individual high level requirements also might be spread over a number of tasks if they involve different teams/technologies/subsystems so it is not always the case that one task = one requirement.

I don't think it is a good idea to use your schedule as a RTM. The RTM is a 'one stop shop' giving yourself and the customer visibility of the overall requirements traceability.
answered 8 years ago by anonymous

Related questions

0
votes
1
answer
0
votes
1
answer
asked 7 years ago by anonymous
0
votes
1
answer
asked 7 years ago by anonymous
0
votes
1
answer
asked 7 years ago by anonymous
© 2010 - 2012 Project Management Questions - All Rights Reserved