CAPM Predictive Plan-Based Methodologies 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.

• ✗

  Validate Scope to confirm the new feature

  Why it's wrong here

  Validate Scope formalises acceptance of completed deliverables, not evaluation of unapproved requests; the change has not been approved or implemented, so there is nothing to validate. It is tempting because scope verification deals with requirements, and would be correct once the feature is built and awaiting sign-off.

• ✓

  Submit a change request through Perform Integrated Change Control

  Why this is correct

  Once the scope baseline is approved, new features cannot be added informally; the request must enter Perform Integrated Change Control, where it is documented, evaluated and approved or rejected. This satisfies the governance constraint protecting the approved baseline.

• ✗

  Control Scope to update the scope baseline

  Why it's wrong here

  Control Scope monitors scope status and manages baseline changes, but it does not itself authorise the request; the change must first pass through Integrated Change Control. It is tempting because scope changes fall within its remit, and it would be correct for tracking variances after approval.

• ✗

  Direct and Manage Project Work to incorporate the feature

  Why it's wrong here

  Direct and Manage Project Work executes the approved plan; incorporating an unapproved feature would bypass Integrated Change Control and corrupt the scope baseline. It is tempting because this process implements changes, and would be correct only after the change request has been formally approved.

Go deeper

Related to this question