Impediment

A tangible or intangible issue that blocks the team from progressing toward its goals; commonly called a blocker.

Key Points

  • It is a present obstacle that slows or stops the team's work toward agreed objectives.
  • Team members surface impediments quickly (often in the daily scrum), and a designated owner works to remove them.
  • Track impediments in a visible log or board and prioritize by impact on the sprint or release goals.
  • Different from risks (potential future events) and dependencies (relationships); an impediment is a current blocker.

Example

Mid-sprint, the team cannot run automated tests because the shared test environment is down. The Scrum Master coordinates with IT operations to restore the environment and escalates to management to prevent recurrence. Until resolved, the team reorders work that does not require that environment.

PMP Example Question

During the daily scrum, a developer reports they cannot access the test environment due to expired credentials, halting verification of a critical story. How should this be classified?

  1. An impediment (blocker) stopping progress
  2. A retrospective action item for future improvement
  3. A risk that may affect the release later
  4. A change request to add testing tasks to the backlog

Correct Answer: A — an impediment (a blocker that stops the team from progressing)

Explanation: The credential issue is a current obstacle preventing work from moving forward, so it is an impediment.

ICS/OT Incident Response Drills and Exercises

An incident response plan is only a theory until the people who must use it have run it under pressure. This course helps OT engineers, operations leaders, IT responders, and security teams turn a plan on paper into a tested capability.

Define safe states and manual fallback before an incident forces the decision. Build escalation paths, tabletop exercises, and scenarios that expose the gaps a document review cannot find.

Then turn the results into evidence: an after-action report, owned improvements, recovery checks, and a drill cadence that keeps the program alive after the exercise ends.

24 lessons, 2.4 hours. US$47 one-time through HKSM Courses. 30-day money-back guarantee when 50% or less consumed.

Explore the Course


ICS/OT Incident Response Drills and Exercises course preview

Build the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across eight teaching sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management, not on Udemy.

See What Is Included