[jpswade]

> Interruptions and unforeseen tasks will occur.

In a highly interrupted team, sprints don't work. Try lean/Kanban.

You've not mentioned retrospectives, which are an important part of improving your processes, without that how can you make improvements?

There's nothing in agile that talks about deadlines, it's about commitment.

[mdalmijn]

It's a misconception that Sprints don't work when you're highly interrupted. Sprints are as flexible as Kanban, with the only exception that you set a single objective per Sprint. This is the thing that matters most.

If you can't set a single objective per Sprint, then Sprints don't work. Any flexibility argument reflects a poor understanding of Sprints.

Here you can read more: https://mdalmijn.com/p/are-you-practicing-anaconda-or-hummin...

[regularfry]

> commitment

I am convinced that when people talk about burnout from trying to hit sprint goals, it's because of this word, and either being coerced one way or another into commitments they can't meet, or not having enough information or experience to judge what a reasonable commitment is.

It was recently changed in the Scrum Guide from "forecast", which is much more reasonable: you can track forecasts over time to improve them, and nobody expects a forecast to be bang on the money every time. "Commitment" doesn't work that way.