How to implement Impediment List

What is an Impediment List?

An impediment list is a tool used in Scrum to track obstacles or issues that prevent a team from completing their tasks efficiently. These impediments can range from technical issues, such as bugs or software limitations, to organizational challenges, like unclear requirements or inadequate resources.

Types of Impediments with Examples

1. Technical Impediments: A critical server crash, Lack of automated testing frameworks.
2. Organizational Impediments: Inadequate management support, Bureaucratic processes slowing down decision-making.
3. Process-Related Impediments: Dependencies on other teams, Insufficient documentation.
4. Interpersonal Impediments: Conflicts within the team, Lack of communication or trust among team members.

Levels of Impediments

1. Team Level: Managed by the Scrum Master, these impediments are usually identified during daily stand-ups or sprint retrospectives. The Scrum Master documents them, often using tools like Jira, and works to resolve them quickly to maintain team productivity.

2. Cluster Level: Handled by a Tech Cluster Lead, these impediments affect multiple teams within a cluster. They are typically addressed in broader retrospectives involving representatives from each team.

3. Company Level: Overseen by the CTO, these impediments impact the entire organization. They are often strategic in nature and require high-level intervention to resolve.

How Impediments Arise

Impediments often come to light during retrospective meetings, where the team reflects on challenges faced during the sprint. For cluster or company-level impediments, an overall retrospective may be held to gather insights from multiple teams and address widespread issues.

Ownership of the Impediment List

1. Team Level: The Scrum Master owns the team impediment list, similar to how the Product Owner manages the product backlog. This ownership includes identifying, documenting, and facilitating the resolution of impediments.

2. Cluster Level: The Tech Cluster Lead is responsible for the cluster impediment list, ensuring that issues affecting multiple teams are addressed.

3. Company Level: The CTO owns the company impediment list, tackling strategic and organizational challenges.

Steps to Implement an Impediment List

1. Initialization: — Set up impediment lists in tools like Jira for each level: team, cluster, and company. — Create Kanban boards with statuses such as “To Do,” “In Progress,” and “Done” to track progress.

2. Escalation Mechanism: — Develop a process for escalating impediments from team level to cluster and company levels, similar to bubbles rising in a glass of Schweppes. — Handle sensitive impediments (e.g., those involving personnel changes) with extra care.

3. Regular Reviews: — Conduct regular reviews at cluster and company levels, ideally during overall retrospectives, to discuss and resolve impediments. — Allocate time at the beginning of these meetings to review the current impediments and their statuses.

Conclusion

The impediment list is a powerful tool for systematically addressing obstacles at various levels within an organization. By using a structured approach to identify, document, and resolve impediments, teams can enhance their efficiency and collaboration. Regular reviews and an effective escalation mechanism ensure that no impediment goes unnoticed or unaddressed, promoting continuous improvement across the organization.

Sources:

• Scrum.org on Navigating Impediments
• Lean Agile Training on The Impediment List
• Tech Agilist on Strategies for Scrum Masters
• Ostendo.io on Creating an Impediment List