CAPMEasy

CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach

Question 28 of 85 in Explain when it is appropriate to use a predictive, plan-based approach

In a predictive project, the project scope is controlled through:

Show answer & explanation

Correct answer: Integrated change control and scope baseline management

Explanation

Scope management in predictive projects uses integrated change control — any change to the defined scope must be formally requested, analyzed, approved, and baseline-updated. The scope baseline (WBS + WBS dictionary + scope statement) defines the approved scope against which changes are measured.

**Why not A:** Sprint reviews where a product owner accepts or rejects user stories are an agile/Scrum ceremony. Predictive projects do not use sprints, product owners, or user stories for scope control. Scope is controlled through baselines and formal change control.

**Why not B:** Daily standups are an agile ceremony for team coordination. Predictive projects may use regular status meetings, but daily standups are not the mechanism for scope control. Scope control in predictive projects is formal and baseline-driven.

**Why not C:** Continuous refactoring of the WBS contradicts the principle of baseline stability in predictive projects. The WBS is part of the scope baseline, which can only be changed through formal change control. Continuous refactoring undermines the baseline's function as a stable reference.

Key Concept

This question covers Explain when it is appropriate to use a predictive, plan-based approach under Explain when it is appropriate to use a predictive, plan-based approach (Predictive, Plan-Based Methodologies).

All 1,500+ CAPM questions are free