In situations of conflict, it is important for the project manager to address the issue constructively. Cultivating self-awareness through emotional intelligence (EI) can help team members understand their own emotions and those of others, which is crucial in resolving conflicts. This approach aligns with the PMBOK guide's recommendations on conflict management, which suggest that problem-solving and collaboration are effective strategies for dealing with team conflicts12. By fostering EI, the project manager can facilitate a more harmonious work environment and mitigate the negative impact on the project. References: = PMI's resources on conflict management and resolution strategies1; PMBOK Guide's section on conflict resolution2.

Following the stakeholder engagement plan is the best option for the project manager in this situation. The stakeholder engagement plan is a document that describes how the project manager will communicate with, manage the expectations of, and involve the stakeholders in the project decisions. By following this plan, the project manager can ensure that the decision about the new timeline is made in a transparent, collaborative, and timely manner, and that the stakeholders are informed and satisfied with the outcome. References:
(Professional in Business Analysis Reference Materials source and documents)
* PMBOK Guide, Seventh Edition, Section 13.2.3, "Stakeholder Engagement Plan"
* Professional in Business Analysis (PMI-PBA) Guide, Section 5.3.2, "Stakeholder Engagement"

* A stakeholder is a person or group that has an interest or influence in the project, such as the sponsor, the customer, the team, the supplier, or the regulator12. A key stakeholder is a stakeholder that has a high level of power and interest in the project, and whose support and involvement are critical for the project's success34.
* A project manager is responsible for managing the expectations and communications of the stakeholders, and ensuring that their needs and requirements are met throughout the project lifecycle5 .
A project manager should also involve the stakeholders in the decision-making process, especially when there are changes that affect the project scope, schedule, cost, or quality .
* In this scenario, a new regulation affects the project, and a critical status meeting discussing the scope changes is required. The project manager discovers that a key stakeholder cannot attend the scheduled meeting. This means that the key stakeholder's opinion and feedback will not be heard or considered in the meeting, which may lead to dissatisfaction, conflict, or resistance from the stakeholder later on.
* Therefore, the best option for the project manager is to meet with the key stakeholder prior to the meeting to obtain their opinion. By doing so, the project manager can:
* Inform the key stakeholder about the new regulation and its impact on the project
* Seek the key stakeholder's input and suggestions on how to deal with the scope changes
* Address any concerns or issues that the key stakeholder may have
* Gain the key stakeholder's approval and support for the proposed changes
* Represent the key stakeholder's interests and preferences in the meeting
* Communicate the outcome and action plan of the meeting to the key stakeholder after the meeting
* Meeting with the key stakeholder prior to the meeting can help the project manager to maintain a positive and collaborative relationship with the stakeholder, and to ensure that the project meets the stakeholder's expectations and requirements. It can also help to avoid or minimize any potential risks or problems that may arise from the scope changes, such as delays, rework, disputes, or loss of trust.
References:
1: Project Stakeholder Management - Project Management Institute 2: Stakeholder Analysis and Mapping: A Guide for Beginners 3: [How to Identify Key Stakeholders in a Project] 4: [Key Stakeholders: Definition, Role & Importance] 5: [Project Communications Management - Project Management Institute] : [How to Manage Stakeholder Expectations in Project Management] : [Project Scope Management - Project Management Institute] : [How to Manage Scope Changes on a Project]

According to the PMBOK Guide, issue management is the process of identifying and resolving issues that arise during the project life cycle1. Issues are problems that have already occurred and need to be addressed as soon as possible to avoid further negative impacts on the project objectives2. The project manager is responsible for managing issues and ensuring that they are resolved in a timely and effective manner3. One of the key steps in issue management is to identify the appropriate response and have it implemented4. This means that the project manager should analyze the issue, determine the best course of action, assign responsibilities, and monitor the progress of the resolution4. By doing so, the project manager can mitigate the impact of the issue on the project schedule and other aspects of the project performance4. The other options are not sufficient to manage the issue effectively. Identifying and reporting the issue (A) is necessary but not enough, as it does not involve taking any action to resolve the issue. Monitoring and controlling the issue (B) is also important but not sufficient, as it assumes that the issue has already been addressed and only needs to be tracked. Communicating any identified action to impacted stakeholders (D) is a good practice but not the primary responsibility of the project manager, as it does not ensure that the action is actually implemented and effective. References:
* 1: PMBOK Guide, 6th edition, p. 89
* 2: PMBOK Guide, 6th edition, p. 456
* 3: PMBOK Guide, 6th edition, p. 457
* 4: PMBOK Guide, 6th edition, p. 458

In Agile, scope is flexible, and time and resources are generally fixed per sprint. Therefore, when scope seems unmanageable, prioritization is the correct approach. The Scrum team-including the Product Owner-must decide which items provide the most value and can fit within the sprint.
Option B aligns with Agile principles by focusing on value delivery and continuous negotiation. This maintains flexibility while aiming to achieve business objectives.
Option A contradicts Agile team principles by injecting resources mid-sprint.
Option C is partially correct but lacks the negotiation and prioritization step.
Option D contradicts Agile's principle of team-driven planning and adaptive scope.
References:
Agile Practice Guide, Chapter 5: "Agile Planning Concepts"
The Scrum Guide (2020), Section: "Sprint Planning"
PMBOK Guide - Seventh Edition, Performance Domain: Planning and Delivery