Sprint Work Keeps Rolling Over
A Scrum Master’s Guide to Restoring Predictability Without Blame
Q: “Hi Vibhor, I’m struggling with a team that constantly carries work over from one Sprint to the next. During Sprint Planning, they commit to a certain amount of work, but by the end of the Sprint several items remain unfinished. The team says the work is more complex than expected, but this has been happening for the last few Sprints. The Product Owner is frustrated because predictability is missing, and leadership is starting to question the team’s performance. How should I help the team improve without making it feel like a blame exercise?”
Thanks for the question.
This is one of those situations where a Scrum Master can either become a process police or a coach.
Because on the surface, the problem looks simple:
The team said they would finish something, and they did not.
But if you stay only at that surface level, the conversation quickly becomes unhelpful.
The Product Owner starts thinking, “The team is not serious about its commitments.”
The team starts thinking, “The PO does not understand how complex this work is.”
Leadership starts thinking, “Maybe this team is not performing.”
And the Scrum Master gets pulled into the middle, trying to defend the team while also acknowledging that, yes, the problem is real.
This is exactly the moment where your coaching stance matters.
Repeated carryover is a delivery problem. It is ALSO a signal, “Something about the way we plan, refine, slice, collaborate, or communicate is not working.”
The Scrum Master’s job is not to protect the team from accountability. It is also not to allow accountability to become blame.
The job is to help the team and stakeholders inspect the practices being followed honestly, learn from them, and make the next Sprint a little better than the last one.
Let’s look at where the real issues may be hiding.
Got an urgent question?
Get a quick answer by joining the subscriber chat below.
