Scope, change requests and traceability

Protecting scope, assessing and pricing changes, and keeping requirements, solution, tests and delivery linked.

In this lesson

Baselines and change control
Traceability end to end
Status, risks and escalation

Key points

Baseline = signed requirements + SDD
Every change: describe, classify, estimate, decide
Requirement IDs link SDD, config, handover, tests, UAT, training
Weekly status; escalate blockers early

Real-world example

Three months after go-live a client disputed paying for 'missing' commission reports. The traceability matrix showed the requirement was recorded as phase 2 in a signed change decision. The conversation became planning phase 2 instead of a payment dispute.

Questions and answers

Where do requirement IDs appear?

SDD, config log, handover, test scenarios, UAT log, training.

Why batch small changes?

To reduce overhead and keep releases controlled.

Read the full lesson, worked example and quiz