In agile, when uncertainty exists around a technical or functional aspect of work, the team can use aspike-a time-boxed research or prototyping activity-to explore the unknown. According to thePMI Agile Practice Guide (Section 5.2 User Stories and Spikes),spikes are ideal when the team lacks information or confidenceabout a proposed solution and needs to experiment before committing.
Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning)explains thatspikes 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 Ais correct because a spike would allow the team to explore the new framework in a controlled way.
* Other options such asIshikawa diagrams (B),pre-mortems (C), andtrend analysis (D)are useful in other contexts, but not suitable for increasing confidence in new technical implementation approaches.

The correct answer is A - Stakeholders should have regularly been engaged to obtain feedback and reduce the functionality risk.
In Agile, stakeholder engagement and iterative feedback loops ensure that the solution being built is aligned with business value. Simply meeting documented requirements is insufficient. Agile practices such as demos and user feedback sessions minimize the risk of building features that fail to deliver value.
PMI Agile Practice Guide:
"Agile emphasizes ongoing stakeholder engagement. Demonstrating working software at the end of each iteration and gathering feedback ensures that the product is delivering business value." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement) Mike Griffiths states:
"Value-driven delivery is achieved not just by delivering what was asked for, but by ensuring it actually meets customer needs. Regular feedback from stakeholders is critical to avoid building low-value features." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* B refers to the lean principle of "decide as late as possible," but feedback, not delay, would have addressed the issue.
* C is unrelated to this context.
* D lacks the collaborative engagement approach emphasized in Agile.

The correct answer is C - Ask the Product Owner to select an item from the backlog on which to work. The Product Owner is responsible for prioritizing the product backlog. When a team finishes its sprint work early, it should collaborate with the Product Owner to identify the next highest-value item to pull into the sprint.
From the PMI Agile Practice Guide:
"The Product Owner owns the backlog and prioritization. If work is completed early, the team may pull in the next most important backlog item, subject to capacity and readiness." (PMI Agile Practice Guide, Section 5.3 - Iteration Execution) Mike Griffiths reinforces:
"If there's remaining capacity in the sprint, teams should consult the Product Owner to select the next item.
The Scrum Master facilitates, but the PO owns content decisions."
(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 - Adaptive Planning)
Incorrect options:
* A skips prioritization.
* B misplaces decision-making authority.
* D incorrectly involves the Scrum Master in backlog decisions.

The correct answer is B - Conduct story-mapping exercises to clarify deliverables and release priorities. Story mapping is a visual practice that aligns stakeholders and teams around a shared understanding of the product vision, user workflows, and incremental delivery plans.
From the PMI Agile Practice Guide:
"Story mapping is a collaborative activity used to understand the user's journey, prioritize features, and identify releases. It is highly effective for stakeholder alignment and promoting shared understanding." (PMI Agile Practice Guide, Section 5.4 - Story Mapping) Also supported by Mike Griffiths:
"Story mapping promotes visibility, alignment, and prioritization. It fosters collaboration between the team and stakeholders and helps translate business objectives into user stories." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Why other options fall short:
* A reverts to heavy documentation, which agile discourages.
* C is a one-time event and doesn't sustain alignment.
* D focuses on adherence to process rather than collaboration and planning clarity.

A spike is a time-boxed research activity used in Agile to explore uncertainties or unknowns, such as dependencies in this case. If the product owner is unsure about the risks related to migrating to a new version of a database, they can request a spike from the team. This will allow the team to investigate the dependencies, assess potential risks, and gather the necessary information to move forward with the user story. This helps reduce uncertainty and makes it easier to make informed decisions about the next steps.