PMI PMI-ACP Practice Test Questions Answers

Security features are typically considerednon-functional requirements (NFRs), which should be captured in theproduct backlogand prioritized accordingly. As per thePMI Agile Practice Guide (Section 5.1: Product Backlog)andMike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery), any requested functionality—whether business- or system-level—must beclearly defined as a backlog itemso the team can plan for it.

Option Ais correct: security requirements should beadded to the backlog and prioritizedlike other features.

Option Bmay come later if implementation is unclear, but first, the work must be defined and logged.

Option CandDrepresent clarification steps but don’t directlysupport implementationas backlog management does.

The correct answer is D — Explain to the team the importance of reducing team size by reducing specializations and bottlenecks and that every team member plays an equal part.

Agile promotes cross-functional, self-organizing teams where all members are responsible for delivering a working product increment. Avoiding specialized silos reduces bottlenecks and improves overall flow. Everyone contributes based on team needs, not personal preferences or status.

PMI Agile Practice Guide:

“Agile teams minimize individual silos by encouraging cross-functional collaboration. Everyone contributes to the team goal, even if the task is outside their core skillset.”

(PMI Agile Practice Guide, Section 6.1 – Team Composition)

Mike Griffiths:

“Specialization often becomes a bottleneck in agile teams. Agile promotes generalizing specialists—team members who are willing to stretch outside their expertise to help the team meet its goals.”

(PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A promotes a command-and-control model—contrary to Agile servant leadership.

B reinforces silos and inefficiency.

C contradicts Agile’s emphasis on team ownership.

Answer: D

—

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.

Answer: D

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

Agile emphasizesjust enough detailto start work and adapt through ongoing conversation. According to thePMI Agile Practice Guide (Section 5.2 Requirements and User Stories), stories should beclear enough for estimation and discussion, but not over-specified. The INVEST model (Independent, Negotiable, Valuable, Estimable, Small, Testable) supports this.

Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning)reiterates that stories should not contain exhaustive detail up front; rather, they evolve throughcollaborative dialoguewith the product owner.

Option Cis correct because it supports collaboration and adaptive planning.

Option AandBlead to over-specification and undermine agility.

Option Daddresses testing but doesn’t resolve confusion about appropriate story detail.

To improve collaboration, it's essential that the team members understand the importance of the project vision statement and feel empowered to contribute. Setting clear expectations ensures that all participants know the purpose of the meeting and their role in contributing. By encouraging everyone to share their ideas and perspectives, the team can reach a consensus or at least acknowledge differing views in a constructive way. This fosters a collaborative environment where team members feel their input is valued.