Scrum comprises five key events, each serving a unique purpose and involving specific participants:
- The Sprint
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
Purpose of Scrum Events
- Sprint: All work in Scrum is done within a timebox called a Sprint, which enables feedback loops.
- Sprint Planning: This planning session occurs before the Sprint starts. Developers outline the work they intend to complete during the Sprint.
- Daily Scrum: Held daily, this event allows Developers to inspect their progress toward the Sprint Goal.
- Sprint Review: At the end of the Sprint, the Scrum Team meets with stakeholders to demonstrate what they have accomplished and to receive feedback.
- Sprint Retrospective: Toward the end of the Sprint, the Scrum Team gathers to discuss the Sprint’s progress and identify improvements for the next Sprint.
Who Participates in the Scrum Events?
- Sprint: Scrum Team
- Sprint Planning: Scrum Team, led by the Product Owner
- Daily Scrum: Development Team (Product Owner and Scrum Master may optionally attend)
- Sprint Review: Scrum Team, Stakeholders, Business Team
- Sprint Retrospective: Scrum Team, led by the Scrum Master
How Much Time Should We Spend on Scrum Events?
- Sprint: Maximum of 4 weeks, typically 2 weeks
- Sprint Planning: 2 hours for a 2-week sprint. Tip: Consider two 1-hour Sprint Planning sessions during the sprint (e.g., if the sprint starts on Wednesday, hold sessions on the following Monday and Thursday).
- Daily Scrum: 15 minutes Tip: Keep the Daily Scrum to 15 minutes, but allow an additional 15 minutes for detailed discussions, especially for teams in different time zones.
- Sprint Review: 1 hour for a 2-week sprint
- Sprint Retrospective: 1 hour for a 2-week sprint
(These time recommendations are based on practical experience.)
Tip – Which is the Most Important Event in Scrum?
In interviews, the simple answer is “all of them.” However, if you must choose one besides Sprint, it often depends on your organization’s context. I would say the Daily Scrum is crucial, as it’s a daily meeting where developers discuss impediments, open questions, and clarifications. This collaboration is essential in our fast-changing world, helping the team stay updated and on track to achieve the Sprint Goal.
Tip: Why Does Scrum Have Events Instead of Ceremonies?
Scrum uses the term “events” instead of “ceremonies.” Although you might hear the term ceremonies in discussions, it is incorrect in the context of Scrum. The distinction is important: ceremonies follow a fixed process without alterations, whereas events in Scrum are designed to be adaptable. Processes within these events can be modified based on prior learnings and team-specific contexts. Each organization’s way of working can vary from team to team, allowing them to adjust processes to better fit their unique needs and experiences.