Blocker

A blocker is a specific impediment that halts or severely delays work, preventing a team or individual from moving forward until it is removed. It should be surfaced quickly, made visible, and escalated for resolution. See Impediment.

Key Points

  • Stops progress immediately until resolved; not just a minor slowdown.
  • Raised promptly (e.g., in the Daily Scrum) and tracked on an impediment log or board.
  • Common sources include access issues, broken environments, missing decisions, or external dependencies.
  • The Scrum Master or Agile leader facilitates removal, while the team may swarm to restore flow.

Example

A developer cannot deploy because production credentials have not been granted. Work on the release is paused until access is approved. The team records this as a blocker and the Scrum Master escalates it to the security team.

PMP Example Question

During the Daily Scrum, the team reports that the test environment is down, preventing all testing from proceeding. How should this be classified?

  1. A risk to be analyzed later
  2. A blocker requiring immediate removal
  3. An assumption to document
  4. A retrospective action item

Correct Answer: B — A blocker (an impediment that stops progress)

Explanation: The test environment outage prevents work from continuing now, which is the definition of a blocker; it needs swift escalation and resolution.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Lead with clarity, influence, and outcomes.

HK School of Management offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More