Which document links project objectives to deliverables by tracing requirements to measurable outcomes, and in which knowledge area is it primarily maintained?

Which document links project objectives to deliverables by tracing requirements to measurable outcomes, and in which knowledge area is it primarily maintained?

• A. Requirements Documentation; Stakeholder Management.
• B. Requirements Traceability Matrix; Scope Management.
• C. Traceability Register; Cost Management.
• D. Requirements Traceability Matrix; Risk Management.

Answer: (B)

A Requirements Traceability Matrix links project objectives to deliverables by tracing each requirement to the measurable outcomes and verification criteria that show it has been satisfied. It lays out the line from what needs to be built to how success will be measured, often connecting requirements to design elements, test cases, acceptance criteria, and final deliverables. This ensures every objective has a corresponding deliverable and a way to validate it, which is exactly what ties objectives to concrete outcomes. This is maintained primarily within Scope Management, since it directly supports defining, validating, and controlling what is included in the project and ensuring deliverables meet approved requirements. Plain Requirements Documentation describes what is needed but not the explicit, end-to-end linkage to deliverables and tests. Stakeholder Management focuses on engaging people rather than tracing requirements to outcomes. A Traceability Register is a repository of trace links but is not the standard, formal tool used to demonstrate that requirements map to measurable deliverables. Cost Management and Risk Management deal with budget and risk aspects rather than the traceability of requirements to outcomes.

A Requirements Traceability Matrix links project objectives to deliverables by tracing each requirement to the measurable outcomes and verification criteria that show it has been satisfied. It lays out the line from what needs to be built to how success will be measured, often connecting requirements to design elements, test cases, acceptance criteria, and final deliverables. This ensures every objective has a corresponding deliverable and a way to validate it, which is exactly what ties objectives to concrete outcomes.

This is maintained primarily within Scope Management, since it directly supports defining, validating, and controlling what is included in the project and ensuring deliverables meet approved requirements.

Plain Requirements Documentation describes what is needed but not the explicit, end-to-end linkage to deliverables and tests. Stakeholder Management focuses on engaging people rather than tracing requirements to outcomes. A Traceability Register is a repository of trace links but is not the standard, formal tool used to demonstrate that requirements map to measurable deliverables. Cost Management and Risk Management deal with budget and risk aspects rather than the traceability of requirements to outcomes.