In agile, when uncertainty exists around a technical or functional aspect of work, the team can use a spike-a time-boxed research or prototyping activity-to explore the unknown. According to the PMI Agile Practice Guide (Section 5.2 User Stories and Spikes), spikes are ideal when the team lacks information or confidence about a proposed solution and needs to experiment before committing.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explains that spikes are used to investigate technical approaches, prove concepts, or explore new technologies, and they provide the team with the insight and confidence needed to proceed with less risk.
* Option A is correct because a spike would allow the team to explore the new framework in a controlled way.
* Other options such as Ishikawa diagrams (B), pre-mortems (C), and trend analysis (D) are useful in other contexts, but not suitable for increasing confidence in new technical implementation approaches.

The agile facilitator should focus on keeping the daily coordination meeting (daily stand-up) focused and efficient. If the meeting is becoming unproductive or lengthy, the facilitator needs to actively manage the flow and intervene when team members deviate from the meeting's objective, which is to quickly discuss progress, identify blockers, and align on the work for the day. By doing this, the facilitator can help the team maintain the purpose and time-box of the meeting, which is generally 15 minutes.

The team's primary role is to estimate and define the work items in the product backlog. In an Agile environment, the team collaborates with the product owner to break down user stories into manageable tasks, providing effort estimates (such as story points) to help guide future iterations. The team also works with the product owner to refine and clarify requirements when needed, ensuring that the work is well understood and ready for execution.

The correct answer is B - Establish a live video feed between the dispersed teams to enable spontaneous engagement and collaboration on issues.
Agile encourages face-to-face communication as the most effective form of knowledge sharing. For distributed teams, this means using video conferencing, virtual whiteboards, and real-time collaboration tools to replicate co-located team dynamics. This improves clarity, reduces misinterpretation, and accelerates problem-solving.
PMI Agile Practice Guide states:
"For distributed teams, using video conferencing, shared tools, and real-time collaboration platforms helps bridge communication gaps and maintains team cohesion. Face-to-face communication, even via video, remains the most effective method." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement) Mike Griffiths also notes:
"Distributed teams must invest in communication technologies to reduce barriers. Real-time, visual communication enables faster resolution of issues and a shared understanding of tasks." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 - Team Performance) Incorrect Options:
* A involves centralized control and status reporting - not Agile.
* C demands co-location, which may not be feasible.
* D accepts poor performance instead of addressing root causes.

Before the workshop, the team members should read and identify relevant user stories from the product backlog that directly contribute to the goal of developing the feature for receiving and resolving customer complaints. This ensures that the stories being worked on are well-understood and aligned with the release goal.
The team should also consider the possible risks associated with each selected user story, such as technical challenges or dependencies. Additionally, they should evaluate the value each story adds to the final user (customer), ensuring that the team focuses on delivering maximum value in the release.