Global Impediments Removal

Play Description

Pattern Summary 

Global Impediments Removal is a coordinated effort to surface, manage, and remove impediments that exceed a team’s span of control by bringing them to someone who has either the power or influence to address the impediment. The aim is to ensure that systemic impediments don’t persist and slow down the flow of work.

Related Definitions

• Impediment: An obstacle that slows or prevents progress for a person, team, or organization.
• Global Impediment: Any impediment that impacts multiple teams or requires resources from outside the team to remove the impediment.

Also Known As

• Cross-Team Impediment Resolution
• Enterprise Impediment Removal
• Organizational Blocker Clearing
• Systemic Impediment Removal

Related Patterns

Global Impediments Removal Board

Challenge Categories

Impediment Removal, Issue Resolution

Challenges Addressed

In many scaling efforts, teams can resolve their own impediments via retrospectives or the efforts of Scrum Masters (Team Coaches). But when impediments cross team or functional boundaries—requiring decisions, resources, or coordination from leadership—they often go unresolved. This slows delivery, creates frustration, and weakens trust.

Global Impediments Removal provides a structured approach for escalating, owning, and resolving such impediments quickly and at the right level.

Detailed Description

Global Impediments Removal is a coordinated effort to surface, manage, and remove impediments that exceed a team’s span of control by bringing them to someone who has either the power or influence to address the impediment. The aim is to ensure that systemic impediments don’t persist and slow down the flow of work.

Global Impediments Removal typically involve a visible, transparent system, that assigns ownership, tracks progress, and ensures timely removal—all the way to the level of senior decision-makers, when needed. In doing so, this ensures that impediments that transcend a single team’s scope are treated as high-priority work that is handled proactively, with clear accountability and visibility.

In Frameworks

Here’s how some agile scaling frameworks address global impediments.

Scaled Agile Framework (SAFe): SAFe addresses global impediments in multiple ways. In one method, a Team Coach/Scrum Master raises an impediment at the Coach Sync that occurs at least once per week. Another technique is to bring the global impediment to the Release Train Engineer (RTE), who aids in removal. A third involves bringing a global impediment to the Portfolio Sync so Lean Portfolio Management and executive leadership can address it.

Scrum@Scale: Scrum@Scale uses a Scaled Daily Scrum (see Cross-Team Sync pattern) to raise and address impediments. Each successive Scaled Daily Scrum provides an opportunity to bring the global impediment to a larger audience and, eventually to members of the Executive Action Team (EAT), who often have sufficient authority to remove the impediment.

Large-Scale Scrum (LeSS): LeSS considers impediments to be systemic dysfunctions, not isolated team problems. Particularly if multiple teams are blocked by the same issue, LeSS recommends that it be exposed by changing the system itself and NOT simply management by escalation. In LeSS, the Overall Retrospective (see Multi-Team Retrospective) provides an opportunity to address systemic impediments and leverage experiments to remove them.

How to Use:

There are multiple ways to implement Global Impediments Removal, depending on your organization’s structure, maturity, and tooling. Below are common approaches and considerations:

1. Global Impediments Board / Register / Backlog

• • Create a centralized impediment backlog (often with a Kanban board).
  • Each impediment becomes a “ticket” or backlog item, with details, impacts, dependencies, and proposed resolutions.
  • Categories or swimlanes may distinguish impediments by domain (e.g. infrastructure, compliance, process, external dependencies).

2. Triage / Prioritization

• • At a regular cadence (e.g. weekly), a cross-functional governance group or leadership forum reviews new impediments, prioritizes them, and assigns them for resolution.
  • Use clear criteria (e.g. impact on customer, cost of delay, number of teams blocked) to prioritize.

3. Escalation Path / Ownership

• • Define clear escalation paths: team → area/stream-level → program/portfolio level → executive level.
  • Assign an owner at each escalation level who is accountable for driving resolution.
  • If ownership does not result in progress within a committed window, escalate to the next level.

4. Transparency & Visibility

• • Make the global impediment backlog visible to all relevant stakeholders (via dashboards, shared boards, portals).
  • Publish status, aging, and resolution updates.
  • Ensure teams can see where impediments stand, who’s responsible, and what’s being done.

5. Timeboxing & SLAs

• • For high-impact impediments, some organizations define Service-Level Agreements (SLAs) or target resolution timeframes to ensure prompt resolution.
  • If an impediment breaches its SLA, trigger automatic escalation or review.

6. Feedback & Continuous Improvement

• • During retrospectives or operational reviews, analyze impediments: root causes, patterns, and prevention strategies.
  • Use metrics (e.g. average resolution time, number of escalations, recurring impediments) to drive systemic improvement.

7. Embed in Governance / Decision Forums

• • Integrate impediment review into existing leadership or governance forums (e.g. “Impediment Review Board,” “Risk & Issue Council”).
  • Ensure that leaders understand and commit to resolving impediments, rather than delegating without follow-through.

Do Not Use This Pattern When

The Multi-Team Planning pattern may not be suitable in the following scenarios:

1. When planning takes priority: Focus on value, not just timelines and budgets.
2. Small Team Sizes: If the organization or program has fewer than 50 people, the complexity and overhead of these planning techniques may outweigh the benefits. In such cases, simpler planning methods may be more effective.
3. Overemphasis on Processes: If using these techniques leads to excessive process overhead or rigidity, hindering the ability to adapt quickly, it can conflict with the core Agile principle of prioritizing individuals and interactions over processes and tools.
4. Misalignment with Organizational Goals: If the planning methods do not align with the organization’s objectives, culture, or capacity, they may cause friction or inefficiency. It’s crucial to ensure that these techniques match the organization’s maturity and goals.