The correct answer is D - Estimating the relative size of stories by using story points.
Planning poker is a consensus-based estimation technique used in Agile to assign relative size (often using story points) to product backlog items. Each team member selects a card to indicate their estimate, and the group discusses discrepancies to reach agreement.
From the PMI Agile Practice Guide:
"Planning poker is a consensus-based estimation technique that helps teams estimate the size of user stories using story points. It supports collaboration and shared understanding." (PMI Agile Practice Guide, Section 5.3 - Estimation Techniques) Mike Griffiths writes:
"Planning poker helps teams perform relative sizing using a modified Fibonacci sequence. The goal is not precision, but shared understanding and relative complexity comparison." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 - Adaptive Planning) Why other options are incorrect:
* A describes analogy-based estimation, not planning poker.
* B refers to "bucket system" estimation, a separate technique.
* C refers to dot voting, which is a prioritization-not estimation-tool.

The Definition of Done (DoD) is a crucial agile practice that outlines the agreed-upon criteria for when a deliverable is considered complete and ready for release. It ensures that all aspects of the deliverable meet the necessary standards and requirements before it is finalized. Additionally, theteam should demonstrate the deliverable, typically during a sprint review or other appropriate meeting, to confirm that it meets stakeholder expectations and aligns with the project goals. This practice helps ensure that the deliverables are truly complete and ready for release, avoiding rework and maintaining a high level of quality.

The correct answer is D - Up-to-date project radiators.
Information radiators provide at-a-glance visibility into project status, progress, blockers, and other key metrics. Sharing or including these visual tools in extended stakeholder communication ensures transparency and up-to-date awareness, which aligns with agile values.
PMI Agile Practice Guide:
"Information radiators provide immediate and transparent access to project health and status. They reduce the need for formal reporting and keep stakeholders aligned in real time." (PMI Agile Practice Guide, Section 5.6 - Information Radiators) Mike Griffiths:
"Using radiators to keep stakeholders informed improves trust, accelerates decision-making, and supports ongoing engagement." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A and B are not relevant for stakeholder reporting.
* C is too narrow and lacks the holistic view offered by radiators.

Pull communication is most effective for a distributed team working across multiple locations, especially when task-oriented communications and discussion boards are involved. With pull communication, team members can access information when needed, such as through shared documents, wikis, or discussion boards. This ensures that communication is effective and available asynchronously, allowing the team to collaborate and stay informed without needing tobe online at the same time. This method is particularly useful when managing a geographically dispersed team.

In agile, theProduct Owner is the ultimate decision-makerregarding backlog prioritization and scope changes. According to thePMI Agile Practice Guide (Section 5.1: Backlog Prioritization), any changes that affect value delivery, schedule, or scopeshould be discussed with the Product Owner, who evaluates the business impact.
Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery)reinforces that product direction and scope decisions must be handled through collaboration between the team and the Product Owner.
* Option Dis correct: seeking Product Owner input ensures value-based decision-making and customer alignment.
* Option A(re-estimating the entire project) is unnecessary and burdensome.
* Option Brejects valuable input and ignores iterative flexibility.
* Option Cgoes against agile principles of focus and sustainable pace.