PMP Process — Managing Technical Aspects Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Implement the change immediately without updating documents

  Why it's wrong here

  Implementing an approved change without updating project documents, such as the project management plan, schedule baseline, or scope baseline, is a critical error. This practice undermines configuration management, making it impossible to track the current approved state of the project. Without proper documentation, future decisions will be based on outdated information, leading to potential rework, scope creep, and a lack of control over project execution.

• ✗

  Instruct the team to ignore the change until next sprint

  Why it's wrong here

  Delaying the implementation of an approved change, particularly one affecting the critical path, until a future sprint is inappropriate and detrimental to project progress. Approved changes are authorized modifications that must be integrated into the project as soon as feasible to maintain schedule integrity and ensure the project remains aligned with its objectives. Postponing such a change can lead to further schedule slippage, increased costs, and a disconnect between the planned and actual project status.

• ✗

  File the change request in the project archives

  Why it's wrong here

  Simply filing an approved change request in the project archives without incorporating it into active project plans and baselines renders the approval process ineffective. Archiving is typically done for completed or rejected requests, or for final project documentation, not for operationalizing an approved modification. This action fails to integrate the change into the project's execution, leading to a discrepancy between the project's official documentation and its actual implementation, thereby negating the purpose of the change control process.

• ✓

  Communicate the change to stakeholders and update the project management plan and baselines

  Why this is correct

  This option correctly outlines the essential steps following the approval of a change request, especially one impacting the critical path. It mandates updating the project management plan and relevant baselines, such as the schedule and cost baselines, to reflect the new approved state. Concurrently, communicating these changes to all affected stakeholders ensures everyone is informed, manages expectations, and maintains alignment across the project team and external parties, which is crucial for effective project control and successful delivery.

Go deeper

Related to this question