In projects with high levels of uncertainty, especially those that are innovative in nature, it is beneficial to increase the number of iterations. This allows for more frequent reassessments and adjustments, which can help in managing change requests more effectively. By breaking down the project into smaller parts and reassessing at the end of each iteration, the project manager can incorporate necessary changes in a controlled manner, thus reducing the overall number of change requests.
: The PMBOK Guide outlines the iterative approach as a means to manage and control projects with high uncertainty1. It suggests that iterative cycles allow for continuous improvement and adaptation, which is crucial for innovation projects2. The Professional in Business Analysis materials also support this approach, emphasizing the importance of iterative review and adaptation in response to change34.

When missing requirements specifications are identified during the design phase, the project manager should meet with the development team to review and assess the requirements. This collaborative approach ensures that all team members are aware of the discrepancies and can contribute to finding a solution. It is also aligned with the PMBOK Guide's emphasis on engaging stakeholders and maintaining open communication throughout the project lifecycle. By assessing the requirements with the team, the project manager can ensure that the project remains aligned with its objectives while addressing the gaps in the specifications.
References:
Requirements Management Practice Guide | PMI1.
Effective requirements management - Project Management Institute2.
PMBOK Guide Seventh Edition FAQs3.

During the initiation phase of a project, the project manager and the team define the project idea, including project goals, scope, and resources1. If a potential risk, such as low construction productivity, is identified during a lessons learned sharing session, it should be added to the risk register1. The risk register is a document where all details of the identified risks are recorded. The project manager should then develop a mitigation strategy for site execution. This strategy could include various actions to address the risk, such as improving processes, providing additional training, or hiring additional resources. The goal is to reduce the impact of the risk on the project's objectives. References: Asana Resources | Project management, 4 Phases of the Project Management Lifecycle Explained | Coursera

According to the PMBOK Guide, the schedule performance index (SPI) and the cost performance index (CPI) are two key indicators of the project performance measurement1. The SPI measures how efficiently the project team is using the time allocated for the project, while the CPI measures how efficiently the project team is using the resources allocated for the project1. An SPI or CPI value greater than 1 indicates that the project is ahead of schedule or under budget, respectively. An SPI or CPI value less than 1 indicates that the project is behind schedule or over budget, respectively1. In this question, the project manager notices that the SPI is 1.8 and the CPI is 0.1, which means that the project is ahead of schedule but over budget. This is a serious issue that needs to be addressed as soon as possible, as it may jeopardize the project viability and stakeholder satisfaction. The project manager should not ignore the project sponsor's concern, as the project sponsor is the person who provides the financial resources and support for the project2. The project manager should also not assume that it is normal to spend more money in the design phase of a project, as this may indicate poor planning, estimation, or control of the project costs3. The project manager should not stop crashing the schedule, as this may affect the project scope, quality, or risk. The project manager should not use a resource-levelling technique, as this may delay the project completion and increase the project costs.
The best option for the project manager is to manage the project sponsor closely and revise the project's resource management plan to improve indicators. This means that the project manager should communicate frequently and transparently with the project sponsor, explain the reasons for the cost overrun, and seek their input and approval for any corrective actions. The project manager should also review and update the project' s resource management plan, which is the document that describes how the project resources will be estimated, acquired, managed, and controlled. The project manager should identify and implement strategies to reduce the project costs, such as optimizing the resource allocation, negotiating better rates, or eliminating unnecessary activities or resources. By managing the project sponsor closely and revising the project's resource management plan, the project manager can improve the project performance indicators and increase the chances of delivering the project within the approved budget. References:
* 1: PMBOK Guide, Chapter 7, Section 7.4.2.1, Page 267
* 2: PMBOK Guide, Chapter 13, Section 13.1.2.1, Page 518
* 3: 5 Essential Tips for Schedule Control in Project Management
* : PMBOK Guide, Chapter 6, Section 6.6.2.5, Page 215
* : PMBOK Guide, Chapter 6, Section 6.4.2.5, Page 201
* : Guide to Project Budgeting & Scheduling
* : PMBOK Guide, Chapter 9, Section 9.1.3.1, Page 313
* : How to Make a Project Budget: Project Budgeting Basics

The first step in any communication-related issue is to review the Communications Management Plan and the Stakeholder Engagement Plan to ensure expectations are correctly documented and aligned. These documents define who needs what information, when, and how it should be delivered. PMIS may provide access, but stakeholders may still require proactive updates through preferred channels (e.g., emails, reports).
According to the PMBOK Guide - Seventh Edition (Communication Performance Domain and Stakeholder Engagement), project managers should tailor communications based on stakeholder needs, which are identified through these plans.
Option A is reactive and not process-driven.
Option C assumes a technical failure without verification.
Option D provides a one-time fix but does not resolve the systemic issue of missed stakeholder expectations.
References:
PMBOK Guide - Seventh Edition, Communication and Stakeholder Engagement Performance Domains PMBOK Guide - Sixth Edition, Sections 10.1-10.3 and 13.1-13.3
-