Overview
Direct Answer
Kanban is a lean workflow management approach that visualises tasks as cards moving through defined stages, with explicit limits on concurrent work in each stage to prevent bottlenecks. It originated in Japanese manufacturing but has been widely adopted in software development to regulate work-in-progress and improve delivery predictability.
How It Works
Work items are represented as cards on a board divided into columns representing workflow states (typically To Do, In Progress, Done). Each column has a work-in-progress limit that constrains the maximum number of items allowed simultaneously, forcing completion before new work enters that stage. Metrics such as cycle time and throughput are tracked to identify constraints and optimise flow.
Why It Matters
Organisations value this method because it reduces waste, shortens delivery cycles, and enables teams to respond rapidly to emerging priorities without disrupting established processes. By exposing bottlenecks through visual constraints, teams can allocate resources more effectively and maintain sustainable pace, reducing context-switching costs and burnout.
Common Applications
The approach is used across software development teams, IT operations, manufacturing support, and administrative workflows. Examples include continuous-deployment pipelines, help desk ticket management, and content publishing workflows where stable, predictable throughput is required.
Key Considerations
Kanban requires discipline in setting realistic work-in-progress limits; overly generous limits defeat the constraint mechanism. Teams must establish clear stage definitions and metrics collection, as poorly defined workflow states can obscure rather than reveal system problems.
More in Software Engineering
Version Control
Development PracticesA system that records changes to files over time so that specific versions can be recalled later.
Load Testing
Quality & TestingTesting a system's behaviour under expected and peak load conditions to ensure adequate performance.
Garbage Collection
Paradigms & PatternsAutomatic memory management that reclaims memory occupied by objects no longer referenced by the program.
Memory Leak
Paradigms & PatternsA type of resource leak where a program fails to release memory that is no longer needed.
Feature Flag
Development PracticesA software development technique allowing features to be enabled or disabled at runtime without deploying new code.
Relational Database
Paradigms & PatternsA database structured to recognise relations among stored items, organised in tables with rows and columns.
Monorepo
Development PracticesA version control strategy where multiple projects or packages are stored in a single repository.
Dependency Injection
Paradigms & PatternsA design pattern where dependencies are provided to a component rather than created within it.