CAPM Practice: Determine how to document project controls of predictive, plan-based projects

Scope control during execution involves managing changes to the scope baseline through integrated change control. When change requests are received, they are evaluated, and the CCB approves or rejects them. Approved scope additions are reflected in updated baselines. WBS creation, scope statement development, and stakeholder identification are planning activities.

**Why not B:** Identifying stakeholders and their scope requirements is a planning activity performed before execution begins. During execution, the focus shifts from identifying requirements to controlling changes to the already-defined scope baseline.

**Why not C:** Defining the project scope statement is a planning process that occurs before execution. The scope statement is an input to scope control, not an activity performed as part of controlling scope during execution.

**Why not D:** Creating the Work Breakdown Structure is also a planning activity that decomposes the scope into manageable work packages. The WBS is established before execution begins and serves as the baseline against which scope is controlled.