Description: A blocker in the context of Kanban and agile methodologies refers to any problem or impediment that prevents a team from progressing in their work. These blockers can arise from various sources, such as external dependencies, lack of resources, technical issues, or pending decisions. Identifying and managing blockers is crucial for maintaining workflow and team efficiency. In a Kanban board, blockers are often visualized with a specific color or symbol, allowing all team members to quickly recognize the obstacles that need to be addressed. Effective management of blockers not only helps resolve immediate issues but also fosters a culture of continuous improvement, where the team learns to anticipate and mitigate future impediments. In summary, blockers are critical elements that require attention and action to ensure that the team can meet its goals and delivery deadlines.
History: The concept of blocker in agile methodologies has developed over the evolution of these practices, which began to take shape in the 1990s with the introduction of methods like Scrum and Kanban. Kanban, in particular, originated in the Japanese manufacturing industry, specifically at Toyota, where it was used to optimize production. As agile methodologies expanded into software development, the identification and management of blockers became an essential practice for improving efficiency and collaboration within teams.
Uses: Blockers are used in the context of Kanban and agile methodologies to identify and resolve issues that affect workflow. Teams often hold daily meetings, known as ‘stand-ups’, where current blockers are discussed. Additionally, project management tools can be used to allow teams to log and track blockers visually, facilitating their resolution. Managing blockers is essential for maintaining productivity and ensuring that projects progress without interruptions.
Examples: An example of a blocker could be the lack of client approval to proceed with a phase of the project, preventing the team from moving forward. Another case could be a technical issue, such as a software failure that prevents necessary testing. On a Kanban board, these blockers would be clearly marked so that all team members can see them and work on their resolution.
