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
##############################################

When a project is faced with a fixed budget, it's crucial for the project manager to prioritize the work based on its value to the organization. This approach ensures that the most important and valuable parts of the project are completed within the available budget. This is in line with the principles of value-driven delivery, which is a key concept in project management and business analysis. It emphasizes delivering the highest value to the business and stakeholders, and making decisions based on the maximization of value12. References: PMBOK Guide, Project Management Institute1; What to do when no more financing is available for a project in PMI, Project Management Stack Exchange1.

When stakeholders are concerned about visibility and control, the project manager should address governance directly by engaging stakeholders to review how oversight, reporting, decision rights, and escalation will work in an agile context. Meeting with stakeholders to discuss and review the governance structure (B) is the best first step because it builds shared understanding and confidence, clarifies what information is needed (metrics, cadence, artifacts), and adapts governance appropriately without assuming the solution upfront.
Jumping immediately to a hybrid model (A) may be correct later, but it presupposes the outcome rather than first understanding stakeholder needs, regulatory requirements, and organizational controls. Simply following the existing governance unchanged (C) risks misfit-traditional gates and heavy documentation may slow a time-critical agile effort or create friction, while still not providing meaningful transparency. Reviewing governance "to reflect scope changes" (D) is too narrow; governance must reflect delivery approach, roles, and information flow-not only scope. Stakeholder-centered governance design supports trust, compliance, and timely decision-making-key business-environment objectives in PMP-aligned delivery.

Team building in project management is the process of developing a cohesive team that will work together to achieve successful outcomes12. It involves identifying the strengths and weaknesses of each member and using those insights to create an environment where collaboration, trust, and open communication are encouraged3. In this case, facilitating a team-building meeting can help address the issue of team members working individually rather than as a team. This meeting can help the team members understand each other better, build trust, and foster a sense of belonging, which can encourage them to work together as a team12.
References:
Team Building in Project Management | PMI1
Team Building | Project Management Professional (PMP) - GreyCampus2
Ways to Create a Strong Project Team | PMI - Project Management Institute4 Team Building: Success Path to Project Management - Eduhubspot3

Explanation: