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.

• ✗

  Ignore minor requests to avoid conflict

  Why it's wrong here

  Ignoring minor requests is a passive approach that fails to address the root cause of scope creep and can lead to stakeholder dissatisfaction and unmanaged expectations. This inaction does not prevent the scope from expanding informally, nor does it provide a mechanism for evaluating the impact of these requests on project baselines. A PMP must proactively manage scope, not avoid it, to maintain project control and achieve objectives.

• ✓

  Remind stakeholders that all changes must go through the formal change control process

  Why this is correct

  This is a crucial proactive step to manage scope creep by re-establishing project governance. By reminding stakeholders of the formal change control process, the project manager reinforces the established procedures for evaluating, approving, or rejecting proposed changes, thereby preventing further unauthorized additions to the project scope. This action directly supports maintaining the scope baseline and managing stakeholder expectations effectively.

• ✗

  Add the requests to the project backlog without approval

  Why it's wrong here

  Adding requests directly to the project backlog without formal approval bypasses the critical change control process, effectively condoning and institutionalizing scope creep. This action undermines the project's scope baseline and can lead to unmanaged increases in work, budget overruns, and schedule delays, as the impact of these additions has not been properly assessed or authorized. It creates an illusion of control while actually losing it.

• ✗

  Update the project management plan to reflect all informal requests

  Why it's wrong here

  Updating the Project Management Plan (PMP) to incorporate informal requests without them first undergoing the formal change control process is fundamentally incorrect and detrimental. This action legitimizes unauthorized scope changes, effectively making informal requests part of the official plan without proper impact analysis, stakeholder review, or formal approval from the Change Control Board (CCB). It compromises the integrity of the project baselines and the PMP itself.

• ✓

  Implement a change request for each informal request to formalize them

  Why this is correct

  For existing informal requests that have already surfaced, the most appropriate action is to initiate a formal change request for each one. This brings all proposed scope additions under the project's established change control process, allowing for proper evaluation of their impact on scope, schedule, cost, and quality. This approach ensures that even previously informal requests are properly reviewed, approved, or rejected, maintaining project governance and control.

Go deeper

Related to this question