Agile Velocity Drop: Root Cause Analysis Through Retrospectives

• A.Increase the team size by adding new members to distribute the workload
• ✓ B.Hold a retrospective focused on identifying the causes of overtime and discuss ways to improve sustainable pace
• C.Reduce the scope of the next sprint to give the team a break
• D.Inform the product owner that the team cannot commit to any new features until morale improves

Why B: Option B is correct because the first step when facing burnout and overtime is to hold a retrospective to identify root causes and discuss sustainable pace improvements. This aligns with the agile principle of continuous improvement and the PMP People domain focus on team motivation and well-being. Addressing the underlying issues before taking corrective actions ensures long-term productivity rather than temporary fixes.

• A.Reduce the sprint backlog to lower the team's workload
• B.Ask the functional manager to add more developers to the team
• ✓ C.Facilitate a sprint retrospective to identify the causes of the velocity drop and collaboratively develop an improvement plan
• D.Ask the product owner to prioritize fewer stories in the next sprint

Why C: Option C is correct because the Scrum Master's first responsibility is to facilitate a retrospective to uncover the root causes of the velocity drop and the changing definition of 'done.' This aligns with the PMP's emphasis on leading the team through collaborative problem-solving rather than imposing top-down solutions. The team's feedback about being overwhelmed and the shifting 'done' criteria indicates a process breakdown that requires team-driven improvement.

• A.Remove the team's external dependencies by negotiating with stakeholders.
• B.Replace the scrum master with a more experienced one.
• ✓ C.Facilitate a root cause analysis with the team to identify underlying issues and create an action plan.
• D.Increase the sprint duration to give the team more time.

Why C: Option C is correct because the first step when facing a consistent drop in velocity and team demotivation is to facilitate a root cause analysis with the team. This aligns with the PMP's focus on servant leadership and empowering the team to identify and solve their own problems, rather than imposing external solutions. The retrospective has failed to produce actionable improvements, so a deeper, facilitated analysis is needed to uncover the true underlying issues, which may include but are not limited to external dependencies.

• A.Reassign work to individual contributors to increase accountability
• B.Increase the sprint length to give the team more time
• ✓ C.Conduct a retrospective to identify and address the root causes of the drop
• D.Replace two team members with more productive resources

Why C: The correct answer is C because the team's velocity drop and demotivation are symptoms of underlying issues that need to be uncovered through a retrospective. In agile, the retrospective is the primary mechanism for continuous improvement, allowing the team to inspect its processes, identify root causes (e.g., technical debt, unclear requirements, or interpersonal friction), and adapt. Reassigning work or replacing team members would bypass the team's self-organization and likely worsen morale, while increasing sprint length treats a symptom without addressing the cause.