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.

The correct answer is D because organizational transformation to agile requires more than process changes- it requires a shift in mindset. Training teams on agile values and principles builds a shared foundation and helps foster commitment to agile ways of working.
From PMI Agile Practice Guide:
"Agile transformation requires attention to both practices and mindset. Leaders must help teams embrace agile values, empower decision-making, and promote an agile culture through education and active support." (PMI Agile Practice Guide, Section 2.1 - Organizational Change and Transformation) From PMBOK Guide - 7th Edition:
"Successful transformation begins with people understanding the why and how of agile. Change cannot happen effectively without adequate training and communication." (PMBOK Guide 7th Ed., Principle 1 - Be a Diligent, Respectful, and Caring Steward) From Mike Griffiths' PMI-ACP Exam Prep Book:
"Agile success is rooted in the team's understanding of core principles. Agile leaders must invest in developing a strong foundational mindset, as well as practices. Education is a critical enabler of sustainable agile adoption." (Mike Griffiths, Chapter 1 - Agile Principles and Mindset) Option A is a partial strategy but doesn't ensure cultural transformation.
Option B is necessary but not sufficient-buy-in alone won't change behavior.
Option C is tactical and useful but doesn't address team-wide mindset change.

The best answer is A because an agile practitioner should first facilitate collaboration, uncover the root causes of disagreement, and help the teams align around a shared outcome. The issue is not simply the absence of targets or KPIs; it is a cross-functional conflict involving cost, compliance, product choices, and sustainability commitments. PMI-ACP topics emphasize collaboration, stakeholder engagement, shared vision, systems thinking, and conflict facilitation.
Option B is too directive and may increase resistance because it forces compliance without resolving the underlying concerns. Option C centralizes the decision with executives, which reduces team collaboration and does not reflect agile servant leadership. Option D may be useful later, but KPIs alone will not resolve the tension or rebuild alignment. The agile practitioner should promote a collaborative approach to solving conflict and ensure common understanding of purpose and vision.
=========

The correct answer is D - Planning poker.
Planning poker is a consensus-based estimation technique commonly used in Agile projects. During this technique, team members discuss user stories, clarify details, and independently assign story points. The facilitator (often the Scrum Master) ensures balanced participation. This process encourages team collaboration and reduces estimation bias.
From the PMI Agile Practice Guide:
"Planning poker is a common estimation technique where team members discuss the story, then individually provide estimates using a card deck, reaching consensus over multiple rounds." (PMI Agile Practice Guide, Section 5.3 - Estimation Techniques) Mike Griffiths adds:
"Planning poker is based on Wideband Delphi and allows teams to converge on estimates through discussion and consensus. It is particularly useful for relative estimation of story points." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 - Adaptive Planning) Why other options are incorrect:
* A (Lessons learned) applies to retrospective activities, not estimation.
* B (Wideband Delphi) is the foundation of planning poker but is more formal and anonymous.
* C (Formal point counting) is not a standard Agile estimation technique.

In Scrum, the product owner is the primary point of contact between stakeholders and the development team.
According to the PMI Agile Practice Guide (Section 3.3: Roles and Responsibilities), the Scrum Master ensures that communications flow properly and protects the team from distractions.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) emphasizes the importance of having a single point of contact for stakeholder feedback to avoid miscommunication and overload.
* Option A is correct: redirecting communication through the product owner keeps the team focused and the backlog structured.
* Option B is unprofessional and discourages stakeholder engagement.
* Option C bypasses review and prioritization-backlog management should be intentional.
* Option D could blur roles and bypass proper channels.