Which is a possible reason why the requirement was not implemented?

The project team has all the document control process and versioning in place to capture the requirements changes. The team ensures that the change is documented in the scope document, resulting in the changed work breakdown schedule (WBS) and schedule. However, a key requirement was not implemented in the release

Which is a possible reason why the requirement was not implemented?
A . The requirements traceability matrix was not updated with the change.
B . The schedule management plan was not updated with the change.
C . The requirements management plan was not updated with the change.
D . The scope management plan was not updated with the change.

View Answer

Answer: A