The correct answer is C - Conducted an end-of-phase demonstration.
Agile emphasizes continuous feedback. Regular demonstrations (e.g., sprint reviews or product demos) allow stakeholders, including the customer, to inspect the product increment and provide real-time feedback. Had the team demoed the product, they might have discovered the deficiencies before release.
PMI Agile Practice Guide states:
"A demo or review allows stakeholders to inspect the product increment and provide feedback.
Demonstrations reduce the risk of unmet expectations and confirm that the team is building the right product." (PMI Agile Practice Guide, Section 5.7 - Reviews and Demos) Mike Griffiths writes:
"Agile avoids large, end-of-phase validations. Instead, customer feedback is solicited at the end of every iteration through structured demos. This allows for early course correction and alignment with expectations." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Other options:
* A is a waterfall artifact and not aligned with agile workflows.
* B is analysis-heavy and doesn't ensure real stakeholder feedback.
* D (retrospective) improves process, not product validation.

Planning Poker is a well-known estimation technique where team members use numbered cards (usually Fibonacci series) to estimate story point values based on relative size. It's a consensus-based estimation method, as described in the PMI Agile Practice Guide (Section 5.2: Estimation Techniques) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 6: Estimating Techniques).
* Option D is correct: Planning Poker is explicitly designed for estimating stories in terms of points.
* Option A (Parametric) is more common in traditional (predictive) planning.
* Option B (One-to-one comparison) refers to relative sizing without collaboration.
* Option C (Affinity) is another agile technique but typically used for grouping stories into size buckets, not direct story point consensus estimation.

Pair programming is a proven agile technique for improving quality, sharing knowledge, and ramping up less experienced developers. The PMI Agile Practice Guide (Section 5.5: Quality and Engineering Practices) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 3: Team Performance) recommend using pair programming to improve team cohesion and performance when skill gaps are affecting velocity.
* Option A is correct: pair programming supports learning and improves delivery quality.
* Option B misuses the retrospective-it's not for backlog prioritization.
* Option C may be helpful, but estimation changes don't directly address the skill gap.
* Option D may reduce risk short-term but doesn't help the team improve or grow.

In Agile, changes are expected and are part of the iterative process. The product owner should take the opportunity to coach the stakeholder on agile principles, explaining how continuous feedback, flexibility, and adaptability are core to delivering value in an Agile project. Instead of pushing back on changes, the product owner can help the stakeholder understand that responding to change helps improve the product and better meet user needs. This helps align the stakeholder ' s expectations with Agile practices and fosters better collaboration throughout the project.

The correct answer is D - Create a risk burndown chart showing the reduction of risks over time.
In Agile, risk management is integrated into each iteration. A risk burndown chart is a visual information radiator that tracks the total risk exposure and how it changes over time, making risk transparent and easy for the team to understand.
From the PMI Agile Practice Guide:
"A risk burndown chart can be used to communicate the decreasing level of project risk over time and encourage discussion on risk mitigation strategies." (PMI Agile Practice Guide, Section 6.4 - Risk Management) Mike Griffiths also states:
"Agile teams use tools like risk burndown charts to visualize risks and track mitigation. They provide real- time understanding of current and remaining risks." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 - Problem Detection and Resolution) Other options:
* A is a responsibility assignment matrix (not risk-focused).
* B and C are traditional (predictive) methods and don't align with Agile risk communication.