PK0-005 Tools and Documentation Practice Question
An agile team uses story points to estimate user stories. During planning poker, one developer consistently gives much higher estimates than the rest of the team. What is the best action for the team?
⚠ Common exam trap
PK0-005 often tests the misconception that estimation is purely mathematical — candidates pick averaging or median thinking it's objective, but agile exams emphasize collaborative discussion and surfacing assumptions over statistical smoothing.
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
✓
Ask the developer to explain their reasoning
In planning poker, a consistently higher estimate from one developer is a signal that they may see complexity, risk, or dependencies the rest of the team has overlooked. The best action is to ask the developer to explain their reasoning so the team can discuss assumptions and converge on a shared understanding, rather than mechanically averaging or discarding the estimate. This preserves the collaborative purpose of story-point estimation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Average the estimates and move on
Why it's wrong here
Averaging ignores valuable input and may miss important risks.
- ✗
Discard the outlier estimate
Why it's wrong here
Discarding the estimate removes a team member's reasoning without discussion, so any genuine risk or hidden complexity stays undiscovered. Discarding outliers is tempting because it cleans the data set, and it would be correct for statistical analysis of noisy measurements, not for collaborative estimation.
- ✗
Use the median estimate
Why it's wrong here
Taking the median silently overrides the team's discussion, hiding the reason behind the high estimate instead of resolving it. Median is tempting because it resists outliers statistically, and it would be correct for aggregating independent numeric forecasts, not for surfacing assumptions during planning poker.
- ✓
Ask the developer to explain their reasoning
Why this is correct
Outliers in planning poker usually signal hidden complexity or misunderstood requirements. Asking the developer to explain their reasoning surfaces assumptions and enables the team to converge on a shared estimate, satisfying the goal of accurate collaborative estimation rather than averaging away genuine insight.
Go deeper
Related to this question
About these practice questions
One of 954 original PK0-005 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.