According to the PMBOK Guide, the project manager should manage the project scope, including the planning, validation, and control of the scope. The project manager should also manage the project changes, including the initiation, evaluation, approval, and implementation of the changes. In this scenario, the project manager received a request to add additional changes 1 day before the planned change date. This is a potential change to the project scope that may also impact the project time, cost, quality, and other aspects. The best course of action is to review the additional changes and perform integrated change control. This can help the project manager to assess the feasibility and desirability of the change request, and to determine the appropriate response and approval. Reviewing the additional changes and performing integrated change control (option C) is the best solution to the issue, as it demonstrates proactive and effective project scope and change management. Rejecting the changes as the lead time is too short (option A) may not be feasible or ethical, as it may violate the customer's expectations and satisfaction, and may damage the trust and relationship with the customer. Determining whether the project team is capable of making the changes (option B) may not be sufficient or realistic, as it may ignore or overlook the impact and value of the change request, and may create a conflict or resentment among the project team. Checking if the changes are covered in the statement of work (SOW) (option D) may not be relevant or helpful, as it may not address the change request itself, nor does it account for the possible deviations or changes that may occur during the project execution. Reference: : Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK Guide) (6th ed.). Newtown Square, PA: Author1 : Change Request - Project Management Knowledge2 : Managing Change Requests in Project Management [Template]3 : Which Project Documents Need A Change Request For Updates?4

When a conflict arises during a project charter review, it's important for the project manager to address the situation promptly to prevent escalation and maintain focus on the project objectives. Facilitation techniques are a key tool for improving communication and resolving conflicts within a team. These techniques can include active listening, ensuring that each party is heard, and guiding the discussion towards a mutual understanding or agreement. By continuing the meeting and employing these techniques, the project manager can help the stakeholders focus on the common goal of the project's success, rather than getting sidetracked by the conflict12.
Reference:
PM Study Circle: "5 Conflict Resolution Techniques in Project Management" 1 LovePMP: "PMP Questions conflict" 2

External stakeholders typically require performance metrics to understand the status of a project. Earned value is a proven methodology to measure project performance objectively. Earned Value in terms of schedule (D) and cost (E) offers valuable insights on how well the project is adhering to its baseline plans.
D: Earned Schedule (EV vs. Planned Value) shows schedule adherence.
E: Earned Cost (EV vs. Actual Cost) shows cost efficiency.
Options A and C are portfolio-level metrics, not typically reported by project managers.
Option B is vague and not part of standard EVM practice.
Reference:
PMBOK Guide - Seventh Edition, Measurement and Delivery Performance Domains PMI Practice Standard for Earned Value Management

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.
Reference:
Agile Practice Guide, Chapter 5: "Agile Planning Concepts"
The Scrum Guide (2020), Section: "Sprint Planning"
PMBOK Guide - Seventh Edition, Performance Domain: Planning and Delivery

When faced with conflicts arising from cultural differences within a project that involves multiple organizations, the project manager should first seek guidance from the project sponsor. This is because the project sponsor has the authority and perspective to understand the broader organizational strategies and can provide direction on how to best address the cultural issues. Additionally, the sponsor can facilitate the development of a strategy that aligns with the project's goals and the organizations' cultures123. Reference:
Managing Cross Cultural Differences in Projects1.
Cultural Diversity in Project Management: How Project Success is Perceived in Different Cultures2.
Cultural Differences: Knowing the Nine Dimensions of Culture to Succeed in Project Management3.