Task 7: Remove Impediments
Every project encounters obstacles. Vendors miss delivery dates, regulatory approvals stall, key team members get reassigned, technical dependencies reveal themselves mid-sprint, and organizational politics create invisible walls that slow everything down. The PMP Exam Content Outline defines Task 7: Remove Impediments as a critical competency within the Process domain — and it's one of the most practical, action-oriented skills a project manager can develop.
An impediment is anything that obstructs, delays, or prevents the project team from delivering value. In Agile environments, the Scrum Master or Agile PM is explicitly responsible for removing impediments, but in every methodology, the project manager serves as the team's primary obstacle-clearing force. This study guide covers the ECO enablers, the lifecycle of impediment management, and how this task is tested on the PMP exam.
ECO Enablers for Task 7
The PMP Exam Content Outline identifies three enablers for removing impediments, each describing a distinct phase of the impediment management lifecycle:
- Determine critical impediments, obstacles, and blockers for the project team. Before you can remove an impediment, you must identify it. This involves active listening during team meetings, reviewing sprint retrospectives, monitoring risk registers, and proactively soliciting input from team members who may be reluctant to surface problems.
- Prioritize critical impediments, obstacles, and blockers for the project team. Not all impediments are equal. A blocked critical-path activity demands immediate attention, while a minor inconvenience for a non-critical task can be addressed later. Prioritization uses impact analysis, urgency assessment, and team input.
- Use network to implement solutions to remove impediments, obstacles, and blockers for the project team. The project manager rarely has direct authority to remove every blocker. Instead, they leverage their network — sponsors, functional managers, vendors, steering committees, and other stakeholders — to clear the path. This enabler also requires continually re-assessing to ensure solutions hold.
These enablers align with PMBOK 7's Team performance domain (serving the team by clearing obstacles), the Planning domain (anticipating impediments through risk management), and the Leadership principle (advocating for the team). In Agile contexts, this also maps to the Scrum Master's core accountability of removing impediments to the Development Team's progress.
Types of Impediments and Their Sources
Impediments come in many forms. Recognizing the type of impediment you're dealing with determines the appropriate removal strategy. Here are the most common categories tested on the PMP exam:
| Impediment Type | Examples | Removal Strategy | Typical Owner |
|---|---|---|---|
| Resource Impediments | Team member reassigned; equipment unavailable; budget frozen mid-project | Negotiate with functional managers; escalate to sponsor; adjust schedule or scope | Project Manager / Sponsor |
| Technical Impediments | Legacy system incompatibility; missing API documentation; unresolved architectural decision | Bring in SME; spike/prototype to resolve unknowns; escalate technical debt to product owner | Technical Lead / Architect |
| Process / Bureaucratic Impediments | Approval chain takes 3 weeks; compliance review blocks deployment; change control board backlogged | Streamline or fast-track approvals; request temporary process waiver; use network to expedite | PMO / Governance Body |
| External / Vendor Impediments | Third-party deliverable is late; vendor contract dispute; regulatory inspection delayed | Invoke contract clauses; engage procurement; develop contingency workaround | Procurement / Legal |
| Interpersonal / Team Impediments | Unresolved conflict between developers; team morale collapse; key person burnout | Facilitate conflict resolution (see Task 1); adjust workload; bring in temporary support | Project Manager / Scrum Master |
The Impediment Management Lifecycle
Removing impediments isn't a one-time activity — it's a continuous cycle that runs throughout the project. PMI expects project managers to establish a systematic approach:
1. Detection and Logging
Impediments must be surfaced before they can be removed. Detection mechanisms include: daily standups (Agile), status meetings (predictive), retrospectives, risk review sessions, one-on-one conversations, and anonymous team surveys. Once detected, impediments should be logged in a visible, accessible format — an impediment log, an information radiator on a team board, or a dedicated section of the risk register. The log should capture the impediment description, date identified, who raised it, impact level, and current status.
2. Impact Analysis and Prioritization
Once an impediment is identified, the project manager must assess its impact. Key questions include: Is it blocking the critical path? How many team members are affected? Is the impact growing over time? What is the cost of delay? Prioritize using a simple matrix: High Impact / Urgent: act immediately and escalate if necessary. High Impact / Not Urgent: assign an owner and track resolution timeline. Low Impact / Urgent: address quickly but don't disrupt sprint/project flow. Low Impact / Not Urgent: monitor; address during planned improvement cycles.
3. Resolution Using Your Network
This is where the project manager's stakeholder relationships pay dividends. The PMP exam emphasizes that the project manager should not try to solve every impediment alone. Instead, they should leverage their network — the people with authority, expertise, or resources to clear the blocker. This might mean asking the sponsor to intervene with another department head, requesting the procurement team to expedite a vendor contract, or collaborating with the PMO to temporarily relax a reporting requirement. The key exam concept: the PM facilitates removal; they don't necessarily perform it themselves.
A common wrong-answer trap on the PMP exam presents an impediment scenario and offers "the project manager should personally resolve the issue" as an option. While the PM owns responsibility for ensuring impediments are removed, PMI expects the PM to leverage organizational assets, escalate appropriately, and use their stakeholder network — not to single-handedly fix every problem. Look for answer choices that involve: identifying who has the authority to resolve the blocker, facilitating a conversation with the right person, or escalating through appropriate channels after documenting the impact.
4. Continuous Re-Assessment
The fourth element embedded in the ECO enablers is "continually re-assess." Impediments can resurface in new forms, solutions can create secondary problems, and what appeared resolved may have been only partially addressed. The PM should regularly revisit the impediment log during retrospectives, risk reviews, and status meetings. Ask: Did the solution actually work? Has the impediment re-emerged? Are there new impediments caused by the fix? This feedback loop is essential for continuous improvement.
Impediment Removal in Different Methodologies
| Aspect | Predictive (Waterfall) | Agile / Scrum | Hybrid |
|---|---|---|---|
| Primary Owner | Project Manager, with escalation to sponsor | Scrum Master is explicitly accountable; team members also surface impediments at Daily Scrum | PM (or hybrid lead) owns impediment log; team uses Agile ceremonies to surface issues |
| Detection Cadence | Weekly status meetings, risk reviews, phase-gate reviews | Daily at standup; Sprint Retrospective; Sprint Review; real-time via kanban blockers | Daily standups for team-level; weekly status for cross-team; phase-gate for governance-level |
| Visibility | Issue log, risk register, status reports | Impediment board (physical or digital), sprint backlog flags, burndown chart anomalies | Combined: digital impediment log plus visual board for co-located teams |
| Escalation Path | PM → Functional Manager → Sponsor → Steering Committee | Scrum Master → Product Owner (if scope-related) → Stakeholders → Organizational leadership | Depends on governance model; typically PM escalates with input from Agile ceremonies |
How Impediment Questions Appear on the PMP Exam
Pattern 1: "A critical path activity is blocked because..."
When the critical path is threatened, immediate action is required. The PM should first assess the nature of the impediment, then determine who in their network can resolve it most quickly. Look for answers that involve: identifying the root cause, evaluating impact on the schedule baseline, and engaging the appropriate stakeholder. Avoid answers that suggest ignoring the blocker or simply accepting schedule slippage.
Pattern 2: "During the daily standup, a team member reports..."
In Agile scenarios, the Scrum Master's response to an impediment raised at standup should be to log it, assess it, and begin working the resolution — ideally outside the standup so the meeting isn't derailed. The PMP exam may test whether you know that the Scrum Master doesn't need team consensus to start removing an impediment; they have the authority and accountability to act.
Pattern 3: "A vendor has delayed delivery three times..."
Recurring external impediments require a different approach. After the first delay, the PM may work with the vendor directly. After repeated delays, the appropriate response involves: reviewing contract terms, engaging procurement, considering alternative vendors, and updating the risk register. Look for answers that reference formal procurement processes rather than repeated informal negotiation.
The PMP exam almost never rewards passivity. Answer choices that suggest waiting, monitoring without action, or hoping the impediment resolves itself are virtually always wrong — especially when the impediment affects the critical path or blocks multiple team members. PMI expects proactive, decisive impediment management. The correct answer will involve taking action now: logging, analyzing, escalating, or resolving.
Key Principles from PMBOK 7
PMBOK 7's Team performance domain explicitly calls out the project manager's responsibility to "eliminate impediments." The Servant Leadership style — central to both PMBOK 7 and the Agile Practice Guide — positions the project leader as someone who clears the path so the team can do its best work. Additionally, the principle of Stewardship requires PMs to be diligent, respectful, and trustworthy custodians of the project, which includes proactively removing obstacles rather than letting them accumulate.
The Tailoring principle is also relevant: impediment management must be tailored to the organizational culture. In a hierarchical organization, escalation through formal channels may be necessary. In a flat, Agile organization, the PM may be empowered to remove most impediments directly. The PMP exam expects you to recognize the appropriate approach for the context described in the scenario.
The Relationship Between Impediments and Risk
Impediments and risks are closely related. An unresolved impediment that persists becomes a risk (or materializes an existing risk). Conversely, effective risk management can prevent many impediments from arising in the first place. For example, if your risk register identifies "key team member may be reassigned" as a risk with a mitigation plan, you're better prepared when it actually happens. The PMP exam may test whether you know to update the risk register when an impediment reveals a new risk or triggers an existing one.
Study Checklist for Task 7
- ✅ Can you define what qualifies as an impediment and distinguish it from a risk, an issue, or a simple task?
- ✅ Do you understand the five types of impediments (resource, technical, process, external, interpersonal) and the appropriate removal strategy for each?
- ✅ Can you describe the impediment management lifecycle: detect → log → prioritize → resolve via network → re-assess?
- ✅ Do you know that the project manager facilitates removal rather than personally solving every impediment?
- ✅ Can you distinguish how impediment management differs between predictive, Agile, and hybrid environments?
- ✅ Are you able to recognize the correct PMP answer pattern: proactive action, leveraging the network, and formal logging vs. passive "wait and see"?
- ✅ Do you understand when to escalate an impediment and through which channels?
Task 7 is fundamentally about being the person who clears the path. It's one of the most visible ways a project manager demonstrates value to the team — and it's a skill that translates directly to real-world project leadership. Continue to Task 8: Negotiate Agreements to learn how negotiation skills complement your ability to remove obstacles.
← Back to ECO Study Guide Index | Practice Process Domain Questions →