Traceability Audit

The Traceability Audit documents the processes of:
1) comparing specifications to what was actually developed and plans to actual events,
2) identifying if and where change control process broke down, and,
3) determining the cause of all variations and deviations.

The comparison process focuses on Functional Specification and the Master Project Plan and looks at what occurred in the development phase and how that was different than planned.

These differences could take the form of feature reduction, elimination, creation; modifications in the Functional Specification; or scope/schedule/budget changes in the Master Project Plan.

The comparison process will also discover if those documents were maintained through the change control procedure. If not, they must be updated and change requests made.

A project must satisfy the criteria upon which it was established during the envisioning and planning phases.

Its documentation represents the discipline and commitment of a team dedicated to delivering quality.

The traceability audit process confirms quality documentation or remediates existing documentation to expected standards. In addition, the development phase must be assessed to ensure that what was committed to during early phases has been actually built.

The traceability audit will also confirm or remediate this.

The result of a traceability audit, regardless of its intermediate findings, is a project with current and accurate documentation and development results aligned with the Functional Specification.


Click here to download the template.