What causes replanning of the project scope?

Question

Options

• ARequested changes
• BProject scope statement changes
• CVariance analysis
• DApproved change requests

• A
  3% (1)
• B
  10% (4)
• C
  5% (2)
• D
  82% (32)

Explanation

Approved change requests are the formal trigger for replanning project scope because, within the change control process, only changes that have been evaluated, authorized, and documented carry the authority to modify project baselines. Until a change is approved, it has no standing to alter the project management plan or scope baseline.

Why the distractors are wrong:

• A (Requested changes): A request is just a proposal - it must pass through integrated change control before any replanning occurs. Requests that are rejected or deferred do not change anything.
• B (Project scope statement changes): Scope statement changes are an output of replanning, not a cause. They happen because of approved change requests, not independently.
• C (Variance analysis): This is a monitoring and controlling technique that compares planned vs. actual performance. It may surface the need for a change request, but it does not itself authorize or cause replanning.

Memory tip: Think of it as a traffic light - a requested change is a yellow light (pending), but only an approved change request turns the light green and lets replanning proceed. No approval = no action on the plan.

No community discussion yet for this question.