Because Scrum deliberately keeps the number of formal events minimal to ensure focus and flexibility. In the Scrum Guide, the official events are:
- Sprint
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
But what about Product Backlog Refinement?
It is an important activity, but it’s not a formal Scrum event. Here’s how the Scrum Guide (2020) describes it:
“Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details, such as a description, order, and size.”
Key Points:
| Aspect | Description |
| Is it required? | Yes — to keep backlog ready for future sprints |
| Is it time-boxed? | No — teams choose how much time to spend (usually 5–10% of Sprint time) |
| Who participates? | Product Owner, Developers, Scrum Master (facilitates if needed) |
| When is it done? | Anytime during the Sprint — usually scheduled mid-sprint or just-in-time |
| Why not an official event? | Scrum favors flexibility — teams decide how and when to refine. |
Think of it this way:
- Events = Time-boxed, structured ceremonies
- Refinement = Continuous team activity
So it’s essential, but not formal.
Analogy:
You clean your kitchen regularly — it’s important.
But it’s not on your daily family calendar like dinner or school runs.
Same with refinement — critical, but informal.
