Learn vocabulary for identifying, escalating, and communicating impediments.
0 / 10 completed
1 / 10
What is an 'impediment' in Scrum vocabulary?
An impediment is anything outside the team's power to resolve that blocks their progress — e.g., waiting for a vendor decision, access to a system, or a dependency on another team. The Scrum Master's job is to remove or escalate these.
2 / 10
What does 'escalate' mean in impediment removal vocabulary?
Escalation means taking an unresolved impediment to someone with the authority to act — e.g., a product manager, department head, or senior engineer. The Scrum Master frames it clearly: 'This is blocking the team from delivering X by Y.'
3 / 10
What is 'impediment backlog' in Scrum Master vocabulary?
An impediment backlog (or blocker list) is the Scrum Master's working list of all active obstacles — including who is responsible for resolution, the current status, and the escalation path if not resolved by a specific date.
4 / 10
What language should a Scrum Master use when communicating an impediment to leadership?
Effective impediment escalation language is specific: names the team, the blocker, when it started, the business impact, and the exact action requested — making it easy for leadership to act quickly and understand urgency.
5 / 10
What is 'technical impediment' vs 'organisational impediment' in Scrum vocabulary?
Technical impediments include: broken CI, missing dev environment, untested APIs. Organisational impediments include: waiting for approval, unclear ownership, cross-team dependencies, policy restrictions. Both are the Scrum Master's responsibility to address.
6 / 10
Review Comment: 'This function is returning null when it should be an object. I've added a check but the logic still feels unclear. Can you explain why this is happening?' What does the developer likely *mean* by 'the logic still feels unclear'?
This question tests understanding beyond just technical correctness. The developer isn't simply pointing out a bug; they're expressing confusion about *why* that bug exists – specifically the underlying logic and potential design flaws contributing to the unexpected null return. The correct answer reflects this higher-level concern, acknowledging the problem's root cause.
7 / 10
Slack Message: '@johndoe, I'm blocked on getting access to the staging database. The DevOps team says it's queued, but I haven't received any updates in two hours.' What is John Doe *most* likely trying to achieve with this message?
This assesses the ability to recognize the intended purpose of a message. John Doe isn't asking for immediate help; they're seeking information regarding the progress of a dependency. The correct response highlights the proactive nature of the inquiry – it's about obtaining an update and understanding the delay.
8 / 10
PR Description: 'Implemented new user authentication flow. Updated login() function to use JWT tokens for improved security. Address issue #1234.' What is the primary *benefit* being communicated in this PR description?
This question probes understanding of how PR descriptions should convey value. While issue #1234 is mentioned, the core message is about enhanced security through JWT tokens. The description focuses on *why* the changes were made – to improve security – which is a critical benefit for stakeholders.
9 / 10
Standup Update: 'Yesterday I was stuck debugging a memory leak in the reporting service. It took me three hours to identify and fix it.' What does Sarah *intend* for the team to understand from this statement?
This question examines communication about impediments. Sarah isn't just reporting what happened; she's highlighting the *impact* – the time invested in resolving the issue. Understanding this context is crucial for the team to appreciate the potential disruption and prioritize future work.
10 / 10
API Response (Error): `HTTP 500 Internal Server Error. Reason: 'Insufficient permissions to access resource X.'` What does this API error response *primarily* indicate?
This focuses on interpreting an API error response. The 'Insufficient permissions' message clearly points to a problem with the user's access rights. The correct answer acknowledges this authorization issue as the root cause of the server error.
What will I learn from the "Impediment Removal — Communication and Vocabulary" exercise?
Learn vocabulary for identifying, escalating, and communicating impediments.
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.