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

After CCB approval, the project manager must update all affected project documents and baselines before work begins. This includes: updating the scope baseline (WBS, scope statement), schedule baseline (adding activities and adjusting dates), cost baseline (adding budget), and any other affected subsidiary plans. Work starts against the updated, approved baselines — not the original ones.

**Why not A:** A new project charter is not needed for an approved scope change. The project charter authorizes the overall project; scope additions within an existing project are managed through change control and baseline updates. Creating a new charter would imply starting a new project.

**Why not B:** Re-engaging stakeholders to collect new requirements is not the immediate next step after CCB approval. The requirements for the change were already defined in the change request that the CCB reviewed. The next step is updating the baselines and plans to incorporate the approved change before work begins.

**Why not C:** Starting work immediately after CCB approval without updating baselines creates a governance gap. The team would be working against outdated baselines, making performance measurement inaccurate. Updated baselines are needed so the additional work has proper scope, schedule, and cost targets.