PK0-005 Tools and Documentation Practice Question
A project team uses planning poker to estimate user stories. What is the purpose of this technique?
⚠ Common exam trap
The trap is confusing estimation activities with planning or definition activities — candidates pick 'assign tasks' or 'define Definition of Done' because those are also team ceremonies, but planning poker's sole output is a consensus effort estimate.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
To reach a consensus on effort estimates
Planning poker is an agile estimation technique in which each team member privately selects a card representing their effort estimate (often Fibonacci numbers) for a user story, then all cards are revealed simultaneously. Discrepancies are discussed, and the team re-votes until they converge on a shared estimate. Its core purpose is to reach consensus on effort estimates while surfacing differing assumptions early.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To define the Definition of Done
Why it's wrong here
Planning poker estimates relative size or effort; the Definition of Done is a shared quality checklist agreed separately. It is tempting because both are agile ceremonies artefacts, but poker never sets completion criteria, and conflating them would let estimation sessions redefine acceptance standards.
- ✗
To assign tasks to team members
Why it's wrong here
Planning poker produces relative effort estimates through consensus, not task allocation. It is tempting because the team gathers and discusses work, but assignment happens during sprint planning or task breakdown; estimation deliberately excludes who does what, so this misreads the technique's output.
- ✓
To reach a consensus on effort estimates
Why this is correct
Planning poker achieves consensus by having each estimator reveal their card simultaneously, exposing divergent assumptions before discussion. This satisfies the stem's requirement directly: the technique's purpose is collective agreement on effort, not individual accuracy or velocity forecasting. Divergence triggers debate, then re-estimation, converging the team on one shared estimate.
- ✗
To create a Gantt chart
Why it's wrong here
Planning poker yields story point estimates; a Gantt chart is a schedule built from durations, dependencies and dates. It is tempting because both support planning, but poker produces no timeline data, and converting points to calendar bars requires separate velocity and duration assumptions.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PK0-005 question from scratch — 954 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This PK0-005 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PK0-005 exam.