5 exercises on agile ceremony language — standups, retrospectives, planning and sprint reviews. Choose the most natural and professional option.
0 / 5 completed
1 / 5
The team discussion is going off-track and you want to limit the time spent on a topic. Which phrase is best?
Let's timebox this to 5 minutes: "Timebox" is a core agile term for setting a fixed maximum time limit on an activity, after which the team moves on regardless of whether it is finished. It is neutral, structured, and respectful — it signals that the topic deserves time, but not unlimited time. Option A is abrupt and dismissive. Option C is informal and suggests the discussion was a mistake. Option D devalues the topic without a decision being made. Timeboxing is used in standups, planning sessions, and retrospectives to keep meetings productive, so this phrase is essential vocabulary for any agile facilitator.
2 / 5
During a planning session, someone raises an important issue that is outside the current agenda. How do you handle it professionally?
I'll add that to the parking lot: The "parking lot" is a standard agile facilitation technique for capturing off-agenda items so they are not lost but also don't derail the current session. It signals to the contributor that their input is valued and will be addressed — just not right now. Option A sounds dismissive and shuts the speaker down. Option B is vague and "the end of the meeting" often gets skipped. Option C puts the burden on the speaker and doesn't use agile vocabulary. Using "parking lot" demonstrates structured facilitation and helps teams stay on track without making anyone feel ignored.
3 / 5
At the start of a daily standup, the facilitator wants to open the floor for blockers. Which phrasing is most professional?
Is there anything blocking anyone? In agile, a "blocker" (or "impediment") is a specific term for anything preventing a team member from making progress on their work. Using "blocking" connects directly to the vocabulary of standups and sprint boards, where blockers are tracked explicitly. Option B uses "problems," which is imprecise and broader than blockers. Option C is a vague yes/no question that doesn't use agile terminology. Option D is wordy, informal, and awkward. This phrase is brief, inclusive, and uses exactly the right word to prompt team members to surface impediments that the Scrum Master or team can help resolve.
4 / 5
Before accepting a user story as done, a developer wants to understand the agreed exit criteria. Which phrase is best?
What's the definition of done for this? The "Definition of Done" (DoD) is a formal agile concept — a shared checklist of criteria that must be met before any work item can be considered complete. It typically includes tests passing, code reviewed, documentation updated, and acceptance criteria verified. Option A is informal and lacks the specific DoD terminology. Option B shifts focus to "the client," which is not always relevant and conflates DoD with acceptance criteria. Option D is vague and casual. Asking specifically about the "definition of done" aligns the team around the shared standard and prevents premature closure of stories. It is essential vocabulary in sprint planning and reviews.
5 / 5
In a sprint review, the facilitator wants to go through each item on the board from left to right. Which phrase is standard agile language?
Can we walk the board? "Walking the board" is a standard agile ceremony phrase for reviewing the sprint board — typically from right to left (Done → In Progress → To Do) or left to right — item by item, discussing status, blockers, and completion. It is visual, structured, and widely understood in Scrum and Kanban teams. Option A is functional but informal and doesn't reference the board as a visual management tool. Option C puts the burden on a single speaker and loses the collaborative, item-by-item structure. Option D says "this week," which may not match the sprint cadence and is less precise. "Walk the board" is part of the shared agile vocabulary that keeps ceremonies efficient.