Early in 2018, a translation initiative of the Scrum Glossary took off. It is amazing that there are currently 20 languages in the works. A new release is envisioned before the end of 2018. No deadlines though, no stress.
“Failed Sprint” is not part of the glossary, although a definition might still be helpful.
4 thoughts on “Failed Sprint (a definition)”
In my eyes, unless canceled, a sprint always succeeds. Until the world ends…
It’s a timebox, it has served its purpose and has succeeded when it ends. Though you can do quite a few things to diminish your learning from such a timebox. That’s maybe a failure of the scrum team then.
I would put it even stronger. Not even a canceled Sprint is a failed Sprint. It was canceled because -for whatever (really important) reason- it totally made no sense to continue the Sprint. Still not what I would consider a failed Sprint.
Even if we cancel a Sprint, there most likely will be learnings, hence not a failed Sprint. Would you agree?
Not sure, Ari. A cancelled Sprint, in my view, is just that, a cancelled Sprint. A Sprint that was stopped.
It is traumatic, but probably even less about fail/success than anything else in Scrum. The only certainty is that such a Sprint did not deliver the value or return that was hoped for.