- A
Add more team members to increase velocity.
Why wrong: Adding people may increase communication overhead and reduce velocity initially.
- B
Extend the sprint duration to complete more work.
Why wrong: Fixed-length sprints are a core agile principle.
- C
Ask the product owner to prioritize only critical stories.
Why wrong: Prioritization is important but does not solve the estimation inaccuracy.
- D
Reestimate the remaining work and adjust the release plan.
Using historical velocity to forecast is agile best practice.
Quick Answer
The correct answer is to reestimate the remaining work and adjust the release plan. This is the right move because agile velocity adjustment relies on empirical data—when actual velocity is 30% lower than estimated due to unforeseen technical debt, the project manager must recalculate the team’s true capacity and realign the release plan accordingly, rather than pushing the team to meet an unrealistic target. On the CompTIA Project+ PK0-005 exam, this scenario tests your understanding of adaptive planning under the “inspect and adapt” principle; a common trap is choosing to add more resources or extend sprint length, which violates agile’s focus on sustainable pace and transparency. Remember the memory tip: “Velocity is a fact, not a target—reestimate, don’t accelerate.”
PK0-005 Project Management Concepts Practice Question
This PK0-005 practice question tests your understanding of project management concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A project manager is leading a software upgrade project. The project is using an agile methodology with two-week sprints. After three sprints, the team has not completed all planned user stories, and the product owner is frustrated. The project manager reviews the velocity and finds it is 30% lower than estimated. The team cites unforeseen technical debt. What should the project manager do?
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
Reestimate the remaining work and adjust the release plan.
Option D is correct because the project manager should first reestimate the remaining work based on the actual velocity (30% lower than planned) and then adjust the release plan accordingly. This aligns with agile principles of data-driven planning and transparency, addressing the root cause (unforeseen technical debt) by incorporating the team's actual capacity into future sprints.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add more team members to increase velocity.
Why it's wrong here
Adding people may increase communication overhead and reduce velocity initially.
- ✗
Extend the sprint duration to complete more work.
Why it's wrong here
Fixed-length sprints are a core agile principle.
- ✗
Ask the product owner to prioritize only critical stories.
Why it's wrong here
Prioritization is important but does not solve the estimation inaccuracy.
- ✓
Reestimate the remaining work and adjust the release plan.
Why this is correct
Using historical velocity to forecast is agile best practice.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose to 'add more team members' (Option A) or 'extend sprint duration' (Option B) as intuitive fixes, but the exam tests the agile principle of adapting the plan based on empirical data (velocity) rather than forcing scope or schedule changes that ignore the underlying technical debt.
Detailed technical explanation
How to think about this question
Velocity is a key agile metric calculated as the sum of story points completed per sprint. When actual velocity is 30% lower than estimated, the project manager must use the new velocity to reforecast the release burn-down chart. Technical debt (e.g., accumulated code complexity, missing tests) reduces the team's effective capacity; reestimating remaining stories with this debt factored in ensures the release plan reflects reality, allowing the product owner to make informed trade-offs between scope, time, and quality.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the PK0-005 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Project Management Concepts — study guide chapter
Learn the concepts, then practise the questions
- →
Project Management Concepts practice questions
Targeted practice on this topic area only
- →
All PK0-005 questions
500 questions across all exam domains
- →
CompTIA Project+ PK0-005 study guide
Full concept coverage aligned to exam objectives
- →
PK0-005 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PK0-005 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Project Life Cycle Phases practice questions
Practise PK0-005 questions linked to Project Life Cycle Phases.
Basics of IT Infrastructure and IT Project Management practice questions
Practise PK0-005 questions linked to Basics of IT Infrastructure and IT Project Management.
Project Management Concepts practice questions
Practise PK0-005 questions linked to Project Management Concepts.
Tools and Documentation practice questions
Practise PK0-005 questions linked to Tools and Documentation.
PK0-005 fundamentals practice questions
Practise PK0-005 questions linked to PK0-005 fundamentals.
PK0-005 scenario practice questions
Practise PK0-005 questions linked to PK0-005 scenario.
PK0-005 troubleshooting practice questions
Practise PK0-005 questions linked to PK0-005 troubleshooting.
Practice this exam
Start a free PK0-005 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PK0-005 question test?
Project Management Concepts — This question tests Project Management Concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Reestimate the remaining work and adjust the release plan. — Option D is correct because the project manager should first reestimate the remaining work based on the actual velocity (30% lower than planned) and then adjust the release plan accordingly. This aligns with agile principles of data-driven planning and transparency, addressing the root cause (unforeseen technical debt) by incorporating the team's actual capacity into future sprints.
What should I do if I get this PK0-005 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.