No running!

August 24, 2022
By calling iterations "Sprints", Scrum implies a need for constant running. Don't be fooled.

No running!

Take your time.

Slow is smooth. Smooth is fast.

Find a sustainable pace.

An occasional sprint may be appropriate, but not always.

This is one thing that annoys me about Scrum. By calling iterations “Sprints”, the framework implies a need for constant running. I suppose the name has stuck, as an hommage to the rugby metaphor, after which Scrum itself is named. But don’t be fooled.

You should not… cannot always be running.

Slow down.

Share this

Related Content

"Agile" isn't about delivering every sprint

Frequently delivering software, but not considering feedback on how to improve, isn't agile.

Two modes of agile failure

I've heard both "Agile is only good for developers" and "Agile is only good for management". I think they're two modes of the same failure.

Scrum is great in theory, but "it will never work in the real world"

I think there are two "real worlds", and they often clash. One where Agile, Scrum, XP, and DevOps make perfect sense. Another where they don't.