Blocked

Blocked refers to a situation where a work item, task, or user story cannot progress due to an unresolved issue or dependency. It indicates that something external is preventing completion, such as missing information, approval delays, technical issues, or resource constraints.

In Agile and project management, marking an item as blocked makes the obstacle visible to the team and stakeholders, allowing for faster problem resolution and preventing hidden delays.

Advanced

A blocked status is commonly used on task boards, Kanban boards, or sprint backlogs to signal impediments that affect workflow. Teams use visual indicators, such as color codes or tags, to highlight blocked tasks.

Advanced tracking involves root cause analysis and categorization of blockages, such as external dependencies, technical defects, or business decisions. Regular stand-up meetings or review sessions help identify and remove blockers quickly, maintaining steady progress and protecting team velocity. In Agile environments, the Scrum Master or project lead typically facilitates the removal of blockers.

Relevance

• Improves visibility of workflow issues that hinder progress
• Encourages proactive communication and collaboration
• Helps teams identify and address systemic process bottlenecks
• Prevents work from stagnating during sprints or cycles
• Enables faster problem resolution and accountability
• Supports continuous improvement by analyzing recurring blockers

Applications

• A developer marking a task as blocked due to missing API access credentials
• A content writer waiting for stakeholder approval before publishing
• A QA tester pausing verification while waiting for a development fix
• A project team identifying a vendor delay as a blocking issue
• A Scrum Master facilitating resolution of technical dependencies

Metrics

• Number of blocked items per sprint or iteration
• Average time tasks remain blocked
• Frequency of recurring blockers in specific workflows
• Impact of blockers on team velocity and throughput
• Resolution rate and time to unblock tasks

Issues

• Blocked tasks can delay dependent work and create project bottlenecks
• Unreported blockers lead to inaccurate progress tracking
• Repeated blockers indicate systemic communication or process issues
• Failure to resolve blockers promptly can lower team morale
• Overreliance on manual reporting may obscure real-time visibility

Example

A development team marked a key user story as blocked because a required third-party API was unavailable. By raising the issue in the daily stand-up, the Scrum Master coordinated with the vendor to resolve it within 24 hours, allowing the sprint to continue without significant delay.