When a project team consisting of professionals from different nationalities is struggling with deliverables, the project manager should provide support to help the team solve their own problems. This approach aligns with the principles of servant leadership and empowerment, which are crucial in managing cross-cultural teams. By supporting the team in problem-solving, the project manager fosters a cooperative environment that encourages creativity, motivation, and the use of diverse perspectives to overcome challenges. This method also helps in building team cohesion and effectiveness, which are essential for the successful completion of projects in a multicultural setting123.
: = The approach is supported by resources on managing cross-cultural differences in projects and supporting team performance, as found in the Project Management Institute's (PMI) materials123.

According to the Project Management Professional (PMP) standards, when a milestone is missed, it's important to maintain transparency and communicate effectively with all stakeholders. This includes sending formal communication about the missed milestone. While this may reflect poorly on the team in the short term, it upholds the principles of accountability and integrity, which are crucial for long-term success and trust-building in any project.
Delaying communication (Option B) or foregoing it (Option D) can lead to a lack of trust and can create a precedent for non-transparency. Asking for a meeting with the sponsor to decide whether to send the formal communication (Option C) could be seen as an attempt to avoid responsibility. Therefore, the best course of action is to send a formal communication regarding the missed milestone (Option A).
: Project Management Professional (PMP) Certification Handbook available at PMI's official website.
Specifically, refer to the section on 'Professional Responsibility' which discusses the importance of transparency and communication in project management.

* According to the PMBOK Guide, 6th edition, section 5.6.2, the project manager should perform an impact analysis when a change request is received, to assess the potential effects on the project scope, schedule, cost, quality, resources, risk, and other aspects.3
* The project manager should also communicate the impact analysis to the relevant stakeholders, such as the project sponsor, the product owner, the customer, and the team, to facilitate the decision making process and obtain their agreement on the change.3
* The project manager should not accept or reject the change request without performing an impact analysis, as this may lead to unrealistic expectations, missed deadlines, scope creep, or stakeholder dissatisfaction.3
* The project manager should not ask the product owner to prioritize the new request without performing an impact analysis, as this may disrupt the agile team's work and compromise the quality of the deliverables.4
* The project manager should not call the stakeholder to tell them that the final product schedule must be extended without performing an impact analysis, as this may damage the trust and relationship with the stakeholder and cause them to lose confidence in the project.
The references for this answer are:
1: Discuss Exam PMP Topic 2 Question 499 Discussion | Actual4test 2: Free PMP Practice Exam Questions -
120 Sample Test Questions 3: PMBOK Guide, 6th edition, Project Management Institute, 2017, pp. 149-
152. 4: Agile Practice Guide, Project Management Institute, 2017, pp. 37-38. : [Managing Stakeholder Expectations for Project Success: A Knowledge Integration Framework and Value Focused Approach, Ori Schibi, 2013, pp. 97-98.](https://www.pmi.org/learning

In Agile project management, the iteration review is a meeting held at the end of an iteration where the team demonstrates the work completed during the iteration. This event is an opportunity for the project manager to show the business stakeholders the integrated features in action, thus addressing their concerns about understanding the feature integration with the product. It allows stakeholders to see the tangible results of the development efforts and provides a platform for immediate feedback.
: The answer is based on general Agile practices and the role of iteration reviews in Agile project management, which are commonly included in PMP study materials and the PMBOK guide.

According to the PMBOK Guide, quantitative risk analysis is a process that numerically analyzes the effect of identified risks on overall project objectives. It is usually performed on risks that have been prioritized by the qualitative risk analysis process. Quantitative risk analysis requires specialized skills and tools, such as statistical analysis, simulation, and modeling. Therefore, not every project team member may have the knowledge or experience to perform this task. If the project manager encounters such a situation, the best option is to help the team member to perform the quantitative risk analysis through coaching, mentoring and training. This way, the project manager can ensure that the team member learns the necessary skills and techniques, and can contribute to the risk management process. This also aligns with the project manager's responsibility to develop the project team and enhance their competencies. Option A is not the best answer because contacting the PMO and requesting another team member may cause delays and disruptions in the project schedule and team dynamics. Option B is not the best answer because escalating the issue to the functional manager may not solve the problem, and may create conflict between the project manager and the functional manager. Option D is not the best answer because performing the quantitative risk analysis for the team member may not be feasible or efficient, and may deprive the team member of the opportunity to learn and grow. References: PMBOK Guide, 6th edition, pages 431-432, 440-441.