PK0-005 Tools and Documentation Practice Question
An agile team uses story points for estimating effort. During sprint planning, the team's average velocity is 30 story points per sprint. The product owner wants to commit to 35 story points for the upcoming sprint. What should the team do?
⚠ Common exam trap
PK0-005 often tests whether candidates understand that velocity is an empirical planning input, not a target to be dictated by the product owner — options that 'satisfy the PO' or 'extend the sprint' are classic distractors.
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
✓
Commit to 30 story points based on historical velocity.
Velocity is the team's historical throughput, and committing to more than average velocity without a concrete capacity change sets the sprint up for failure. The team should commit to 30 story points based on demonstrated velocity, and if the product owner wants more, the backlog or team capacity must be renegotiated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Remove the definition of done to save time.
Why it's wrong here
Removing the definition of done abandons the shared quality standard, so completed work no longer meets the agreed criteria and velocity becomes meaningless. It is tempting as a way to fit more points into the sprint, and would be correct only when the team deliberately renegotiates that standard with the product owner.
- ✗
Increase the sprint duration to accommodate more points.
Why it's wrong here
Extending the sprint duration changes the timebox, invalidating velocity as a per-sprint measure and concealing the capacity gap rather than addressing it. It is tempting because more days appear to yield more points, and would be correct only if the team permanently re-baselined its sprint length and recalculated velocity.
- ✓
Commit to 30 story points based on historical velocity.
Why this is correct
Historical velocity of 30 story points is the team's demonstrated capacity per sprint. Committing to 35 exceeds that proven throughput, so committing to 30 aligns the sprint commitment with actual delivery data rather than the product owner's aspiration.
- ✗
Accept the 35 story points to satisfy the product owner.
Why it's wrong here
Accepting 35 points commits to work exceeding the team's demonstrated capacity of 30, so the sprint goal is likely missed and the increment incomplete. It is tempting to satisfy the product owner, and would be correct only after the team's velocity genuinely rose through sustained delivery.
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.