Scrum Master Facilitation Language Exercises

A Scrum Master facilitates all five Scrum ceremonies: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and Backlog Refinement. Facilitation language includes opening phrases like "Let's timebox this to 15 minutes," "Who would like to share their update?", and "Let's park that discussion in the parking lot." The Scrum Master does not manage — they create space for the team to self-organise, using neutral language that avoids directing outcomes.

Sprint Retrospective vocabulary includes "What went well?", "What could be improved?", "What should we start, stop, or continue doing?", "root cause analysis," "action items," and "team health." Common retrospective formats have their own vocabulary: in a "4Ls" retro, teams discuss what they Liked, Learned, Lacked, and Longed for. Effective Scrum Masters use diverge/converge language: "Let's take five minutes to write individual sticky notes before we discuss as a group."

Impediment removal language includes "I'll take that as an action item and follow up with [team/person] today," "What specifically is blocking you?", "Is this something the team can resolve, or does it need escalation?", and "I've raised this with the product owner and we should have a resolution by end of day." Scrum Masters distinguish between impediments (blocking progress now) and risks (potential future blockers), and use language accordingly: "This is a current impediment that needs immediate attention."

Velocity is the amount of work a team completes in a sprint, measured in story points. In planning discussions, a Scrum Master might say "Based on our average velocity of 34 points over the last three sprints, let's plan for a similar capacity this sprint." Velocity vocabulary also includes "velocity trend," "sustainable pace," and "capacity planning." Scrum Masters caution against using velocity as a performance metric across teams, as story point definitions vary.

A burndown chart shows the remaining work (story points or tasks) in a sprint or release plotted against time. Scrum Masters explain it with phrases like "The ideal burndown line shows us completing work at a steady pace. We're currently above the ideal line, which means we have more work remaining than planned." Related vocabulary includes "scope creep" (work added mid-sprint), "burnup chart" (showing completed work), and "zero-day risk" (incomplete stories at sprint end).

Sprint Planning vocabulary includes "sprint goal," "capacity," "commitment," "acceptance criteria," "definition of done (DoD)," and "pull from the backlog." The Scrum Master facilitates by asking "Does the team feel confident we can meet this sprint goal?" and "Have we accounted for planned leave and meetings in our capacity calculation?" The team discusses whether stories are "ready" (meets Definition of Ready: clear, estimated, independent) before pulling them into the sprint.

Effective Scrum Master coaching questions include "What's stopping you from resolving this yourself?", "What would success look like for this sprint?", "How might we approach this differently next time?", "What support do you need from me?", and "If you had to pick the single most important improvement, what would it be?" These open-ended questions use a coaching stance rather than providing solutions, encouraging the team to develop self-sufficiency and continuous improvement capability.

The Definition of Done (DoD) is a shared checklist that a story must meet before being considered complete. In team discussions, a Scrum Master enforces it by asking "Does this meet our Definition of Done?" or stating "We can't mark this story as done until the acceptance tests pass and the code has been reviewed." Creating and updating the DoD uses language like "Let's add unit test coverage above 80% to our DoD" or "We agreed as a team that code review is a DoD criterion."

Conflict resolution language includes "I'm hearing two different perspectives — let's make sure both are understood before we move forward," "Can we focus on the problem rather than the person?", and "What outcome would work for everyone here?" Scrum Masters use active listening phrases ("What I'm hearing you say is...") and reframing ("Let's treat this as a team challenge rather than an individual one"). When conflicts require escalation, Scrum Masters communicate to management without compromising team trust.

A "parking lot" is a facilitation technique for capturing off-topic or time-sensitive discussion items without disrupting the current agenda. The Scrum Master notes the item visibly and says "That's an important point — let me put it in the parking lot so we address it before the end of the meeting." Parking lot language signals respect for the topic while protecting timebox. At the end of the ceremony, the Scrum Master returns to parked items: "Before we close, let's quickly address the items in our parking lot."