Back to Basics with Scrum Events
Scrum is one of the best-known agile frameworks. Almost every team has heard of it and many will say they’re “doing Scrum.” But are they really?
Too often we see the events treated as optional extras, skipped when things get busy, rushed through or reduced to status reporting. The rhythm of Scrum gets lost, and with it, the opportunity to deliver real value every Sprint.
That’s why it helps to go back to basics.
We’ve created a simple cheat sheet for our clients that captures the essence of each Scrum event in plain language. It’s not a replacement for the Scrum Guide from Scrum.org - that remains the definitive source. Instead, this is a way to spark conversations in teams about whether they’re truly living the intent of Scrum, or just going through the motions.
The Sprint - a mini project
The Sprint is a fixed two-week timebox where the team collaborates to deliver value. We treat each Sprint like a mini project, with a clear start, middle and close. The goal is to deliver something of value every two weeks or sooner if possible.
Sprint Start - Sprint Planning
Purpose: create a realistic Sprint Plan the team can commit to.
Start fresh with an empty Sprint Backlog.
Confirm who’s in by checking each team member’s availability and capacity.
Agree the why by setting a Sprint Goal that supports the Product Goal.
Pull the what from the Product Backlog.
Plan the how by agreeing how the work will be delivered.
Commit carefully and stop when the team can’t take on more.
Sprint Middle - Daily Scrum
Purpose: inspect team performance and adapt the Sprint Plan every day.
Make the plan visible by focusing on the Sprint Backlog.
Repeat the why and remind everyone of the Sprint Goal.
Share progress by showing the Sprint Backlog item finished yesterday.
Signal intent by showing the Sprint Backlog item you’ll work on today.
Raise flags by asking for help and surfacing risks and issues.
Update the plan by reflecting changes directly in the Sprint Backlog.
Sprint Close - Sprint Review
Purpose: inspect the product outcomes and adapt the product roadmap.
Repeat the why by reminding everyone of the Sprint Goal and Product Goal.
Share progress by reporting planned and unplanned work status.
Show the work by presenting the Done items to stakeholders.
Gather feedback by observing reactions, discussing ideas, and noting issues.
Shape the next Sprint by discussing Product Backlog items.
Sprint Close - Sprint Retrospective
Purpose: inspect team performance and adapt the team’s way of working.
Celebrate wins by recognising performance and thanking people.
Look back by inspecting the last retrospective’s experiment - keep, dump, or change.
Set the focus by agreeing a theme for this retrospective’s discussion.
Reflect by surfacing problems, risks, tensions, and opportunities.
Commit by choosing one experiment to add to the next Sprint.
The Unofficial Event - Refinement
While not listed as a formal event in the Scrum Guide, we know Refinement is essential.
Purpose: run a future-focused discovery cycle - exploring value and shaping backlog items so they’re ready for a future Sprint.
Unpack the why by agreeing the customer or business value.
Describe the what by visualising behaviours, rules, and dependencies.
Estimate the effort by sizing items relative to a known anchor.
Prioritise the roadmap into Now, Next, Soon, and Later.
Break it down by slicing items small enough for one Sprint.
Get ready to Sprint by adding acceptance criteria and final details.
Why it matters
Scrum isn’t complicated but it is disciplined. Each event exists for a reason. Together they create the rhythm that helps teams deliver value predictably, while still adapting to change.
Sometimes, the simplest reset is the most powerful.
Try It With Your Team
If your Scrum feels like lip service or just meetings without substance, it might be time for a reset.
Start with the basics and revisit the purpose of each event. Ask your team, are we really doing this, or are we just going through the motions?
The Sprint Events Cheat Sheet includes expanded guidance for each event, with everyday language you can use as conversation starters with your team.
Updated on 25 September 2025
