How to Handle Decreasing Velocity in Agile Projects

• A.Add more user stories to the backlog to increase team motivation.
• B.Ask the product owner to speak with the team about the importance of the sprint goals.
• ✓ C.Facilitate a meeting with the team to review and clarify the sprint goal and ensure alignment.
• D.Report the velocity drop to senior management and ask for intervention.

Why C: Option C is correct because the Scrum Master's first responsibility is to ensure the team understands and aligns on the sprint goal. The disengagement and confusion about sprint goals directly indicate a breakdown in shared understanding, which must be resolved through facilitation before any other action. Addressing this immediately restores focus and can prevent further velocity degradation.

• ✓ A.Conduct a retrospective to identify impediments and improvement actions.
• B.Ask the team to work overtime to catch up on velocity.
• C.Replace the underperforming team members with new resources.
• D.Increase the sprint length to give the team more time.

Why A: The PM should facilitate a retrospective to identify root causes of decreasing velocity and address team morale. Option A is correct because it uses agile ceremonies to collaboratively find improvements. Option B adds pressure without solving root issues; option C ignores team dynamics; option D changes process without understanding impediments.

• A.Require the team to commit to fewer story points next sprint
• ✓ B.Work with the product owner to refine user stories and shield the team from external interruptions
• C.Add more developers to the team to increase velocity
• D.Increase the sprint duration to give the team more time

Why B: Option B is the best action because the root cause is unclear requirements and frequent interruptions. The project manager should work with the product owner to refine user stories and ensure they are clear, and also shield the team from stakeholder interruptions. Option A (reducing story points) does not address the root cause; the team would still face unclear requirements and interruptions. Option C (adding developers) does not solve the clarity or interruption issues and may disrupt the team. Option D (increasing sprint duration) is not appropriate as it does not address the root cause and violates timeboxing principles.

• A.Encourage the team to work overtime to catch up.
• B.Add more team members to increase capacity.
• C.Increase the sprint duration to give the team more time.
• ✓ D.Implement a process to control scope changes during the sprint.
• ✓ E.Limit work-in-progress (WIP) to reduce multitasking.

Why D: Limiting work-in-progress (WIP) can reduce context switching and improve focus. Implementing a change control process for scope changes during a sprint helps stabilize requirements. Both address root causes of velocity drop.

• ✓ A.Facilitate a focused retrospective to identify specific root causes
• ✓ B.Work with the product owner to limit unplanned work from stakeholders
• ✓ C.Review the velocity trend and adjust the sprint backlog accordingly
• D.Reduce the sprint length to increase focus and delivery
• E.Require the team to work overtime to regain lost velocity

Why A: Option A is correct because a focused retrospective can help identify root causes of the velocity drop. Option B is correct because the product owner should manage stakeholder expectations and limit unplanned work. Option C is correct because analyzing velocity trends helps the team adapt their backlog and planning. Option D is incorrect because reducing sprint length typically increases overhead and does not address the surge of unplanned tasks. Option E is incorrect because mandatory overtime leads to burnout and reduced quality, harming long-term productivity.

• A.Increase the frequency of daily standups to twice per day
• B.Add more team members to increase capacity
• C.Assign a senior developer to monitor individual productivity
• ✓ D.Facilitate a retrospective to identify impediments and propose improvements

Why D: Option D is correct because in agile, the retrospective is the appropriate forum for the team to identify and address process issues, such as the drop in velocity and siloed work. Option A is wrong because increasing standup frequency does not address root causes and may add more pressure. Option B is wrong because adding team members can disrupt team dynamics and does not address the underlying issues. Option C is wrong because assigning a senior developer to monitor individual productivity is micromanaging and contrary to agile principles.