T07: Remove Impediments | Domain 1

📖 Lý thuyết / Theory

🇺🇸 English

In Agile (Scrum), the Scrum Master is explicitly responsible for removing impediments. This is one of the three Scrum Master accountabilities (Serving the Development Team, Serving the Product Owner, Serving the Organization).

Impediment types:

Internal: Team member sick, technical debt, unclear requirements, skill gap
External: Infrastructure not ready, dependency on another team, waiting for vendor, security approval
Organizational: Bureaucracy, conflicting priorities, resource constraints, approval bottlenecks

PM/SM role: identify impediments early (daily standup), categorize by resolution path (self-resolve vs PM escalation), and track resolution.

🇻🇳 Tiếng Việt

Trong Agile (Scrum), Scrum Master chịu trách nhiệm rõ ràng về việc loại bỏ impediments. Đây là một trong ba trách nhiệm của Scrum Master.

Loại impediment:

Nội bộ: Thành viên bệnh, technical debt, yêu cầu không rõ ràng, skill gap
Bên ngoài: Hạ tầng chưa sẵn sàng, phụ thuộc team khác, chờ vendor, phê duyệt security
Tổ chức: Quan liêu, ưu tiên xung đột, hạn chế nguồn lực, bottleneck phê duyệt

🔧 Impediment Log Template

ID	Date	Description	Type	Impact	Owner	Action	Due	Status
IMP-001	05/01	AWS staging env down for 3 days	External	Team can't test integration	PM/DevOps	Escalate to CTO, use local docker instead	05/03	✅ Resolved
IMP-002	05/05	Bank Partner A API docs not provided	External	Sprint 4 stories blocked	PM	Escalate to Partner Manager, daily follow-up	05/08	🔄 In Progress
IMP-003	05/06	PR reviews taking 3+ days	Internal	Sprint velocity impacted	Tech Lead	Team agreement: 24h PR SLA	05/07	✅ Resolved

🎯

Exam Tips — Remove Impediments

Impediment removal = primary responsibility của Scrum Master trong Scrum
PM không nên để team "tự giải quyết" blockers bên ngoài — PM chủ động escalate và follow up
Daily standup question: "What impediments do you have?" — PM tracks và acts on these
Khi impediment không thể resolved bởi PM → escalate to sponsor/management với clear ask
Track impediments trong impediment log, không chỉ nhớ miệng

💼 Thực chiến / Scenario

🏢

FinTech Company X — Partner API Integration Blocker

Tình huống: Team Project Alpha bị block vì Bank Partner A chưa cung cấp sandbox API access. Sprint 4 có 8 story points phụ thuộc vào partner API. Đã chờ 5 ngày, partner không phản hồi email.

PM actions (Impediment Removal):

1. Identify: Log impediment ngay trong daily standup khi dev raise issue lần đầu.

2. Escalate appropriately: PM liên hệ trực tiếp với Partner Manager (không chờ dev tự làm), leo thang lên Account Manager level nếu PM không nhận được response trong 24h.

3. Parallel path: Trong khi chờ API, team develop với mock/stub server — không để team idle. Điều chỉnh sprint to pull in other ready stories.

4. Escalate to sponsor: Nếu vẫn không có API access sau 3 ngày, PM báo cáo sponsor với risk: "Sprint 4 velocity sẽ giảm X% nếu partner API không available by Day 7."

5. Document: Log tất cả communication attempts trong issue log.

✏️ Practice Questions

Question 1

During a daily standup, a developer mentions they are blocked waiting for access to a third-party API that requires approval from another department. What should the PM/Scrum Master do?

A. Tell the developer to send a follow-up email and wait
B. Remove the story from the sprint and move to the next sprint
C. Actively work to remove the impediment by contacting the other department and escalating if necessary, while enabling the developer to work on other items
D. Assign the task of getting the access to the developer as it's their responsibility

✅ Answer: C — The SM/PM's primary job is to remove impediments. They should proactively contact the blocking department, escalate if needed, and simultaneously redirect the developer to other work. Option A is passive. B removes value without trying. D puts an organizational impediment on a developer — that's the PM's job, not the developer's.

Question 2

The Scrum Master notices that the same impediment (slow CI/CD pipeline) has been listed in three consecutive sprint retrospectives without resolution. What should they do?

