Kanban | Glossaire

Kanban is a Japanese-originated project and workflow management method that enables teams to visualize, manage, and optimize their work flow. Based on lean production principles, this approach uses a visual board to represent different stages of a process and limit work in progress (WIP). Unlike iterative methods like Scrum, Kanban operates as a continuous flow, allowing greater flexibility and constant adaptation to changing priorities.

Kanban Fundamentals

Workflow visualization: Clear representation of all tasks and their progression through different columns (To Do, In Progress, Done, etc.)
WIP limitation: Setting maximum limits on simultaneous tasks per column to prevent overload and improve focus
Flow management: Continuous optimization of work throughput by identifying and eliminating bottlenecks
Continuous improvement: Application of Kaizen principles to progressively refine processes and increase efficiency

Benefits of Kanban

Complete transparency: Immediate visibility into the status of all work for the entire team and stakeholders
Enhanced flexibility: Ability to add or reprioritize tasks without waiting for sprint completion, unlike fixed iterative methodologies
Reduced lead times: WIP limitation and flow smoothing enable faster feature delivery
Rapid bottleneck identification: Constraints become instantly visible, facilitating proactive resolution
Improved predictability: Flow metrics (lead time, cycle time) enable more reliable forecasting

Practical Kanban Board Example

Here's a typical Kanban board structure for a software development team, with WIP limits:

kanban-board-structure.md

## Kanban Board - Dev Team

| Backlog | To Do (5) | Analysis (3) | Development (4) | Code Review (2) | Testing (3) | Done |
|---------|-----------|--------------|-----------------|-----------------|-------------|-------|
| 25 items| 4 items   | 2 items      | 4 items         | 1 item          | 2 items     | 156 items|

### Board Rules:
- Each column has a WIP limit (number in parentheses)
- Blocked cards are marked in red
- Urgent cards have a priority flag
- Current average lead time: 8.5 days
- Current average cycle time: 5.2 days

### Key Metrics:
- Throughput: 12 items/week
- Blocking rate: 8%
- Capacity utilization: 87%

Implementing Kanban

Map the current flow: Identify all stages work passes through, from initial request to final delivery
Create the visual board: Establish columns representing each process stage, either physically (whiteboard) or digitally (dedicated tool)
Define WIP limits: Start with conservative limits based on team size, then progressively adjust based on observations
Establish explicit policies: Clearly document criteria for moving between columns (Definition of Done for each stage)
Measure and optimize: Collect flow metrics (lead time, cycle time, throughput) and hold regular retrospectives to improve the system
Implement service classes: Define different work types (standard, expedite, fixed date) with their own processing rules

Professional tip

Start with a simple Kanban board with 3-4 columns maximum and gradually increase granularity. Initial over-complexity is the most common mistake. Focus first on WIP limitation and flow observation before adding additional columns. An effective WIP limit should occasionally create situations where the team cannot start new work, which forces collaboration to unblock in-progress tasks.

Popular Kanban Tools

Jira: Comprehensive solution with advanced metrics features, flow reports, and automation
Trello: Intuitive card-based interface, ideal for small teams and simple projects
Azure DevOps Boards: Native integration with Microsoft ecosystem and CI/CD pipelines
Monday.com: Flexible visual platform with numerous customization and automation options
GitHub Projects: Kanban integrated directly into repositories for development teams
Kanbanize: Specialized tool with advanced analytics and multi-team support for complex organizations

Kanban offers a pragmatic and scalable approach to project management, particularly suited to environments where priorities change frequently. By combining visualization, work-in-progress limitation, and continuous improvement, this method significantly increases productivity while reducing team stress. Its progressive adoption, without major organizational disruption, makes it an excellent starting point for organizations seeking to initiate agile transformation.