Scrum defines five key events (sometimes called ceremonies) that structure the work and enable inspection, adaptation, and transparency. Here’s a summary of each event and what needs to be done:
Description: The Sprint is a fixed, time-boxed period (usually 1–4 weeks) during which a usable and potentially releasable product increment is created. It is the core container event that includes all other Scrum events.
Begin the sprint immediately after the previous one ends.
Maintain a consistent cadence (no gaps between sprints).
Focus on achieving the Sprint Goal by completing items from the Sprint Backlog.
No changes are made that would endanger the Sprint Goal.
Description: Held at the start of each sprint, this event sets the direction and scope for the upcoming sprint.
The Scrum Team (Product Owner, Scrum Master, Developers) meets to:
Define the Sprint Goal.
Select Product Backlog items to work on during the sprint.
Plan how the selected work will be accomplished.
Ensure everyone understands the work and the goal for the sprint.
Description: A short, daily meeting (usually 15 minutes) for the Developers to synchronize activities and create a plan for the next 24 hours.
What to Do:
Progress toward the Sprint Goal.
What was done since the last Daily Scrum.
What will be done before the next one.
Any impediments or obstacles.
Adjust the plan as needed to stay on track.
Description: Held at the end of the sprint to inspect the increment and adapt the Product Backlog if needed.
The Scrum Team and stakeholders:
Review what was accomplished during the sprint.
Demonstrate the completed work (increment).
Gather feedback and discuss what to do next.
Adapt the Product Backlog based on feedback and changes in priorities.
Description: The final event in the sprint, focused on continuous improvement.
The Scrum Team reflects on:
What went well during the sprint.
What could be improved.
How to improve processes and teamwork in the next sprint.
Agree on actionable improvements to implement in the next sprint.