PMI Updated PMI-ACP Exam Questions and Answers by zayaan

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.

Answer: D

══════════════════════════════════════════════════

After the product vision is communicated, the product owner should ensure that the product backlog is prioritized so the team can focus on delivering the most valuable features first. According to the PMI Agile Practice Guide (Section 5.1 Product Backlog and Vision Alignment), prioritizing the backlog helps teams understand the product roadmap and plan their efforts accordingly.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) reinforces that the product owner’s key responsibility is backlog prioritization, not task management or detailed design.

Option C is correct: prioritizing the backlog enables the team to understand and plan the roadmap.

Option A and B are too detailed for the product owner and move into the team ' s domain.

Option D is a team responsibility, not the product owner’s.

Agile values active stakeholder collaboration and transparency. The best way to address stakeholder concerns is to engage them directly in the feedback loop. The PMI Agile Practice Guide (Section 7.2: Stakeholder Engagement) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) both recommend inviting stakeholders to iteration reviews or demos to provide updates and gather feedback.

Option C is correct: inviting the regional sales manager to the review fosters transparency and collaboration.

Option A and B dismiss valid stakeholder input, which goes against agile principles.

Option D is overly cautious and does not proactively resolve the issue.

The correct answer is C — During the retrospective, discuss the issue and create an action plan to avoid it in the future.

When teams misestimate or experience incomplete work, it’s important to reflect during the retrospective and create action items. This is a fundamental aspect of agile: continuous inspection, adaptation, and team-driven improvement.

PMI Agile Practice Guide:

“Retrospectives help identify opportunities for improvement. The team reviews its estimation accuracy and adjusts processes or practices based on patterns observed.”

(PMI Agile Practice Guide, Section 5.8 — Retrospectives)

Mike Griffiths elaborates:

“Estimating complexity is an area for ongoing learning. Teams use retrospectives to improve their sizing, identify knowledge gaps, and refine their planning techniques.”

(PMI-ACP Exam Prep, Chapter 5 — Adaptive Planning)

Other options:

A unnecessarily involves a project manager (non-agile).

B assumes one-size-fits-all rules, which limits team agility.

D ignores the structured opportunity the retrospective provides for team learning.

Answer: C

—