According to the PMBOK Guide, scope change control is the process of managing the changes to the project scope and ensuring that they are aligned with the project objectives and benefits. Scope change control involves identifying, documenting, analyzing, approving, or rejecting changes to the project scope. Scope change control also requires updating the project management plan, project documents, and project baselines to reflect the approved changes. Scope change control is part of the integrated change control process, which involves coordinating changes across all aspects of the project, such as schedule, cost, quality, risk, and stakeholder expectations. The CCB is a formal group of stakeholders who are responsible for reviewing and approving change requests and ensuring that they are consistent with the project charter and business case. The CCB also monitors the impact of changes on the project performance and benefits. The project manager should collaborate with the CCB to review the scope and submit any change requests that are necessary to keep the project on schedule while still meeting the project objectives. This will ensure that the scope changes are properly evaluated, authorized, and communicated to the project team and other stakeholders. The other options are not the best choices because they do not follow the scope change control process and may result in scope creep, rework, conflicts, or missed expectations. Option B is incomplete because it does not mention the collaboration with the CCB and the review of the scope. Option C is risky because it may increase the cost and complexity of the project without ensuring that the scope changes are justified and approved. Option D is irresponsible because it ignores the impact of scope changes on the project schedule and quality. References:
PMBOK Guide, Seventh Edition, Chapter 4: Project Integration Management, Section 4.6: Integrated Change Control
PMBOK Guide, Seventh Edition, Chapter 5: Project Scope Management, Section 5.6: Scope Change Control
PMI-PBA Guide, Chapter 5: Planning the Business Analysis Approach, Section 5.3: Benefits Tracking
Scope change control - Project Management Institute
