PK0-005 Tools and Documentation Practice Question
During a sprint review, the product owner notices that the team completed 30 story points in the previous sprint and 25 in the current sprint. The project manager wants to track the average story points completed per sprint to predict future performance. Which metric should be used?
⚠ Common exam trap
PK0-005 often tests whether candidates confuse velocity (average points per sprint) with burndown/burnup charts (visual progress tools) — the trap is picking a chart because it sounds agile, when the question asks for the predictive metric itself.
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
✓
Velocity
Velocity is the agile metric that measures the average number of story points a team completes per sprint, and it is used to forecast how much work the team can deliver in future sprints. With 30 points in one sprint and 25 in the next, the average velocity is 27.5, which the project manager can use for release planning and capacity forecasting. This is exactly the metric the question describes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Burnup chart
Why it's wrong here
A burnup chart plots completed work against total scope over time, showing progress and scope changes, not an average of story points per sprint. It is tempting because it tracks completion, but the requested metric is velocity, the rolling average of story points finished each sprint.
- ✗
Burndown chart
Why it's wrong here
A burndown chart plots remaining work against time within a single sprint, showing daily progress toward the sprint goal. It does not average completed story points across sprints. It is tempting because it visualises work completed, but it would be the right choice for tracking whether one sprint is on track, not for predicting future capacity.
- ✓
Velocity
Why this is correct
Velocity measures the average story points a team completes per sprint, directly satisfying the product owner's need to predict future performance from the 30- and 25-point sprints. Unlike cumulative flow or burndown, which track work remaining over time, velocity averages completed points across iterations, giving the forward-looking capacity forecast requested.
- ✗
Planned value
Why it's wrong here
Planned value measures budgeted cost of work scheduled in earned value management, expressed in currency, not story points completed. It cannot average sprint throughput. It is tempting because it forecasts performance against a baseline, but that baseline is cost and schedule, so it would be correct for cost or schedule variance reporting, not agile velocity.
Go deeper
Related to this question
About these practice questions
This PK0-005 question is part of Courseiva's 954-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.