Handling Impediments in Scrum
In Scrum, Developers may occasionally encounter impediments that block their progress. When these impediments are outside of the Developers’ control, it is important to know how to address the situation to ensure that the team continues to work effectively and that the issue is resolved as quickly as possible.
Exam Question
Developers are blocked by an impediment in the middle of the Sprint. The impediment is outside the Developer’s control. What should they do?
(choose the best answer)
A. Cancel the Sprint.
B. Immediately raise the issue to the Scrum Master.
C. Complete the work that can be done and complete the remainder during the “hardening sprint”.
D. Stop using Scrum.
E. Drop the Product Backlog items affected by the impediment from the Sprint Plan.
Correct Answer
B. Immediately raise the issue to the Scrum Master.
Explanation
Correct Answer
B. Immediately raise the issue to the Scrum Master:
The Scrum Master is responsible for helping the Scrum Team remove impediments that are blocking their progress. When the Developers encounter an impediment that is outside of their control, the best course of action is to immediately raise the issue to the Scrum Master. This allows the Scrum Master to take the necessary steps to resolve the impediment, ensuring that the team can continue working towards the Sprint Goal.
Why the Other Options Are Less Appropriate
A. Cancel the Sprint:
Cancelling a Sprint is a drastic measure that should only be considered if the Sprint Goal becomes obsolete. An impediment blocking progress does not necessarily mean that the Sprint needs to be cancelled, especially if it can be resolved.
C. Complete the work that can be done and complete the remainder during the “hardening sprint”:
Scrum does not endorse the use of “hardening sprints.” The focus should be on completing potentially shippable Increments within each Sprint. If work cannot be completed due to an impediment, the issue should be addressed immediately.
D. Stop using Scrum:
This is not a valid option. Scrum is designed to handle challenges, including impediments. Stopping the use of Scrum because of an impediment goes against the principles of adaptability and continuous improvement.
E. Drop the Product Backlog items affected by the impediment from the Sprint Plan:
Dropping Product Backlog items from the Sprint Plan should not be the first response to an impediment. Instead, the team should first try to resolve the impediment. Dropping items would be a last resort if the impediment cannot be removed and would only be done with the agreement of the Product Owner.
Relevance to the PSD Exam
Understanding how to handle impediments is crucial for the PSD exam, as it tests the ability to apply Scrum principles in real-world scenarios. Knowing the role of the Scrum Master in resolving impediments is a key aspect of effective Scrum practice.
Key Takeaways
- Raise Impediments Early: Developers should immediately inform the Scrum Master of any impediments they cannot resolve themselves.
- Scrum Master’s Role: The Scrum Master is responsible for helping the team remove impediments and ensuring the team can continue working towards the Sprint Goal.
Conclusion
When Developers are blocked by an impediment that is outside of their control, they should immediately raise the issue with the Scrum Master. This approach ensures that the impediment is addressed quickly, allowing the team to continue working effectively and meet the Sprint Goal. For more information on preparing for the PSD exam, visit our Professional Scrum Developer PSD™ Exam Prep.
