Requirements & Traceability

A project's Requirements tab. Requirements & Traceability is on the Team plan.

• Each requirement gets an id (REQ-1 and so on), an optional parent, a priority (Must, Should, Could or Won't have) and a status (Draft, Approved, Implemented, Verified, Deferred or Rejected). Approving, verifying and rejecting need a project manager.
• Link tasks on the project, named tests with a result, Decision Log entries, Risk Register entries and GitHub pull requests on the project's tasks.
• Coverage: a requirement with no linked task or no linked test is a gap. Deferred, rejected and won't-have requirements are not counted.
• Raise as a risk files a Risk Register entry (the Risk Register must be on).
• Changing the wording, priority or status tells the people on linked tasks and keeps the earlier version.
• A link never lets anyone see a task, decision or risk they could not already see; hidden ones are counted, not named.

Ask Ava about traceability for one project or every project.