The root cause analysis indicated that a component added as part of a change request was not tested, which led to the product being rejected during the quality control check. This suggests a gap in the change control process where the quality management artifacts, such as test plans or checklists, were not updated to include the new component for testing. Therefore, the project manager should review and update the change control process to ensure that all aspects of a change, including quality management artifacts, are considered and updated accordingly. This action will help prevent similar issues in future and ensure that changes are fully integrated into the project's quality management framework.
The answer is verified using the principles found in the PMBOK Guide, which outlines the importance of integrated change control and its impact on project quality management. The guide emphasizes the need to review and update all project documents, including quality management plans, to accommodate changes within the project. Additionally, the Professional in Business Analysis (PMI-PBA) reference materials support the need for thorough documentation and communication of changes to prevent quality issues and ensure project success.

The project manager should engage the team members and guide them to investigate why they hold differing views. Understanding the rationale behind each interpretation promotes root cause analysis and leads to an informed decision.
According to the PMBOK Guide - Seventh Edition, problem-solving and facilitating collaborative discussions are key leadership competencies. By engaging the individuals first, the project manager avoids making unilateral decisions and promotes team responsibility.
Option B risks propagating incorrect information.
Option C delegates decision-making without proper facilitation.
Option D is premature without understanding the discrepancy sources.
Reference:
PMBOK Guide - Seventh Edition, Planning and Team Performance Domains
PMI's Conflict Resolution and Decision-Making Techniques
-

The project manager's primary responsibility during team conflict is to engage directly with the team to facilitate resolution and restore team performance. This includes using interpersonal and leadership skills such as active listening, emotional intelligence, and coaching. When there's confusion about change requirements, the project manager should first clarify with the team before escalating or deferring.
The PMBOK Guide - Seventh Edition emphasizes that project managers should foster open communication, resolve conflict early, and clarify ambiguity through engagement.
Option A undermines collaboration and may create resentment.
Option C (HR) is inappropriate for technical disagreements.
Option D escalates too early before using team-level conflict resolution.
Reference:
PMBOK Guide - Seventh Edition, Section 3.1: Leadership and Communication PMI Talent Triangle: Power Skills - Conflict Management

When the project manager identifies that the delay on the critical path was caused by the client, it is essential to formally document this and then seek a discussion with the client. This supports transparency, allows for resolution, and protects the contractor from inappropriate penalties.
Per the PMBOK Guide - Seventh Edition and PMI's Contract Management standards, documenting the root cause and opening a dialogue is the first proper step in addressing contractual disputes.
Option B is a valid legal step, but only after engagement and documentation.
Option C refers to an internal party (sponsor) who may not be relevant here.
Option D may support analysis but does not immediately address the contractual issue.
Reference:
PMBOK Guide - Seventh Edition, Governance and Delivery Performance Domains PMI Practice Standard for Project Contracts

Before escalating or logging an issue, the project manager should take a proactive leadership role and engage directly with the new leader. This conversation allows for alignment of expectations and identification of any process or communication issues that can be resolved collaboratively. This approach is consistent with stakeholder engagement best practices.
Option A postpones corrective action and risks further delays.
Option B escalates prematurely, which may harm collaboration.
Option C is a planning tactic, but not a resolution to the current delay.
Reference:
PMBOK Guide - Seventh Edition, Stakeholder Engagement and Team Performance Domains PMBOK Guide - Sixth Edition, Section 13.3: Manage Stakeholder Engagement
-