When trust or satisfaction is an issue with a stakeholder-especially one as critical as the sponsor-the first step is direct communication. A one-on-one meeting to understand expectations, concerns, and establish rapport is essential. This aligns with stakeholder engagement best practices, where early and proactive engagement is prioritized.
The PMBOK Guide - Seventh Edition, in the Stakeholder Performance Domain, recommends identifying and analyzing stakeholder needs and initiating communication to build or maintain relationships.
Option A is too process-oriented and premature before establishing rapport.
Option B is informative but lacks interpersonal connection.
Option C provides updates but does not address dissatisfaction or rebuild trust.
References:
PMBOK Guide - Seventh Edition, Stakeholder Engagement Performance Domain PMBOK Guide - Sixth Edition, Section 13.3: Manage Stakeholder Engagement
-

In a project with high uncertainty, where the customer is concerned about the number of iterations and the risk of not meeting the mandatory delivery date, a hybrid approach is recommended. This approach combines elements of both predictive and agile methodologies, allowing for flexibility in areas of high uncertainty while maintaining a level of predictability for certain aspects of the project. It enables the project team to plan parts of the project with a high degree of certainty predictively, while managing other parts with more flexibility and adaptability using agile practices.
The recommendation for a hybrid approach aligns with the guidance provided by PMI, which suggests tailoring the project management approach to fit the business environment, the risks, and the complexity of the project12. Additionally, the Professional in Business Analysis Reference Materials supports the use of a hybrid approach in situations where parts of an initiative use a predictive approach and parts use an adaptive approach3.

To avoid the situation where a legal requirement is overlooked in a global project, the project manager should have identified the regulatory differences among the countries involved. This involves a thorough analysis of the legal and regulatory environment in each country to ensure that all requirements are addressed during the planning phase. By understanding these differences early on, the project manager can incorporate the necessary compliance measures into the project plan, avoiding potential legal issues and delays.
The importance of identifying regulatory differences in global projects is highlighted in the PMBOK Guide, which recommends a comprehensive approach to managing projects across different jurisdictions1. This is further supported by the PMI's Global Project Management Framework, which emphasizes the need for understanding the unique requirements on a country-by-country basis to achieve a high level of efficiency on global projects2. Additionally, the Professional in Business Analysis (PMI-PBA) materials advocate for the analysis and management of requirements, including legal and regulatory, throughout the project lifecycle34567.