Understanding Impediments in Scrum
In Scrum, an impediment is anything that hinders the progress of the Scrum Team in achieving the Sprint Goal. Identifying and addressing impediments is crucial for maintaining a smooth and efficient workflow.
Exam Question
In the context of Scrum, what is your understanding of an impediment?
Provide one example of an impediment and one example of something that may mistakenly be characterized as an impediment.
Explanation
What is an Impediment?
- Definition:
An impediment is any obstacle or issue that prevents the Scrum Team from making progress on their work. It could be a blocker that stops work altogether or something that slows down the team’s progress. - Impact on the Team:
Impediments can affect the team’s ability to meet the Sprint Goal. Therefore, it is the responsibility of the Scrum Master to identify and remove impediments as quickly as possible to ensure the team can continue to work efficiently.
Example of an Impediment
- Technical Blocker:
Example: The team is working on a new feature that requires access to a specific API, but the API is down due to an external service issue. This prevents the Developers from continuing their work on that feature.
Why It’s an Impediment: The team cannot proceed with their work until the API issue is resolved. This is a clear impediment that the Scrum Master needs to address by coordinating with the service provider or finding an alternative solution.
Example of Something Mistakenly Characterized as an Impediment
- Miscommunication:
Example: A Developer feels they are unclear about the requirements of a Product Backlog item and claims it as an impediment.
Why It’s Not an Impediment: This situation is more about a need for clarification rather than an actual impediment. The Developer should seek clarification from the Product Owner or the team instead of treating it as a blocker. The Scrum Master can facilitate this communication, but it’s not a true impediment.
Relevance to the PSM III Exam
Understanding what constitutes a real impediment and how to address it is crucial for a Scrum Master at the PSM III level. Demonstrating the ability to differentiate between actual impediments and issues that can be resolved through communication or collaboration is essential for showcasing advanced Scrum mastery.
Key Takeaways
- Impediments: True obstacles that prevent the team from making progress and require intervention to remove.
- Mischaracterized Issues: Situations that may be mistaken for impediments but can be resolved through clarification, communication, or collaboration.
Conclusion
In Scrum, recognizing and addressing impediments is vital for maintaining the team’s momentum and ensuring they can achieve the Sprint Goal. As a Scrum Master, it’s important to differentiate between real impediments and issues that can be resolved without treating them as blockers.

Get ready for the official PSM III exam
80+ PSM III essay practice questions, each with a model answer and an in-depth explanation.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 24 random questions in 150 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSM III exam fee ($500) is paid separately to Scrum.org.
More PSM III exam questions
- In Sprint Planning the Developers work to forecast the Product Backlog items that will be developed during the Sprint and the Developers make a commitment to the Sprint Goal.
- Empiricism requires transparency for effective inspection to occur.
- The Daily Scrum is an event that happens every day.
- Empiricism requires transparency for an effective inspection to occur.
- Two Scrum Teams work on the same product. They pull from one Product Backlog and develop in the same codebase. The Product Owner and the Scrum Master perform their roles for both teams. At the combined Sprint Review each team shows the work they’ve done from their separate code branch.
