In situations where there is a lack of support for the project, it is crucial to identify and engage with key stakeholders who can influence the project's success. The PMBOK Guide emphasizes the importance of stakeholder engagement and the need to analyze stakeholder influence, expectations, and impact on the project to effectively manage their engagement. By understanding which stakeholders have the most influence, the project manager can develop strategies to gain their support and address the concerns that may be hindering the project's progress.
: = The PMBOK Guide1, which outlines the principles of stakeholder engagement and management, and the Professional in Business Analysis Reference Materials2, which provide further insights into the importance of stakeholder analysis in project management.

This question belongs to the Process domain because it focuses on requirements discovery, adaptive development, and selecting an approach that enables value delivery under uncertainty. PMI guidance on complex requirements recognizes that in many projects the needed functionality cannot be fully defined early, especially in complex or evolving environments. In such cases, iterative exploration and prototyping can help stakeholders better understand what they want and reduce costly misunderstandings later.
Option A only records a problem and does not help the customer clarify the need. Option B adds time and cost without improving understanding. Option C is better than A or B, but it still assumes that detailed requirements can simply be elicited up front even though the customer cannot articulate them clearly. Option D is the strongest answer because prototyping helps the customer visualize the functionality, provide feedback early, and shape the solution while value is being created. PMP-style reasoning favors adaptive techniques when requirements are unclear and rapid learning is needed. Therefore, a prototyping approach is the most effective response.

In an uncertain environment, it's crucial for a project manager to validate assumptions and assess risks. This involves identifying, evaluating, and controlling uncertain factors that can significantly affect the project's performance1. This process, known as risk management, helps to avoid or mitigate potential negative effects1. It's also important for the project manager to be comfortable with uncertainty and to be able to react to it in an agile, but well-structured way2. This approach gives the project team confidence that the project is still taking the right steps to deliver as planned2. References: 1 Managing Project Uncertainty: From Variation to Chaos, 2 Managing projects in uncertain times - APM

According to the PMBOK Guide, an issue is a point or matter in question or in dispute, or a point or matter that is not settled and is under discussion or over which there are opposing views or disagreements1 An issue log is a project document that provides a mechanism for tracking and monitoring issues until they are resolved1 The issue log typically contains information such as the issue description, the issue type, the issue owner, the issue priority, the issue status, and the issue resolution1 The issue log is updated throughout the project as new issues arise and existing issues are resolved1 In the given scenario, the project manager is executing a project where an external vendor will provide some deliverables. After awarding the contract to the vendor, the project manager is informed that the vendor is running behind schedule on a separate project. Finding another vendor will exceed the budget. This situation presents an issue that affects the project schedule, cost, and quality, and requires immediate attention and resolution. The project manager should update the issue log first to document the issue, assign an owner, and monitor the status of the issue2 Updating the issue log will also help to communicate the issue to the relevant stakeholders and facilitate the issue management process2 The other options are not the best choices for the following reasons:
* Option B: Lessons learned register. A lessons learned register is a project document that captures the knowledge gained from the project and provides a basis for future actions and decisions. The lessons learned register is updated throughout the project as lessons are learned and validated. However, updating the lessons learned register is not the first action that the project manager should take in response to the issue. The project manager should first document and address the issue in the issue log, and then update the lessons learned register with the relevant information and insights after the issue is resolved.
* Option C: Stakeholder engagement plan. A stakeholder engagement plan is a subsidiary plan of the project management plan that identifies the strategies and actions to effectively engage project stakeholders throughout the project life cycle. The stakeholder engagement plan is updated as needed to reflect the current and desired levels of stakeholder engagement. However, updating the stakeholder engagement plan is not the first action that the project manager should take in response to the issue. The project manager should first document and address the issue in the issue log, and then update the stakeholder engagement plan if the issue affects the stakeholder expectations, interests, or influence.
* Option D: Risk register. A risk register is a project document that records the details of identified individual project risks and other information related to risk analysis and risk response planning. The risk register is updated throughout the project as new risks are identified and existing risks are analyzed, prioritized, and responded to. However, updating the risk register is not the first action that the project manager should take in response to the issue. The project manager should first document and address the issue in the issue log, and then update the risk register if the issue triggers a risk response or creates a new risk.
: 1: PMBOK Guide, 7th edition, Chapter 4: Keeping the Team on Track, Section 4.4: Manage Issues, pp. 104-
105 2: PMBOK Guide, 7th edition, Chapter 4: Keeping the Team on Track, Section 4.4.2: Manage Issues:
Outputs, pp. 106-107 : PMBOK Guide, 7th edition, Chapter 4: Keeping the Team on Track, Section 4.5:
Capture Knowledge, pp. 108-109 : PMBOK Guide, 7th edition, Chapter 4: Keeping the Team on Track, Section 4.5.2: Capture Knowledge: Outputs, p. 110 : PMBOK Guide, 7th edition, Chapter 2: Creating a High- Performing Team, Section 2.4: Engage Stakeholders, pp. 42-43 : PMBOK Guide, 7th edition, Chapter 2:
Creating a High-Performing Team, Section 2.4.2: Engage Stakeholders: Outputs, p. 44 : PMBOK Guide, 7th edition, Chapter 3: Doing the Work, Section 3.4: Navigate Uncertainty and Ambiguity, pp. 72-73 : PMBOK Guide, 7th edition, Chapter 3: Doing the Work, Section 3.4.2: Navigate Uncertainty and Ambiguity: Outputs, p. 74

A retrospective review is a meeting held at the end of an iteration in Agile project management, where the team can assess past work and plan future project goals1. One of the benefits of retrospective reviews is that they foster continuous improvement by identifying what went well and what can be improved2.
If the project team members are not completing tasks during the iterations because of interruptions and requests for help from other teams, it indicates that there is a problem with the team's collaboration and communication. The project manager, as a team facilitator, should address this problem by identifying its root causes and defining the ground rules with all project team members to minimize interferences. This way, the project manager can help the team to focus on their tasks, avoid distractions, and respect each other's time and boundaries3.
The other options are not correct for the following reasons:
B). Recommend to the project team members that they should improve their planning and make their stories smaller. This option does not address the problem of interruptions and requests for help from other teams, which are external factors that affect the team's performance. Making the stories smaller may help the team to deliver faster and more frequently, but it does not solve the underlying issue of poor collaboration and communication.
C). Reunite with the project team members affected and tell them not to reduce the team's capacity. This option is not effective because it does not address the problem's root causes, nor does it involve the whole team in finding a solution. Telling the team members not to reduce their capacity may also be perceived as blaming or pressuring them, which can lower their morale and motivation.
D). Hire a coach to help all project teams to improve their abilities to solve problems on their own. This option is not feasible because it involves hiring an external resource, which may not be available or affordable.
Moreover, hiring a coach does not guarantee that the problem will be solved, as the coach may not have the same context or understanding of the project as the team members.
1: Agile Retrospective Guide: What Is It & How To Run It 2: Sprint Retrospective: How to Hold an Effective Meeting - Atlassian 3: End of the project: how to run your final retrospective