2010-02-11 February 2010 - The Requirements Tracability Matrix (presented by Tom Carlos)

PMI - Sacramento Valley Chapter's I-80 Breakfast Roundtable Meeting
February 11, 2010 at 8:00 AM
Requirements Traceability Matrix
Tom Carlos, PMP

Introductions

In this presentation, we will cover the following:

Definition and Reasons For Requirements Traceability
Defining and setting up a matrix
How to incorporate and integrate the matrix into the overall project plan
Forward and backward utilization and validation
Guarding against scope creep
Leveraging with System Requirements Specifications

Here is an outline of the Requirements Traceability Matrix (RTM) topics that were presented:

Project Management Tools
Tools are the template

Project manager needs to have a means of tracking the work

Deliverables one of many requirements
Requirements tell you what qualifies as a valid deliverable

Create tool to identify requirement
Requirement name and description
Expectation of what the requirement will do

Defining RTM
Tool to help ensure that the project’s scope, requirements and deliverables remain “as is” when
compared to the baseline
Tool for forward and backward traceability

RTM can be used during all phases of a project

Matrix should be created at the very beginning of a project because is forms the basis of the project’ scope and incorporate the specific requirements

Matrix is considered to be bi-directional. It tracks the requirement “Forward” by examining the output of the deliverables and “Backward”.

RTM used to verify that all requirements are met and to identify changes to the scope when they occur

Enhances the scope management process and quality management

Create RTM
Each requirement must be unique and clear
Columns are:
Name
RFP # (Request for Proposal)
DDD # (Deliverable Definition Document)
PPT# (MS Project Subtask and Task numbers)
TS# (Test Script)
Verification (Yes/No) – Paper signed off or people verbally signing it off
Disposition of Requirement – Close, Derived from

Keep track of original, no longer needed, and changed requirements

Columns to prioritize requirements and standards reference

Private Enterprise – Questioned why the documentation is necessary

Government – It’s legislated that the documentation is required

What tool do you use for creating an RTM?
• MS Excel
• MS Access
• Share Point
• RTM Specialty Tool

RTM should be used for every project
Traceability is an essential element for every project, regardless of size
Utilize the features of forward and backward traceability to help manage work
Helps prevent “Scope Creep”
Helps ensure requirements completion as intended
Adds to project documentation
Configuration management – This is how decisions are made, what approval process is

What happens if you do not use RTM
Scope creep and disagreement in requirements
Lost or forgotten requirements
Breakdown in project integration
No means of tracking approval changes/mods
No mapping to Testing phase and Sign-off

Case for the RTM
• Identify, understand and trace current requirements
• Track and understand changes to requirements
• Establish a basis for testing and sign-off

References for this Presentation:

http://ww2.cdc.gov/cdcup/library/templates/CDC_UP_Requirments_Traceabili...