According to the PMBOK Guide (Project Management Body of Knowledge), specifically within the Project Integration Management knowledge area and the Perform Integrated Change Control process:
* Integrated Change Control (Option D): This scenario describes " scope creep " or an unauthorized change. The Perform Integrated Change Control process is designed to prevent exactly this type of issue. By requiring that all changes-regardless of the source-be formally documented, evaluated for their impact on all project constraints (scope, schedule, cost, quality, etc.), and approved by a Change Control Board (CCB) or the Project Manager, the team would have discovered the adverse effect on the other deliverable before the change was implemented.
* Quality Assurance (Option A): This process (now called Manage Quality) focuses on the processes used to create deliverables to ensure they meet quality standards. While it helps ensure the result is correct, it is not the primary mechanism for managing the intake and approval of scope changes.
* Stakeholder Management Plan (Option B): This plan identifies how to effectively engage stakeholders.
While it might define who can request changes, the actual mechanism for processing those requests and analyzing their cross-functional impact is the Change Control System.
* Project Team Building (Option C): This is part of the Develop Team process. While a cohesive team might communicate better, team building itself is not a procedural control for managing technical changes to project deliverables.
In the PMI framework, Integrated Change Control is critical because no change exists in a vacuum. A change to one deliverable often ripples through the project, affecting others. By following a formal process, the Project Manager ensures that the " big picture " is maintained and that the project baseline remains protected from uncoordinated modifications.