A company is migrating from on-premise email to a cloud-based solution. The vendor changes the migration tool mid-project. Which project management document should be updated to track the impact on requirements?
The RTM links requirements to their implementation and is updated when changes affect how requirements are met.
Why this answer
The requirements traceability matrix (RTM) links each requirement to its origin, design, testing, and delivery status. When the vendor changes the migration tool mid-project, the RTM must be updated to reflect how this change impacts each requirement—such as compatibility, data migration rules, or security controls—ensuring all requirements are still met and traceable.
Exam trap
The trap here is that candidates confuse the risk management plan with tracking requirement impacts, but the RTM is the specific artifact for linking and monitoring requirement changes throughout the project lifecycle.
How to eliminate wrong answers
Option A is wrong because the risk management plan documents how risks are identified, analyzed, and responded to, not the tracking of requirement changes; the tool change itself might be a risk, but the impact on specific requirements is tracked in the RTM. Option B is wrong because the project charter is a high-level document that authorizes the project and defines initial scope, objectives, and stakeholders; it is not updated to track detailed requirement impacts during execution. Option D is wrong because the work breakdown structure (WBS) decomposes project deliverables into manageable work packages; it does not map requirements to their verification or track changes to requirements.