Scrum events are the key moments when teams collaborate, inspect, and adapt. But let's be honest: without proper facilitation, these meetings can quickly turn into dull obligations. How do you ensure that as a Scrum Master or facilitator, you bring energy, interaction, and focus to these events? On this page, we'll discuss powerful facilitation techniques for each Scrum event, so your team truly gets value from them.
A well-facilitated Scrum event ensures that:
- Everyone is engaged and contributes.
- The meeting's objectives are clear.
- Time is used effectively.
- Decisions are made and action items are clear.
Poor facilitation leads to:
- Long, inefficient meetings.
- Low engagement and multitasking team members.
- Unclear next steps.
As a Scrum Master or facilitator, you are the key to successful events. Time to sharpen your skills!
1. Sprint Planning – Kicking off the Sprint
Goal: To decide what work will be done in the Sprint and how the team will approach it.
Techniques:
🔹 Timeboxing – Keep discussions concise and focused per backlog item.
🔹 MoSCoW Prioritization – Helps the Product Owner and the team determine what truly needs to be done.
🔹 Silent Writing – Have team members write down their ideas first before discussing them to avoid 'loudest voice' bias.
🔹 Dot Voting – Quickly reach consensus on the most important backlog items.
🛠️ Tip: Start with a clear Sprint Goal and ask the team how they can achieve it.
2. Daily Scrum – Short, sharp, and effective
Goal: Align the team and identify any potential obstacles.
Techniques:
🔹 Walk the Board – Go through each item on the Scrum board to check its status, instead of having each person give an update.
🔹 Fist of Five – Have team members use their fingers (1-5) to indicate how confident they are that the Sprint Goal will be achieved. Low scores? Discuss why.
🔹 Three W’s – Keep the questions focused: What did I do yesterday? What will I do today? What's blocking me?
🛠️ Tip: Keep it short! If it takes longer than 15 minutes, the problem is likely with a team that's too large or working inefficiently.
3. Sprint Review – Not just a demo, but a dialogue
Goal: Show stakeholders what has been delivered and gather feedback.
Some commonly used techniques as examples:
🔹 Customer Walkthrough – Have a real user live-test the new features.
🔹 Feedback Radar – Stakeholders write feedback on post-its (positive, neutral, negative) and stick them on a flip chart.
🔹 Start, Stop, Continue – What should we start, stop, and continue doing based on the Sprint?
🔹 Dotmocracy – Have stakeholders vote on which developments they consider most important.
🛠️ Tip: Keep it interactive and avoid a one-way narrative. Stakeholders should participate, not just listen.
4. Sprint Retrospective – Continuous improvement in action
Goal: Learn from the past Sprint and implement improvements.
Examples:
🔹 Mad, Sad, Glad – Team members share what made them angry, sad, or happy during the Sprint.
🔹 The 5 Whys – Ask ‘why?’ five times to get to the root cause of a problem.
🔹 Speedboat – Visualize the team as a boat: what holds us back (anchors) and what pushes us forward (wind)?
🔹 Lean Coffee – Let team members decide what they want to talk about and structure the discussion based on priorities.
🛠️ Tip: Vary the approach regularly to keep Retros from becoming boring and repetitive.
.svg){kind=icon}
.svg)
