For example, when a high-level business requirement changes 30 days into a project, through trace
relationships you can then immediately assess the impact it has on any downstream functional
requirements, tasks and defects that a developer or tester might be working on. This helps minimize errors
and costly rework because the team members affected are aware of the specific change and its impact.
Implementing traceability and a change control process that’s appropriate for your situation is one of the
most important steps to ensuring success. As a simple first step to establishing change control, you can
use a change request form manually to document changes right now.