The correct answer is to ask the team to estimate the new feature and then decide with the product owner to replace a lower-priority item. This approach is correct because Agile handles new feature requests during a sprint by prioritizing the product backlog without breaking the sprint goal; the team’s velocity of 30 points per sprint provides a data-driven basis for swapping scope, ensuring the schedule baseline remains intact. On the CompTIA Project+ PK0-005 exam, this tests your understanding of the product owner’s role in backlog prioritization and the practical use of velocity for trade-off decisions, with a common trap being to add the feature without removing anything, which would inflate scope and delay the release. A useful memory tip is “Swap, don’t stack”—when a new feature request arises mid-sprint, replace a lower-priority item rather than piling on work, keeping the sprint’s capacity balanced.
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.
You are the project manager for an IT project to upgrade the company's network infrastructure. The project has a schedule baseline approved, and the team is using Agile methodology due to changing requirements. During the second sprint, a key stakeholder requests a new feature that was not originally planned. The team is concerned this will impact the sprint goal. The project is being tracked with a burn-down chart, and the velocity so far is 30 points per sprint. The product owner is hesitant to include the new feature because it will increase the scope and delay the release. As the project manager, what should you do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Ask the team to estimate the new feature and then decide with the product owner to replace a lower-priority item.
In Agile, the product owner is responsible for prioritizing the backlog, and the team's velocity (30 points per sprint) provides a data-driven way to assess trade-offs. Asking the team to estimate the new feature and then deciding with the product owner to replace a lower-priority item respects the sprint goal while allowing scope adjustment without breaking the schedule baseline. This approach aligns with Agile principles of responding to change and maintaining sustainable pace.
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.
✓
Ask the team to estimate the new feature and then decide with the product owner to replace a lower-priority item.
Why this is correct
Agile allows swapping items based on priority after estimation.
Related concept
Read the scenario before looking for a memorised answer.
✗
Reject the request because it is outside the original scope.
Why it's wrong here
Agile embraces change; rejection may hinder value delivery.
✗
Escalate to the sponsor to get approval for a change request.
Why it's wrong here
The product owner is the appropriate decision-maker for scope within the project.
✗
Add the feature to the next sprint backlog to accommodate the stakeholder.
Why it's wrong here
This may overload the team and disrupt the sprint goal.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CompTIA often tests the misconception that any scope change must go through formal change control (Option C), but in Agile, the product owner and team can handle scope trade-offs within the sprint as long as the sprint goal is preserved.
Detailed technical explanation
How to think about this question
The burn-down chart tracks remaining work against time, and velocity (30 points/sprint) is a historical average used for forecasting. When a new feature is estimated, the team can calculate its point value and compare it to the lowest-priority item in the current sprint; if the new feature's points are less than or equal to that item, a swap keeps the sprint backlog size constant and the burn-down trajectory intact. In real-world scenarios, this technique prevents scope creep while accommodating emergent requirements, and it requires the team to have a well-groomed backlog with clear priority rankings.
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 — 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: Ask the team to estimate the new feature and then decide with the product owner to replace a lower-priority item. — In Agile, the product owner is responsible for prioritizing the backlog, and the team's velocity (30 points per sprint) provides a data-driven way to assess trade-offs. Asking the team to estimate the new feature and then deciding with the product owner to replace a lower-priority item respects the sprint goal while allowing scope adjustment without breaking the schedule baseline. This approach aligns with Agile principles of responding to change and maintaining sustainable pace.
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 →
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.
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.