Impediment Log: Description, Severity, and Resolution Actions

PMBOK v8 Definition

An impediment is defined as "an obstacle that prevents the team from achieving its objectives. Also known as a blocker." The Impediment Actions Techniques produce a list that shows a description of the impediment to getting work done, the severity, and the actions being taken to resolve the impediment. This technique is used in adaptive (agile) environments to track and manage obstacles that hinder team progress, ensuring visibility and accountability for resolution.

Why It Matters for the Exam

The PMI exam frequently tests your understanding of how impediments are tracked and managed in adaptive project environments. Questions often appear in the Executing Process Group and focus on distinguishing impediments from risks, issues, and change requests. The exam expects you to know that an impediment log is a living artifact that must be reviewed regularly (typically in daily standups or retrospectives) and that the team is responsible for escalating impediments beyond their authority.

Key Points to Remember (for the exam)

• Definition: An impediment is an obstacle that prevents the team from achieving its objectives (also called a blocker).
• Three Required Fields: The impediment log must always contain: (1) description of the impediment, (2) severity level, and (3) actions being taken to resolve it.
• Primary Tool: The impediment log is the main tool for tracking blockers in adaptive environments.
• Team Responsibility: The team first attempts to resolve impediments themselves; if beyond their authority, they escalate to the appropriate person.
• Common Confusion: Impediments are current obstacles affecting ongoing work, whereas risks are future uncertainties that may or may not occur.
• Review Frequency: Impediments are reviewed daily (e.g., in daily standup meetings) to track progress on resolution actions.
• Severity Levels: Severity helps prioritize which impediments require immediate attention versus those that can wait.

Typical PMI Exam Example

A software development team is working on a critical feature release. During the daily standup, a developer reports that the testing environment is unavailable due to server maintenance. The team updates the impediment log with: "Testing environment unavailable" (description), "High" (severity), and "Contacting IT operations to request alternative environment access" (resolution action). The project manager reviews this log during the daily standup to ensure the blocker is being addressed.

PMI Exam Traps

• Trap: Confusing an impediment with a risk

  • Reality: An impediment is a current obstacle blocking work now; a risk is a future uncertainty that may or may not happen.

• Trap: Thinking the project manager is solely responsible for resolving all impediments

  • Reality: The team is responsible for resolving impediments first; they escalate only when the obstacle is beyond their authority.

• Trap: Confusing the impediment log with the issue log

  • Reality: Both track obstacles, but impediments are specific to adaptive/agile environments and focus on blocking team progress, while issues can apply to any project type.

• Trap: Assuming impediments are documented only once and never updated

  • Reality: The impediment log is a living document updated regularly (daily in standups) with new actions and status changes.

Important PMI Connections

Quick Review Questions

1. What are the three mandatory fields that must appear in an impediment log?

2. During which meeting is the impediment log typically reviewed and updated?

3. What is the difference between an impediment and a risk?

4. Who is responsible for resolving an impediment first: the project manager or the team?

5. What should the team do when an impediment is beyond their authority to resolve?

PMBOK v8 Reference

Section 4.4.2.5 - Impediment Log (within the Adaptive Environments section)