A. Remove it from the impediment list since it's a chronic issue
B. Escalate to organizational management with data on its impact (delay per sprint), build a business case for fixing it
C. Ask developers to work around it
D. Accept it as a permanent constraint

✅ Answer: B — A recurring impediment that persists across three sprints means the SM/PM lacks the authority to resolve it alone — it requires organizational-level action. The correct escalation approach is to quantify the impact (e.g., "adds 2 hours per sprint = 6 engineer-hours lost per sprint = $X/month"), build a business case, and bring it to management. Removing it from the list (A) makes the problem invisible. Workarounds (C) and acceptance (D) normalize the dysfunction.

Question 3

An impediment is blocking two developers but the PM cannot resolve it without executive approval. What is the BEST immediate action?

A. Wait for the approval before taking any other action
B. Reassign blocked developers to other work while escalating the impediment in parallel
C. Remove the blocked feature from scope
D. Ask developers to work on the blocker themselves

✅ Answer: B — The PM must pursue two tracks simultaneously: (1) protect sprint value by keeping the blocked developers productive on other work, and (2) escalate the impediment to those with authority to resolve it. Waiting (A) wastes capacity. Scope removal (C) is a last resort after exhausting escalation paths. Having developers work on organizational blockers (D) misuses developer time and puts them in an awkward position with other teams.

🔧 Impediment Log — Enhanced

Impediment Log

🤖 AI Tools for PMs

🤖

How AI Augments This Process

AI helps PMs analyze impediment root causes, draft escalation messages, generate unblocking strategies, and identify systemic patterns across multiple impediments.

Sample Claude Prompts

Impediment root cause analysis (5 Whys) Help me run a 5 Whys analysis on a project impediment. Impediment: [describe the blocker — specific, observable problem] Impact: [what it's blocking — sprint goal, milestone, team velocity] Duration: [how long this has been a blocker] Who's affected: [roles / teams impacted] What's been tried: [any attempted fixes] Run the 5 Whys analysis and: 1. Identify the root cause (not the symptom) 2. Classify the root cause type: Process / People / Technology / External / Organizational 3. Suggest the right intervention level: team-level fix / PM action / escalation needed 4. Draft an action plan with owner and timeline 5. Identify if this is a systemic issue likely to recur

Escalation message drafting I need to escalate an impediment to [sponsor / PMO / department head]. Impediment: [what is blocked] Business impact: [cost of delay — in time, money, or risk] Duration unresolved: [how long] What I've already tried: [steps taken at my level] What I need from them: [specific decision or action needed] Urgency: [timeline — decision needed by when] Draft an escalation email that: 1. Opens with the business impact (not the technical detail) 2. Gives just enough context (3 sentences max) 3. States clearly what decision/action I need 4. Provides a recommended option with brief rationale 5. Closes with a specific deadline for response Keep it under 150 words.

Impediment pattern analysis I have a list of impediments from the past [N] sprints. Help me find patterns. Impediment log: [Sprint 1]: [impediment description] — resolved in [X days] [Sprint 2]: [impediment description] — [status] [Sprint 3]: [impediment description] — [status] [add more...] Analyze this list and: 1. Identify recurring themes or root cause categories 2. Calculate average resolution time by category 3. Identify the top 2-3 systemic issues that should be addressed at org level (not sprint level) 4. Suggest a process improvement or structural change for each systemic issue 5. Draft a recommendation slide for my PMO/leadership

Jira / Confluence Template

Jira — Impediment Issue Type

── JIRA: IMPEDIMENT ISSUE TEMPLATE ────────────────────── Issue Type: Impediment (custom type or use Task with label) Summary: [BLOCKED] [Sprint/Team] — [short description] Priority: Critical / High / Medium Reporter: [PM name] Assignee: [Person who will resolve it] ── DESCRIPTION ─────────────────────────────────────────── What is blocked: [Sprint goal / user story / milestone] Blocked since: [YYYY-MM-DD] Business impact: [delay in days / cost estimate / risk] Root cause: [initial assessment] Already tried: [what has been attempted] Needs from: [who needs to act — escalation target] Resolution needed by: [date — to not miss milestone] ── LABELS ──────────────────────────────────────────────── impediment | sprint-[N] | category:[process/people/tech/external]

Address and Remove Impediments, Obstacles, and Blockers