Declining Sprint Velocity and Team Morale: Root Cause Analysis
In an agile project, the sprint velocity has been dropping for three consecutive sprints. The team is demotivated and blaming each other during retrospectives. What should you do as the project manager?
Quick Answer
Facilitating a root cause analysis works because it reframes a demoralizing, blame-driven retrospective into a constructive, systems-focused one, which is exactly the shift needed when a team has started attributing declining performance to each other rather than to the actual obstacles in their way. Velocity trends downward for structural reasons far more often than for effort reasons: accumulating technical debt, unclear requirements, external dependencies, or process friction are common culprits, so redirecting the team's energy toward identifying and removing those specific impediments addresses the real problem instead of the symptom of interpersonal friction it has produced. This approach also rebuilds trust, because it signals that the retrospective is a safe space for surfacing problems rather than a forum for assigning fault, which is central to what makes retrospectives effective in the first place. Simply telling the team to work harder, replacing team members, or ignoring the blame dynamic and hoping it resolves itself would leave the underlying impediments in place and likely worsen morale further. Whenever a scenario shows a team's performance metrics declining alongside rising interpersonal tension or blame, look for the answer that shifts the group's focus toward identifying systemic causes collaboratively, since that combination of diagnosis and shared ownership is what restores both performance and trust.
⚠ Common exam trap
Test-takers frequently confuse velocity as a performance metric rather than a planning tool, leading them to choose punitive or superficial fixes like setting higher targets or reducing workload instead of diagnosing the systemic impediments.
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
✓
Facilitate a root cause analysis session to identify impediments and collaboratively find solutions
The root cause analysis session directly addresses the team's demotivation and blame culture by shifting focus to systemic impediments rather than individual performance. In agile, velocity drops often stem from process issues, technical debt, or external blockers—not lack of effort. Facilitating a collaborative session aligns with the PMI's emphasis on servant leadership and removing impediments to restore team morale and productivity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Facilitate a root cause analysis session to identify impediments and collaboratively find solutions
Why this is correct
Root cause analysis helps the team address underlying issues and rebuild trust.
- ✗
Set higher performance targets to push the team to improve
Why it's wrong here
Higher targets without support can demotivate the team further.
- ✗
Reduce the sprint workload to boost velocity
Why it's wrong here
Reducing workload artificially inflates velocity but does not improve productivity.
- ✗
Replace underperforming team members
Why it's wrong here
Replacing team members is a drastic step and may not be necessary.
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Scrum Methodology
Scrum is a lightweight process framework that helps teams deliver complex projects in small, iterative chunks called sprints.
Key term
Project Management Plan
A formal, approved document that defines how a project is executed, monitored, controlled, and closed, serving as the single source of truth for the project team.
About these practice questions
Courseiva writes every PMP question from scratch — 800 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 →
Same concept, more angles
3 more ways this is tested on PMP
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your agile project team has been consistently delivering high-quality work, but sprint velocity has dropped over the last three sprints. The team reports feeling overworked and demotivated. What should you do FIRST?
easy- ✓ A.Facilitate a retrospective to identify root causes and collaboratively develop improvements
- B.Reduce the sprint scope to increase velocity
- C.Replace the scrum master with a more experienced one
- D.Ask the team to work overtime to regain velocity
Why A: Facilitating a retrospective is the correct first step because it empowers the team to collaboratively identify the root causes of the decreased velocity and demotivation, such as technical debt, unclear requirements, or process inefficiencies. This aligns with the agile principle of continuous improvement and servant leadership, where the project manager acts as a facilitator rather than imposing solutions. Addressing the underlying issues through team-driven improvements is more sustainable than forcing scope or personnel changes.
Variation 2. Your agile team has been experiencing declining velocity over the last three sprints. Retrospectives have not identified a clear cause. Several team members mention feeling fatigued and demotivated. As the project manager, what should you do first?
easy- A.Add more team members to the project to distribute the workload
- B.Escalate the velocity drop to the steering committee and ask for guidance
- ✓ C.Schedule individual one-on-one meetings with team members to understand their concerns and identify obstacles
- D.Set stricter deadlines and increase velocity targets to motivate the team
Why C: The first step when facing declining velocity and team demotivation is to engage directly with team members through one-on-one meetings to uncover root causes. This aligns with the PMP's servant leadership approach, where understanding individual concerns and removing obstacles is prioritized before any process or resource changes. The retrospective has already failed to identify the cause, so deeper, private conversations are needed to surface issues like burnout, interpersonal conflicts, or unclear requirements.
Variation 3. Your agile team has been working together for three months, and you notice that sprint velocity has been steadily declining. During the retrospective, team members mention they feel overworked and unclear about priorities. What is the BEST action to take?
easy- ✓ A.Facilitate a discussion with the product owner and team to reprioritize the backlog and reduce workload
- B.Add more team members to the next sprint to increase capacity
- C.Ask the team to work overtime for the next two sprints to catch up
- D.Implement a daily stand-up meeting to track progress more closely
Why A: It directly addresses the root causes of declining velocity: unclear priorities and overwork. By facilitating a discussion between the team and the product owner, you enable collaborative backlog reprioritization and workload adjustment, which aligns with the agile principle of sustainable pace and the servant leadership role of the project manager. This action empowers the team to focus on the highest-value work while reducing burnout, which is the most effective way to restore velocity.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMP practice question is part of Courseiva's free PMI 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 PMP exam.