Agile Velocity Drop Due to Technical Debt: What Should the Project Manager Do First?
Your agile project has seen sprint velocity drop for the past three sprints. The team attributes it to increasing technical debt. As the project manager, what should you do FIRST?
Quick Answer
The correct first step is to facilitate a discussion with the product owner to allocate time for refactoring in the next sprint. This is because technical debt acts as a hidden drag on velocity, forcing the team to spend effort on fixing brittle code rather than delivering new features; without explicit capacity for refactoring, the debt compounds and velocity continues to drop. On the PMP exam, this scenario tests your understanding of the agile principle that the project manager serves as a servant leader who removes impediments by negotiating with the product owner, not by unilaterally assigning work or ignoring the debt. A common trap is to jump into root-cause analysis or team retraining, but the immediate priority is securing dedicated time for refactoring to restore sustainable pace. Remember the mnemonic “Debt First, Discuss Next” — when velocity drops due to technical debt, your first action is always to discuss and allocate time, not to analyze the debt’s origin.
⚠ Common exam trap
Many exam-takers think reducing scope (Option B) is a valid first step, but the PMP exam tests the principle of addressing root causes (technical debt) through collaboration with the product owner, not just compensating for symptoms.
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 discussion with the product owner to allocate time for refactoring in the next sprint
The first step when technical debt impacts velocity is to collaborate with the product owner to prioritize refactoring. As the project manager, you should facilitate a discussion to allocate dedicated time in the next sprint for addressing technical debt, ensuring the team can sustainably improve velocity without compromising quality or overworking.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Bring in external consultants to fix the technical debt
Why it's wrong here
External consultants lack the team's context and cannot decide which debt to repay first; the project manager should first make the debt visible and prioritise it with the team. Consultants are tempting for specialist legacy remediation, but that follows diagnosis, not precedes it.
- ✗
Reduce the scope of future sprints to compensate
Why it's wrong here
Reducing scope treats the symptom while the debt continues accruing, and it hides the real capacity loss from stakeholders. It is tempting because protecting the sprint goal feels pragmatic, but the first step is to surface and prioritise the debt with the team, not shrink delivery.
- ✗
Ask the team to work extra hours to maintain velocity while addressing debt
Why it's wrong here
Extra hours address neither the debt's cause nor its prioritisation, and sustained overtime degrades quality and velocity further. It is tempting because it appears to preserve throughput, but the first action is to make the debt visible and schedule its repayment with the team.
- ✓
Facilitate a discussion with the product owner to allocate time for refactoring in the next sprint
Why this is correct
Facilitating product owner discussion to allocate refactoring time addresses the technical debt the team identified as velocity's root cause. This engages the person controlling backlog priority, ensuring remediation work enters the sprint rather than being perpetually deferred, which is the necessary first step before velocity can recover.
Go deeper
Related to this question
About these practice questions
One of 820 original PMP practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way 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. In an agile software project, the sprint velocity has dropped from 30 story points to 18 over the last two sprints. The team members report that they are spending too much time on unplanned technical debt. The product owner is pushing for more features. What should the project manager do FIRST?
hard- A.Reassign two team members to a separate 'debt reduction' team to isolate the issue
- B.Remove testing from the definition of done to increase velocity
- C.Increase the sprint workload to motivate the team to deliver more features
- ✓ D.Facilitate a discussion between the team and product owner to prioritize technical debt alongside new features
Why D: The project manager's first responsibility is to facilitate a collaborative discussion between the team and the product owner to address the root cause—unplanned technical debt—while balancing the need for new features. This aligns with the agile principle of transparency and stakeholder collaboration, ensuring that technical debt is explicitly prioritized in the backlog alongside feature work. Removing or ignoring the debt would only compound the velocity drop and degrade product quality.
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.