PK0-005 Tools and Documentation Practice Question
During a software development project, the team estimates story points using planning poker. A story is estimated at 8 points, while a similar story was previously estimated at 5 points. What is the primary reason for using relative sizing with story points?
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 compare the effort of stories relative to each other
Story points are a relative measure of effort; the exact values are less important than the relative comparison. Planning poker facilitates consensus.
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 assign story points based on the developer’s skill level
Why it's wrong here
Story points are based on effort, not skill.
- ✗
To track the number of story points completed per day
Why it's wrong here
Velocity is per sprint, not per day.
- ✗
To calculate exact hours needed for each story
Why it's wrong here
Story points are not tied to hours; they are relative.
- ✓
To compare the effort of stories relative to each other
Why this is correct
Story points are relative sizing, not absolute.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PK0-005 question from scratch — 980 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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.