From the #Scrum Guide:
"4. Repeat" (in the section Scrum Definition; in a nutshell: 1. … 2. … 3. …)
From Cambridge Dictionary:
"Repeat: to happen, or to do something more than once."
The definition tells us to do something more than once—but it does not say to do it the same way every time.
A Scrum Team keeps repeating the same steps:
Sprint Planning → the necessary work and the Daily Scrum → Sprint Review → Sprint Retrospective. Repeat.
This does not change. It’s like a heartbeat—providing rhythm, consistency, and structure.
Repetition brings predictability. It reduces complexity. It simplifies.
But what happens within each repetition must evolve.
While the steps stay the same, everything about how the team works will change over time:
How challenges are solved will change.
How the team performs the Scrum Events will change.
How the team plans and collaborates will change.
Which tools and practices are used will change.
Anything can change.
Why? Because Scrum is designed for continuous improvement.
Each event exists to inspect and adapt—to reflect, learn, and make change happen.
So keep repeating these steps:
Plan → Do → Check → Act.
Sprint Planning → the necessary work and the Daily Scrum → Sprint Review → Sprint Retrospective.
And then? Repeat.
I’d love to hear your thoughts in the comments below!
I hope you find value in these short articles and if you are looking for more clarifications, feel free to take contact.
Don't want to miss any of these blog posts? Have the “The Scrum Guide Explored” series weekly in your mailbox.
Wishing you an inspiring read and a wonderful journey.
Scrum on!
