The correct answer is C - The stakeholders will learn whether or not the implementation has worked by getting immediate feedback so they can correct their assumptions for the next sprint.
Agile welcomes stakeholder involvement throughout the project lifecycle. Demos (also called sprint reviews) are critical opportunities for stakeholders to inspect the product increment and provide feedback, which helps teams pivot or adapt early and often. Immediate feedback reduces the risk of building features that do not meet business needs.
PMI Agile Practice Guide:
"Iteration reviews/demos provide stakeholders with the opportunity to see working product increments and offer feedback while there is still time to make changes." (PMI Agile Practice Guide, Section 5.7 - Reviews and Demos) Mike Griffiths supports this by stating:
"Engaging stakeholders during sprint reviews allows assumptions to be challenged early. This feedback loop ensures value alignment and reduces the likelihood of rework." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Other options:
* A incorrectly distances stakeholders from essential agile feedback cycles.
* B shifts focus away from value to effort-based metrics.
* D is more about long-term ROI, not immediate iterative feedback.

As a servant leader, the agile coach's role is to support and empower the team, helping them overcome obstacles that hinder their progress. In this case, the coach should focus on identifying and removing any impediments that are slowing down the work, whether they are technical, process-related, or communication- based. This approach enables the team to work more efficiently, enhances their ability to self-organize, and ensures they can deliver high-quality results. Simply adjusting the work plan or assigning more resources may not address the underlying issues, and a command-and-control approach is counterproductive in an Agile environment.

The correct answer is D - Implement a spike to enhance creativity by experimenting with new techniques and process ideas in order to discover more efficient and effective ways of working.
A spike is a time-boxed research or prototyping activity used to explore uncertainty, investigate a technology, or gain deeper knowledge of an implementation. Spikes are especially useful when a team lacks familiarity with certain technologies, as they reduce risk and support better estimation.
From the PMI Agile Practice Guide:
"Spikes are a type of exploration that agile teams use when they are uncertain about a technology or technique. They are time-boxed research efforts aimed at reducing risk and improving future delivery." (PMI Agile Practice Guide, Section 5.3 - Spikes) Mike Griffiths further explains:
"Spikes allow the team to gain knowledge needed to understand a technical or design problem. They are particularly useful when the team lacks domain or technical experience and are often used to improve estimation accuracy." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 - Adaptive Planning) Why other options fall short:
* A and B manipulate iteration length without addressing the core problem (lack of technical knowledge).
* C increases overhead without solving the learning gap or preventing the root cause (rework).
answers and comprehensive explanations drawn from authoritative sources including the PMI Agile Practice Guide, PMBOK Guide, Mike Griffiths' PMI-ACP Exam Prep Book, and Andy Crowe's PMI-ACP Exam materials.
##################################################

The correct answer is D - Engaged key stakeholders periodically to collect requirements.
Agile is based on frequent stakeholder collaboration. Continuous engagement ensures evolving needs are captured and prevents misalignment. Waiting for planning meetings or demos is too late to catch missing input.
PMI Agile Practice Guide:
"Agile teams ensure stakeholder engagement is ongoing throughout the project. This helps validate requirements and prevent surprises during reviews." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement) Mike Griffiths:
"Stakeholders should be consulted early and often. Relying on static requirements leads to gaps. Agile teams maintain constant feedback loops." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A is too early and one-time.
* B may help but is reactive.
* C is a predictive approach inconsistent with agile.

When a team reports that user stories are unclear or lack sufficient detail, the correct agile response is to foster collaborative refinement and shared understanding. Auser story workshopis a well-recognized practice that involves the team and product owner collaborating to write, clarify, and refine stories. This is supported by thePMI Agile Practice Guide (Section 5.2: User Stories and Backlog Refinement), which recommends story-writing workshops as a proactive way to clarify requirements.
Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning)notes that good agile teams collaboratively refine stories in grooming sessions or workshops to ensure shared clarity and alignment.
* Option Cis correct: a workshop enables both the team and product owner to collaborate in improving story clarity.
* Option Aoversimplifies the solution-acceptance criteria alone don't fully define a story.
* Option Bmisuses the retrospective, which is for process improvement, not story editing.
* Option Descalates prematurely and undermines team ownership and collaboration.