mediumMultiple Choice
PK0-005 Practice Question: A project team is using an agile methodology and…
A project team is using an agile methodology and the product owner frequently changes priorities mid-sprint. What is the most likely consequence?
⚠ Common exam trap
CompTIA often tests the misconception that the product owner's authority to change priorities always leads to better stakeholder satisfaction, but the trap here is that mid-sprint changes actually break the core agile principle of a stable sprint goal, causing missed commitments and reduced trust.
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
✓
Missed sprint goals
In agile methodology, the sprint is a time-boxed iteration with a fixed scope of work committed by the team. When the product owner frequently changes priorities mid-sprint, it disrupts the team's focus and capacity, making it highly likely that the original sprint goals will not be completed. This directly leads to missed sprint goals, as the team cannot deliver the planned work within the sprint's fixed duration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increased team morale
Why it's wrong here
Constant priority churn creates rework and unfinished stories, which frustrates teams and lowers morale rather than raising it. Increased morale is tempting because agile's self-organising teams and short feedback loops genuinely boost morale when the sprint goal is protected from mid-sprint changes.
- ✗
Better stakeholder satisfaction
Why it's wrong here
Frequent mid-sprint reprioritisation disrupts delivery and erodes trust, so stakeholder satisfaction generally suffers rather than improves. It is tempting because agile's iterative reviews and frequent releases do raise satisfaction when priorities are stable within a sprint, which is when this outcome would be correct.
- ✗
Higher quality deliverables
Why it's wrong here
Mid-sprint priority changes force work in progress to be abandoned or reworked, so quality typically falls rather than rises. Higher quality is tempting because agile's short iterations and continuous feedback genuinely improve quality when the sprint backlog stays stable, which is the scenario where this would hold.
- ✓
Missed sprint goals
Why this is correct
Mid-sprint priority changes inject unplanned work, so the team's committed sprint backlog no longer matches capacity. Scope is fixed for the sprint while the product owner keeps reprioritising, making the sprint goal unachievable and predictably missed.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PK0-005 question from scratch — 954 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.