During a sprint retrospective, the team expresses frustration that they are frequently interrupted by unplanned support requests from the operations department. The product owner agrees this is impacting velocity. What should the project manager do FIRST?
This is the most effective agile approach because it involves the Product Owner (PO) in managing the product backlog, which encompasses all work, including support. By prioritizing support requests and allocating a dedicated buffer (e.g., a percentage of sprint capacity or a rotating team member), the team can proactively manage interruptions without derailing sprint goals. This strategy protects the team's focus and morale while ensuring critical support needs are addressed in a structured manner.
Why this answer
The immediate priority is to manage the unplanned work that is disrupting the sprint. By working with the product owner to prioritize support requests and allocate a dedicated buffer (e.g., a fixed capacity within the sprint backlog), the project manager ensures that the team can handle operational interruptions without derailing planned work. This aligns with the Agile principle of protecting the team's focus and using empirical data to adjust the process, rather than escalating or deferring action.
Exam trap
The trap here is that candidates often choose to escalate (Option B) or defer action (Option C) instead of recognizing that the product owner is the correct stakeholder to collaborate with for immediate prioritization and capacity planning.
How to eliminate wrong answers
Option B is wrong because escalating to the project sponsor is premature; the project manager should first collaborate with the product owner, who is responsible for prioritizing the backlog and managing stakeholder expectations. Option C is wrong because asking the team to track time and report at the next retrospective delays action; the team is already frustrated and velocity is impacted, so a proactive solution is needed now, not after another sprint. Option D is wrong because instructing the team to handle support requests as they come would perpetuate the disruption, undermine sprint planning, and likely reduce velocity further, violating the Scrum principle of protecting the sprint goal.