REQUIREMENTS TRACEABILITY MATRIX
PROJECT
PROJECT ID:
MANAGER:
PROJECT
PROJECT TITLE:
SPONSOR:
REQUIREMENT INFORMATION RELATIONSHIP TRACEABILITY
ID CATEGORY REQUIREMENT PRIORITY SOURCE BUSINESS OBJECTIVE DELIVERABLE(S
REQ-001 Mandatory High
REQ-002 Should have Medium
REQ-003 Nice to have Low
MENTS TRACEABILITY MATRIX
RELATIONSHIP TRACEABILITY
VERFICATION VALIDATION
DEFINITIONS
PROJECT MANAGER
The person with responsbility for managing and delivering the project. They will own this log, but may not be the person maintaining it.
PROJECT ID
The project number is assigned by the PMO (Project Management Office) once the project is approved for funding.
PROJECT SPONSOR
The person with ultimate accountablity for the project. They will hold the purse strings.
PROJECT TITLE
The name of the project, this should align with the name given on other project documents (rather than being a nickname).
REQUIREMENT ID
Give each requirement a unique identifier or reference so that it can be easily traced throughout the project life-cycle.
CATEGORY
Provide a category for the requirement typical categories are: functional, non-functional, usability, security, performance, maintainability etc.
REQUIREMENT
Describe the requirement that needs to be met by the project. The requirement might be a product, some product functionality, a service, or a result.
PRIORITY
Provide a priority for the requirement. For example, mandatory, should have, nice to have or high, medium, low.
SOURCE
Enter the name of the stakeholder that identified the requirement.
BUSINESS OBJECTIVE
Document the business objective that this requirement will meet or help to meet. The business objective will come from the project charter or the Project business Case.
DELIVERABLE(S)
List the deliverable or deliverables that will make up this requirement.
VERIFICATION
Explain how you will test that the requirement is completed satisfactorily. For example 99.9% uptime for user acceptance of software.
VALIDATION
Explain how the requirement will be validated or tested. This will often be via user acceptance testing, but it might also be by the achievement of a milestone or perhaps by the completion of a key
performance indicator.
HOW TO CHANGE THE MENU ITEMS IN STATUS FIELDS
Default settings
We have not set any drop down menus, as it is likely that most projects will have different priorities and categories.
How to create a drop down menu
Click on Data tab > Data Validation > Settings > List
In the Source field enter the menu items separated by a comma.
To change the menu items
To change the menu options or remove the dropdown select Data > Data Validation > Settings > List
ADDITIONAL FIELDS YOU MIGHT WANT TO ADD
Supplier - On projects with multiple suppliers you may want to add a field to note the supplier responsible.
WBS ID - Add WBS ID so that the requirement can be linked to the Work Breakdown Structure and project schedule.
Test case ID - Later in the project you may want to link the requirement to the test cases that will be used to
check that the requirement meets the business objective.
