One of the pillars of agile isearly and continuous customer feedbackto ensure that the product being delivered meets stakeholder expectations. According to thePMI Agile Practice Guide (Section 5.3: Reviews and Feedback Loops)andMike Griffiths' PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement),frequent customer reviews (e.g., sprint reviews)ensure alignment and early identification of quality or value issues.
* Option Dis correct: regular customer engagement during reviews ensures delivery effectiveness and customer satisfaction.
* Option Ais inappropriate-daily stand-ups are for internal team coordination.
* Option Breflects a waterfall approach.
* Option Cmisplaces the responsibility-requirements evolve and are refined throughout, not fixed up front.

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.

The sprint retrospective is a key Scrum ceremony where the team reflects on the sprint, identifies what went well, what didn't, and discusses ways to improve their processes. The focus is on continuous improvement, and the team makes plans to implement those improvements in future sprints. Stakeholders are typically not involved in the retrospective, but it's important for them to understand that the meeting is about helping the team improve their collaboration, efficiency, and performance.

The correct answer is A - Prioritize the stakeholder feedback, considering the impact on strategic objectives and current workload, and discuss these priorities with the team in the next sprint planning meeting to collaboratively decide on the next steps.
Agile promotes adaptive planning and continuous stakeholder engagement. While feedback is highly valuable, especially from a sprint review, changes to the product backlog must be carefully prioritized and collaboratively discussed with the team. The product owner's responsibility is to maintain and refine the backlog, ensuring alignment with stakeholder needs while also preserving team focus and avoiding unnecessary disruption during an ongoing sprint.
From the PMI Agile Practice Guide:
"Product backlog refinement is an ongoing process in which the product owner and the team collaborate on the details of backlog items. This includes analyzing, estimating, and prioritizing items to reflect the latest feedback and business needs." (PMI Agile Practice Guide, Section 5.2 - Product Backlog Refinement)
"Agile teams embrace change, especially when it delivers value. However, they also maintain sustainable pace and focus by avoiding mid-sprint scope changes unless absolutely necessary. Backlog items are reviewed and reprioritized before the next sprint begins." (PMI Agile Practice Guide, Section 3.4 - Value-Driven Delivery) From Mike Griffiths' PMI-ACP Exam Prep Book:
"While agile encourages responding to change, disrupting sprint commitments can erode team trust and productivity. Sprint planning is the correct forum to reprioritize work based on new stakeholder insights." (Mike Griffiths, Chapter 5 - Adaptive Planning) Why the other options are incorrect:
* B introduces mid-sprint disruption and disregards agile best practices for maintaining sprint integrity and team focus.
* C eliminates team collaboration and risks breakdowns in communication, violating agile's emphasis on transparency and teamwork.
* D disregards valuable feedback and delays addressing important stakeholder needs, which could compromise customer satisfaction and strategic alignment.