PMI-ACP Dumps With Exact Questions and Answers

Planning Pokeris a well-known estimation technique where team members use numbered cards (usually Fibonacci series) to estimatestory point valuesbased on relative size. It’s aconsensus-based estimation method, as described in thePMI Agile Practice Guide (Section 5.2: Estimation Techniques)andMike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Estimating Techniques).

Option Dis correct:Planning Pokeris 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 forgrouping stories into size buckets, not direct story point consensus estimation.

The correct answer is C — Facilitate team brainstorming of the risks resulting from complexity for the risk register.

Technical complexity introduces risks that must be identified and managed early. Agile leaders support teams by facilitating collaborative risk identification, not by dictating solutions. Brainstorming sessions help surface concerns and lead to proactive mitigation strategies.

PMI Agile Practice Guide:

“Risks are best identified through team collaboration. Facilitated risk identification sessions encourage broad participation and lead to better awareness and ownership of potential issues.”

(PMI Agile Practice Guide, Section 7.3 – Risk Management)

Mike Griffiths:

“In agile projects, technical risks are treated early. Collaborative identification and visibility are key to creating a risk-adjusted delivery plan.”

(PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

A is valid long-term, but brainstorming comes first for awareness.

B limits risk planning to a fixed period (Sprint 0), which may not be enough.

D promotes innovation but not structured risk identification.

Answer: C

—

A key agile principle is that user stories should includeclear acceptance criteria, which must bereviewed and accepted by the product owner. According to thePMI Agile Practice Guide (Section 5.2: User Stories and Acceptance Criteria)andMike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery), acceptance criteria ensure that the team and product ownershare a clear understandingof what constitutes “done.”

Option Ais correct: having the product owner validate acceptance criteria ensures alignment.

Option Baddresses technical quality but not stakeholder dissatisfaction.

Option Cunfairly shifts blame without addressing communication.

Option Dgoes against agile’s iterative and flexible nature.