Requirement Traceability Matrix

The Requirement Traceability Matrix (RTM) is a document that links requirements throughout the validation process. The purpose of the Requirement Traceability Matrix is to ensure that all requirements defined for a system are tested in the test protocols.

The RTM shows all Features within an application. All User Stories created for these Features and all Test Cases written for these User Stories.

Look for indicators: analyze, decide and improve processes :

Indicator	Conclusion / Deciding Factor	Action	Process Improvement
Number of Test Cases for a User Story is very high.	User Story is bigger than expected. Test Cases are redundant.	User Story needs to be split properly. Remove redundant test cases.	1. Requirements should be proper. 2. Sprint planning should be done properly. 3. Check for redundant test cases before adding new. 4. Testers should get test cases reviewed form developers.
Number of Test Cases for a User Story is very low.	All scenarios are not covered. Test cases can be divided.	Test Cases should be written for all possible scenarios. If required, test cases should be divided so that testing can be done easily and fast.	1. Test Cases should have just sufficient steps. 2. Testers should get test cases reviewed form developers.

Indicator

Conclusion / Deciding Factor

Action

Process Improvement

Number of Test Cases for a User Story is very high.

User Story is bigger than expected.

Test Cases are redundant.

User Story needs to be split properly.

Remove redundant test cases.

1. Requirements should be proper.

2. Sprint planning should be done properly.

3. Check for redundant test cases before adding new.

4. Testers should get test cases reviewed form developers.

Number of Test Cases for a User Story is very low.

All scenarios are not covered.

Test cases can be divided.

Test Cases should be written for all possible scenarios.

If required, test cases should be divided so that testing can be done easily and fast.

1. Test Cases should have just sufficient steps.

2. Testers should get test cases reviewed form developers.

Users can also refer to these detailed reports for more details :

1. User Story Tests :

This sub report shows details of all test cases written for User Stories. These details are Test Case Title, Test Case ID, whether the Test Case is Disabled or not and Test Category.

Use => This report gives detailed information about the Test Cases written for all User Stories. This also shows the categories in which these Test Cases fall. This is helpful to know whether we have covered important Test Case Categories which were created in Lookup.