According to the PMBOK® Guide, any change to a project deliverable, project management plan, or project document must be processed through the Perform Integrated Change Control process.
Handling Defects and Modifications: When defects are identified that require a modification to functionality (a change in scope or product requirements), it is not enough to simply fix the defect. The change must be formally requested and evaluated for its impact on the project ' s constraints (cost, time, scope, and quality).
Stakeholder Buy-in: The core of " obtaining stakeholder buy-in " for changes lies within the Change Control Board (CCB) or the formal change process. This process ensures that the Sponsor, Customer, and other key stakeholders review the change, understand its implications, and provide formal approval or rejection. This prevents " scope creep " and ensures all parties are aligned before the modification is implemented.
Analysis of other options:
Control Schedule (Option A): This process is focused on monitoring the status of project activities to update progress and manage changes to the schedule baseline. It does not provide the framework for approving functional modifications.
Perform Qualitative Risk Analysis (Option B): This involves prioritizing individual project risks by assessing their probability and impact. While a defect could be viewed as a realized risk (an issue), the process for getting " buy-in " for a fix is the change control process, not risk analysis.
Control Scope (Option D): This process monitors the status of the project and product scope. While it identifies the need for a change (variance), the actual approval and " buy-in " for that change happen through Integrated Change Control.
Per PMI standards, the project manager is responsible for ensuring that no changes are made to the project ' s baselines without going through the Perform Integrated Change Control process, which serves as the formal mechanism for stakeholder communication and agreement regarding modifications.
