27 Dependency and Impediment Management

Dependency and Impediment Management is the practice of identifying, tracking, and actively resolving the external constraints and active obstacles that threaten an agile team's ability to complete its planned work, distinguishing between dependencies that must be anticipated and coordinated in advance and impediments that arise unexpectedly and require immediate attention.

Distinguishing Dependencies From Impediments

Dependencies as anticipated constraints

A dependency is a known relationship in which one piece of work relies on another team, resource, or decision before it can proceed, and because dependencies can typically be identified during planning, they are best managed proactively by sequencing work and coordinating timing to avoid being caught unprepared when the dependent work becomes due.

Impediments as active obstacles

An impediment is an obstacle that is already actively blocking progress on work currently underway, whether or not it was anticipated in advance; unlike a dependency, which can often be planned around, an impediment demands immediate attention because it is preventing work from moving forward right now.

Managing Dependencies

Mapping dependencies during planning

During release and iteration planning, teams identify which backlog items rely on external teams, shared services, third-party vendors, or decisions from stakeholders outside the team, allowing this information to directly inform the sequencing of work so that dependent items are not scheduled before their prerequisites are expected to be ready.

Coordinating across team boundaries

Because dependencies frequently span multiple teams working on interrelated efforts, managing them well typically requires periodic cross-team synchronization, in which teams share upcoming needs and commitments to one another well before the point at which a missed dependency would actually block progress.

Reducing dependencies through structural choices

Where practical, teams and organizations can reduce the frequency and severity of dependencies through structural decisions such as organizing teams around complete, independently deliverable areas of functionality, minimizing the extent to which any one team's progress is inherently contingent on the timing of another's.

Managing Impediments

Rapid identification

Impediments are most commonly surfaced through daily coordination activities, where team members report obstacles currently affecting their work, allowing the team to become aware of a blocking issue as soon as possible after it arises rather than only discovering it once a deadline has already been missed.

Assigning clear ownership for resolution

Once identified, an impediment should be assigned to whoever is best positioned to resolve it, which may be someone within the team, a manager or coach supporting the team, or a specialist outside the team entirely, ensuring that responsibility for removing the obstacle does not remain ambiguous or unassigned.

Tracking persistent or recurring impediments

Impediments that cannot be resolved quickly, or that recur repeatedly across multiple iterations, warrant explicit tracking so they remain visible rather than being repeatedly reported and then forgotten; recurring impediments often point to a deeper systemic issue that requires a more substantial fix than a one-time resolution.

Escalation When Resolution Exceeds Team Authority

Recognizing the limits of team-level resolution

Some impediments involve decisions or resources outside the authority of the team itself, such as organizational policy, budget approval, or coordination with an external vendor; recognizing when an impediment has reached this threshold promptly, rather than allowing it to linger unresolved within the team, is an important part of effective impediment management.

Escalating with clear context

Escalating an impediment effectively generally requires providing whoever receives the escalation with sufficient context about the obstacle's impact and urgency, enabling a timely decision rather than requiring extensive follow-up simply to understand what is being asked.

Why Dependency and Impediment Management Matters

Protecting the reliability of commitments

By anticipating dependencies during planning and rapidly identifying and resolving impediments as they arise, teams protect their ability to meet commitments made during iteration and release planning, rather than allowing avoidable obstacles to silently erode delivery predictability.

Surfacing systemic issues for broader improvement

Consistent tracking of impediments, particularly recurring ones, often reveals underlying organizational or process issues extending beyond any single team, providing valuable input for broader improvements that address root causes rather than merely coping with their repeated symptoms.