Chapter 62. Anatomy of an Impediment

Len Lagestee

The Scrum Guide states the Scrum Master has a responsibility to the team to remove impediments; but just what is an impediment? One dictionary defines an impediment as “a hindrance or obstruction in doing something.” From a Scrum perspective, the “doing something” is the ability to produce and deliver valuable outcomes within an ecosystem of flow and agility. There are different types of “hindrance or obstruction.”

Anything Constricting Flow or Constraining Pull in the System

The measure of success for a Scrum Team is how well and how frequently the needs of their customers are being met. A blanket term for impediments keeping us from serving customers with the least amount of resistance is friction. Friction comes in many shapes and sizes:

  • Unnecessary approval gates and defensive processes, such as testing sign-offs or governance committees, are examples of process impediments and characterize an untrusting environment.

  • Leadership decision escalations and status reports are examples of legacy impediments and characterize an organization not fully embracing an environment of agility.

  • Poor craftsmanship and the lack of decisiveness from the Product Owner are examples of capability impediments and characterize a team without accountability.

Friction impediments are frequently ignored, as they often touch upon sensitive areas, such as quality and leader behavior, so the comfort of the status quo will be a challenge to overcome. This changes with you.