HKSM

A living list that records all current impediments affecting the Scrum Team, their status, owners, and actions. It is refreshed whenever new blockers are found or resolved and is used to drive removal, escalation, and transparency across Sprints.

Key Points

• Tracks blockers that slow or prevent progress and the actions taken to remove them.
• Maintained by the Scrum Master with input from the whole team.
• Serves as both an input and an output across SBOK processes like Conduct Daily Standup and Remove Impediments.
• Prioritizes impediments by impact and urgency to focus resolution efforts.
• Feeds Scrum of Scrums for cross-team or organizational impediments.
• Supports transparency and continuous improvement during Retrospect Sprint.

Purpose

The log exists to make blockers visible, assign clear ownership, and enable fast removal or escalation. It guides the Scrum Master and stakeholders to allocate help, negotiate dependencies, and protect team flow.

It also preserves learning across Sprints by showing patterns, systemic issues, and the effectiveness of resolution actions.

Key Terms & Clauses

• Impediment: Anything that reduces the team’s ability to deliver (e.g., environment outages, approvals, skill gaps, external dependencies).
• Severity vs priority: Severity is impact on value/flow; priority is the order to address. High severity items should be prioritized first.
• Owner: Person accountable for removing or coordinating removal; often the Scrum Master for external issues, sometimes a team member for local issues.
• Status values: New, In progress, Escalated, On hold, Resolved, Closed.
• Escalation path: Steps and contacts (e.g., vendor manager, architecture board, release management) when local actions stall.
• Time clause: Team working agreement such as blockers are escalated within 24–48 hours if unresolved.
• Risk vs impediment: Risks are uncertain events; impediments are current, active blockers. Risks belong in a risk register; impediments belong here.

How to Develop/Evaluate

1. Capture new impediments immediately during Daily Standup or as discovered, with a unique ID, description, date, reporter, and impact.
2. Assess severity and priority, note affected user stories/tasks, and identify an owner with a target resolution date.
3. Define the next best action and escalation path if the first action stalls.
4. Review the log daily for status updates, aging items, and trends; verify closure with the team.
5. Evaluate quality by checking clarity of descriptions, explicit ownership, realistic target dates, and traceability to Sprint items.
6. Archive closed items but retain for retrospectives to identify recurring or systemic impediments.

How to Use

• Conduct Daily Standup: Update entries, add new impediments, and confirm owners and next actions.
• Remove Impediments: Drive resolution, escalate when needed, and record outcomes and dates.
• Scrum of Scrums: Share cross-team blockers and coordinate organization-level support.
• Retrospect Sprint: Analyze patterns, root causes, and improvement actions to prevent recurrence.
• Sprint Planning and Create Tasks: Consider open impediments when forecasting capacity and task sequencing.
• Stakeholder communication: Provide transparent status on blockers that require external decisions or resources.

Example Snippet

• ID: IMP-17 — Test environment unstable; builds fail intermittently. Severity: High. Owner: Scrum Master. Status: Escalated. Next action: Engage DevOps lead for rollback plan. Target date: 21 Mar.
• ID: IMP-22 — Vendor API access pending approval. Severity: High. Owner: Product Owner. Status: In progress. Next action: Legal review meeting booked. Target date: 19 Mar.
• ID: IMP-25 — Shared UX resource unavailable for 3 days. Severity: Medium. Owner: Team member. Status: New. Next action: Re-sequence stories and request backup allocation. Target date: 18 Mar.

Risks & Tips

• Risk: The log becomes a parking lot with no action. Tip: Require owner, next step, and target date for every item.
• Risk: Confusing risks with impediments. Tip: Split current blockers from uncertain future events and manage them in the right place.
• Risk: Silent normalization of blockers. Tip: Highlight aging items daily and escalate within the agreed timeframe.
• Risk: Over-localized focus. Tip: Use Scrum of Scrums for cross-team or organizational impediments.
• Risk: Lack of visibility. Tip: Keep the log accessible and visible to the team and stakeholders.

PMP/SCRUM Example Question

During the Daily Standup, two new blockers are identified and one old blocker is resolved. What should the Scrum Master update and use to drive follow-up actions and escalation?

1. Product Backlog
2. Updated Impediment Log
3. Risk Register
4. Sprint Burndown Chart

Correct Answer: B — Updated Impediment Log

Explanation: The Updated Impediment Log captures current blockers, owners, status, and actions. It is the primary tool to manage and escalate impediments discovered in the Daily Standup.