Home › Agile glossary › Blocker
Blocker
A blocker is anything preventing an in-flight item from progressing — a missing decision, an unavailable dependency, an unanswered question.
Blockers are the highest-value thing a standup surfaces, and the most commonly mishandled: a blocker named without an owner and a date is a wish. The rule that makes standups worth attending is that every blocker leaves the meeting assigned to a person.
Chronic blockers of the same shape — always waiting on the same approval, always missing the same credential — are process problems, not incidents. They belong in the retrospective, not in tomorrow's standup again.
In Flocci Projects
There is no dedicated blocked status or flag; teams record blockers as a comment on the issue (with an @mention of whoever must unblock it) and rely on the activity history for the trail.
Related terms
See it on a free boardBrowse the whole glossary
- Agile
- Backlog refinement
- Burndown chart
- Burnup chart
- Cycle time
- Daily standup
- Definition of done
- Definition of ready
- Epic
- Kanban
- Lead time
- Planning poker
- Product backlog
- Product owner
- Retrospective
- Scrum
- Scrum master
- Sprint
- Sprint goal
- Sprint planning
- Sprint review
- Story point
- Swimlane
- Throughput
- User story
- Velocity
- WIP limit