After a change request is approved by the Change Control Board (CCB), the project manager should communicate the decision to the stakeholder who requested the change. This is an important step in the change management process as it ensures transparency and maintains trust with stakeholders. It also allows the stakeholder to understand that their request has been considered and integrated into the project, which is crucial for stakeholder engagement and satisfaction.
= The information is aligned with the PMBOK Guide's Change Management Process, which emphasizes the importance of communication with stakeholders after a decision has been made on a change request1. Additionally, the role of Business Analysts in change management includes ensuring that changes align with the organization's goals and objectives, which involves communicating approved changes to relevant stakeholders2.

Meeting milestones without delivering a quality product undermines the project's objectives. The PMBOK Guide - Seventh Edition emphasizes delivery of value and quality as key aspects of project performance. When quality issues emerge, the project manager should collaborate with the team to identify gaps between expected and actual outcomes and take corrective action.
Option B is correct because it addresses the root cause-quality gaps-and aligns outcomes with stakeholder expectations.
Option A assumes a time extension is needed before evaluating the actual gap.
Option C disregards quality, which is a key component of the project constraints (scope, time, cost, quality).
Option D is reactive and ad hoc; reprioritization should follow analysis of root causes.
Reference:
PMBOK Guide - Seventh Edition: Quality and Performance Domains
Agile Practice Guide: Delivering Value and Continuous Improvement

When discrepancies arise between documented scope and current deliverables, the first step is to understand why and how they occurred. The project manager should work with the team to review the change history and clarify whether these changes were officially approved. This enables informed conversations with stakeholders and potential corrective action.
According to the PMBOK Guide - Seventh Edition (Measurement and Stakeholder Performance Domains), issue resolution starts with identification and root cause analysis before initiating change or communications actions.
Option A addresses communication frequency but not the root cause.
Option C is premature if a valid change was already made.
Option D may be done later but doesn't resolve the current concern.
Reference:
PMBOK Guide - Seventh Edition, Scope and Stakeholder Performance Domains PMI Change Control Best Practices