This scenario represents the realization of an external risk. When an identified risk occurs, the appropriate action is to follow the response strategy as documented in the risk management plan. The PMBOK Guide - Seventh Edition emphasizes the importance of using the risk response plan to guide actions when risks occur.
This avoids delays and ensures a structured response rather than ad hoc decision-making.
Option A may be needed in some cases but is not the project manager's responsibility unless required by law.
Option B ignores the actual disruption caused.
Option D introduces unnecessary delay by deferring action instead of using the pre-approved plan.
References:
PMBOK Guide - Seventh Edition, Risk Management Performance Domain
PMBOK Guide - Sixth Edition, Section 11.6: Implement Risk Responses
-

In agile project management, risks are identified and managed continuously throughout the project. Agile teams prioritize risks according to severity and address them as they arise during each iteration. This approach ensures that risks are handled in a timely and efficient manner, aligning with the iterative nature of agile methodologies. The team acknowledges the risks and incorporates risk management activities into their iteration planning and execution, allowing for proactive responses to potential issues1.
: = Agile Risk Management - Brainbok1.

In the context of Agile methodologies and specifically within Sprint Planning, prioritizing backlog items is typically based on the business value each item brings to the project. This approach ensures that the most valuable features are delivered first, providing immediate benefits and enabling early feedback which can be used to guide future development. The business value is a key factor because it aligns the team's efforts with the strategic goals of the organization and the needs of the stakeholders.
: = This prioritization strategy is supported by Agile principles, which emphasize delivering valuable software early and continuously. It is also in line with the guidelines provided by the Project Management Institute (PMI) for Agile project management practices.

The stakeholder register is a key input for managing communications. In Agile, frequent communication and stakeholder inclusion are vital. If there's a failure due to incorrect contact data, the Scrum Master should proactively review and verify the full stakeholder register to ensure it's accurate and complete, preventing recurrence.
According to the PMBOK Guide - Seventh Edition (Stakeholder and Communication Performance Domains), it is the responsibility of the project team to maintain accurate stakeholder information. This promotes engagement, transparency, and effective decision-making.
Option A places undue burden on the product owner and is inefficient.
Option B shifts responsibility to the stakeholder.
Option C demonstrates poor accountability.
References:
PMBOK Guide - Seventh Edition, Stakeholder Performance Domain
Agile Practice Guide, Chapter 4 - Stakeholder Engagement
##############################################