The old school approach is to use Excel and a Requirements Traceability Matrix. It’s not fancy, but it works, especially when plans, procedures and test results point back to the matrix. The failure in traceability is usually human error or lack of compliance. It has to be a team priority and enforced by management and work style/environment.
Here are some options/things to look at in making your decision:
Awesome, thanks for the links. I also tend to believe that it is a process over tooling question; you could even accomplish this with a text document and some checklists.
Comments
The old school approach is to use Excel and a Requirements Traceability Matrix. It’s not fancy, but it works, especially when plans, procedures and test results point back to the matrix. The failure in traceability is usually human error or lack of compliance. It has to be a team priority and enforced by management and work style/environment.
Here are some options/things to look at in making your decision:
https://www.dau.edu/tools/Documents/SAM/resources/RTM_Risk_R...
https://www.perforce.com/blog/alm/what-traceability
https://www.jamasoftware.com/requirements-management-guide/r...
https://www.inflectra.com/Ideas/Topic/Requirements-Traceabil...
Awesome, thanks for the links. I also tend to believe that it is a process over tooling question; you could even accomplish this with a text document and some checklists.