Given the global distribution of the stakeholders and their high interest in the project (as indicated in the stakeholder power/interest grid), a dynamic feedback platform is the most effective way to ensure consistent engagement. By leveraging collaboration tools that allow asynchronous feedback, the team can accommodate stakeholders in different time zones, reducing the delay in obtaining feedback and helping to speed up the decision-making process. This approach ensures that all stakeholders can contribute when it's convenient for them, without the need for synchronized meetings, thus improving overall engagement and decision-making efficiency.

In Agile, continuous integration and regression testing should be part of every iteration to ensure that the product is always in a potentially shippable state. These practices help catch issues early in the development process, preventing defects from accumulating and becoming harder to fix later. By integrating and testing frequently, the team ensures that new code works with existing code and that the product maintains its quality throughout the development lifecycle. This approach aligns with Agile principles of delivering working software regularly and maintaining high-quality standards throughout each iteration.

The correct answer is B because agile approaches prioritize continuous stakeholder engagement, collaboration, and adaptive communication strategies. When stakeholder roles are redefined due to an organizational restructure, the agile team should proactively and directly engage with the newly impacted stakeholders to clarify expectations, responsibilities, and to maintain alignment with evolving needs.
The PMI Agile Practice Guide states:
"Engaging stakeholders directly and frequently fosters a shared understanding of objectives and priorities.
Two-way communication, such as conversations and collaboration sessions, is preferred over one-way communication such as reports or status updates." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement) In addition, Mike Griffiths' PMI-ACP Exam Prep Book supports this approach by highlighting:
"An agile team should regularly revisit and refresh stakeholder analysis. When changes occur in the stakeholder landscape, it ' s essential to revalidate stakeholder needs through open, two-way communication, rather than assuming static roles." (Mike Griffiths, Chapter 3 - Value-Driven Delivery / Stakeholder Engagement) Options A, C, and D fail to incorporate agile's emphasis on direct engagement and collaboration. Option D, while partially correct, lacks the proactive communication component that agile requires. Option C suggests a passive communication method (email), which is discouraged in agile practices for important stakeholder interactions.
Therefore, the best agile-aligned choice is: B

The correct answer is A - Add a task to the product backlog to allow the team time to investigate and experiment prior to estimating.
When the team lacks experience or clarity around a new feature or technical solution, they should perform a time-boxed research activity, known as a spike. Spikes allow the team to explore unknowns, validate assumptions, and gather information needed to provide accurate estimates.
From the PMI Agile Practice Guide:
"When the team is unable to estimate due to uncertainty, a spike can be added to the backlog. This allows time for research, experimentation, or prototyping to enable informed estimation." (PMI Agile Practice Guide, Section 5.3 - Adaptive Planning) Mike Griffiths also writes:
"Spikes are used to investigate technical or functional elements. A spike helps reduce uncertainty and informs future planning and estimation." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 - Adaptive Planning) Why other options are less effective:
* B (Wideband Delphi), C (Planning Poker), and D (Three-point estimation) are techniques for estimation, not suitable when the team lacks enough information to estimate in the first place.

In agile,information radiators-such as visual boards placed in common areas-are used to make project dataaccessible, transparent, and real-time. According to thePMI Agile Practice Guide (Section 7.1 Communication), visibility improves coordination across interdependent teams.
Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement)recommends that agile teams usevisible, shared artifactssuch as task boards, burn charts, or Kanban walls to improvecross- team communicationand reduce friction.
* Option Bis correct: a physical or virtual board offers transparency and encourages informal communication.
* Option Ais useful but not as effective for rapid visibility.
* Option Cis one-way and doesn't support real-time updates.
* Option Dis reactive and could cause delays or misalignment.