CAPM Practice: Determine how to document project controls of predictive, plan-based projects

The Requirements Traceability Matrix traces each requirement from its origin (stakeholder request or business need) through the project lifecycle — to design decisions, deliverables, and test cases. It ensures all requirements are implemented, tested, and accounted for, and provides a change impact analysis tool when requirements change.

**Why not A:** Documenting requirement priority for stakeholder communication is a useful function but is not the primary purpose of the RTM. The RTM's core value is ensuring traceability — linking each requirement through the full project lifecycle from origin to testing and delivery.

**Why not C:** Assigning team members to requirements is a resource management activity, not the purpose of a traceability matrix. The RTM tracks the lifecycle of requirements, not who is responsible for implementing them.

**Why not D:** Estimating the cost of implementing each requirement is a cost estimation activity. The RTM does not contain cost data — it traces requirements from their origin through design, development, and testing to ensure completeness and coverage.