The 5 Phases of Scrum (and Why They’re Not What You Think)
When you search for “the 5 phases of Scrum” on Google, you probably expect a clear list of steps like planning, execution, or review.
But if you’ve worked with agile teams, you know that Scrum isn’t organized into phases. Instead, it’s built around continuous learning cycles called Sprints.
So where does the confusion come from? Let’s clear that up.
The Myth of the 5 Phases of Scrum
In traditional project management, we often talk about phases such as:
- Initiation
- Planning
- Execution
- Control
- Closure
When people discover Scrum, they tend to look for those same steps.
However, Scrum breaks with the idea of moving through fixed stages. Instead of a linear process, it offers an iterative and incremental framework — each Sprint includes everything needed to deliver value, learn, and improve.
How It’s Often Interpreted: The Five Scrum Events
Scrum doesn’t define phases, but it does define five events that structure the work and continuous learning within each Sprint.
Beginners sometimes think of these events as “phases,” and while that’s not technically correct, it can help understand how Scrum flows.
1. Sprint Planning
The team decides what goal they want to achieve and what work is needed to get there.
The outcome is a realistic, value-focused plan.
2. Daily Scrum
A short daily meeting to synchronize, review progress, and adjust the plan.
It’s about transparency and collaboration.
3. Developing the Increment
The team works together to create something functional and valuable for the customer.
Each Sprint results in a potentially shippable Increment.
4. Sprint Review
The team presents the Increment to stakeholders, gathers feedback, and updates the Product Backlog.
The goal is to learn from the outcome and refine direction.
5. Sprint Retrospective
The team reflects on how they worked and defines specific actions for improvement.
It’s the foundation of continuous learning.
The Real Essence of Scrum: Inspect and Adapt
Beyond lists or stages, Scrum is founded on three pillars: transparency, inspection, and adaptation.
Each event serves a purpose — to make work visible, learn from it, and adjust quickly.
That’s what makes Scrum so effective in complex environments: it enables learning while delivering value.
Conclusion
So, does Scrum have five phases?
Not in the traditional sense. What it has are five key events that guide a continuous cycle of learning and delivery.
Scrum isn’t about following steps; it’s about thinking with an agile mindset, experimenting, and improving in every iteration.
If you’d like to explore how to apply this in your own team, check out our Scrum Master Course — a practical way to learn how to live Scrum, not just study it.