Learn retrospective format vocabulary: Start-Stop-Continue, 4Ls, Mad-Sad-Glad, Timeline retrospective, safety check, and the prime directive for productive team retrospectives.
0 / 10 completed
1 / 10
A Scrum Master opens a retrospective by reading: 'Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.' What is this statement called?
The Retrospective Prime Directive (from Norm Kerth's 'Project Retrospectives', 2001) sets a blame-free psychological foundation for the retro. By acknowledging that everyone acted with good intent given the information they had, it discourages blame and encourages systemic thinking. Reading it aloud at the start helps teams shift from 'who failed' to 'what can we improve.'
2 / 10
Before starting a retrospective, a Scrum Master asks each team member to rate from 1–5 how safe they feel sharing honest feedback. A majority answer '2' (low safety). What should the facilitator do?
The safety check (from Esther Derby and Diana Larsen's 'Agile Retrospectives') measures psychological safety before the retro begins. A score of 1–2 indicates people do not feel safe being honest. The facilitator should acknowledge this openly (without blame) and adapt: use anonymous voting tools (like Mentimeter), use written sticky notes instead of verbal sharing, or facilitate a separate conversation about psychological safety barriers before diving into improvement topics.
3 / 10
A retrospective uses four categories for team feedback: what the team Liked, what they Learned, what they Lacked, and what they Longed for. What is this format called?
The 4Ls retrospective (Liked, Learned, Lacked, Longed for) was created by Mary Gorman and Ellen Gottesdiener. It is especially useful after project completion or major releases. 'Longed for' captures wishes and aspirations the team couldn't express in the other three categories. It tends to generate richer learning insights than Start-Stop-Continue because it separates what existed but was missing (Lacked) from what didn't exist at all (Longed for).
4 / 10
A team builds a shared visual timeline of the sprint on a whiteboard — marking deployments, incidents, key decisions, and team events in chronological order — then discusses patterns and emotional responses. What retrospective format is this?
The Timeline retrospective (also called a Sprint Timeline or Event Timeline retro) has team members plot significant events on a shared timeline and annotate them with emotions (often using emoji or colour codes). It helps surface cause-effect relationships across the sprint and reveals patterns invisible when looking at individual items. It is particularly effective after turbulent sprints with many incidents or context switches.
5 / 10
In the 'Mad-Sad-Glad' retrospective format, a team member places a sticky note under 'Mad' about a deployment process issue. What do the three columns represent?
Mad-Sad-Glad is an emotion-based retrospective format that surfaces how team members felt during the sprint, not just what happened. Mad = frustrations, blockers, things that angered the team. Sad = missed opportunities, losses, disappointments. Glad = wins, things that worked well, moments of pride. By starting with emotions rather than facts, this format often unlocks more honest and candid discussion than purely analytical formats.
6 / 10
Review Context: During a code review of the user_authentication module, Alice comments: 'This method is overly complex and could be simplified. It's not immediately obvious what it's doing.' What does Alice mean when she uses the term 'technical debt'?
Technical debt represents the implicit cost of rework caused by choosing an easy solution now instead of using a better approach that would take longer. Alice's comment indicates she believes the current code is a suboptimal choice, and this complexity will likely lead to future issues or require significant refactoring – essentially, it's accruing technical debt.
7 / 10
Slack Message: 'Hey team, I'm feeling pretty frustrated with the recent API response times. We're seeing consistently high latency, and it's impacting our user experience. Anyone have any ideas?' Sarah replies: 'Maybe we should investigate the database queries?' What is Sarah suggesting to address the issue?
Sarah's response suggests initiating a root cause analysis. This is a common approach in retrospectives when performance issues are identified; it involves systematically examining the underlying factors contributing to the problem – often starting with where data originates (the database queries).
8 / 10
PR Description: A developer submits a pull request to add a new feature to the e-commerce platform. The PR description reads: 'Fixed bug where users couldn't update their shipping address during checkout.' What retrospective format is this description most aligned with?
The PR description focuses on a specific, isolated issue (fixing a bug). This aligns with the core principles of a 'blameless postmortem' – which is focused on identifying and addressing systemic problems without assigning blame. It's a simple, factual account of an event.
9 / 10
Standup Update: During the daily standup, David says, 'Yesterday, I spent most of my time debugging a memory leak in the image processing service. It was a really frustrating process.' What is David's statement primarily reflecting?
David's statement highlights an obstacle he encountered – the memory leak. In a standup context, this is primarily reflecting a 'challenge' or 'impediment' that prevented him from completing his planned work. It's valuable information for the team to understand potential roadblocks.
10 / 10
Scenario: The team is using the 'Start, Stop, Continue' retrospective format. During the discussion, Maria suggests adding a sticky note under 'Stop' that says: 'Stop sending daily status reports to management'. What does this statement represent within the context of the retrospective?
The 'Start, Stop, Continue' format focuses on actions the team should take (or not take). Maria's suggestion to stop sending daily status reports directly addresses a communication inefficiency – it's a concrete recommendation for improving workflow.
What will I learn from the "Retrospective Formats Vocabulary" exercise?
Learn retrospective format vocabulary: Start-Stop-Continue, 4Ls, Mad-Sad-Glad, Timeline retrospective, safety check, and the prime directive for productive team retrospectives.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 10 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Scrum Master Facilitation exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss scrum master facilitation topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 10 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Scrum Master Facilitation exercises?
See the full Scrum Master Facilitation exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.