Kanban

Kanban is agile's quieter sibling: no sprints, no ceremonies — just work made visible on a board, limits on how much is in progress at once, and a continuous flow from 'to do' to 'done'. It is the methodology of choice when work arrives unpredictably, which is to say: operations, support, and most of reality.

What It Is

Kanban is a method that visualises workflow on a board — columns for stages (Backlog, In Progress, Review, Done), cards for work items — and manages flow through it. Its two signature disciplines: work-in-progress (WIP) limits, which cap how many items may sit in any stage, forcing finishing over starting; and making everything visible, so blockages and queues are seen rather than felt. Unlike Scrum, Kanban has no fixed iterations — work flows continuously, priorities change as needed, and improvement comes from studying the flow itself (lead time, cycle time, bottleneck migration). It originated in Toyota's manufacturing ('kanban' = signboard) before software adopted it.

Why It Matters to You

Kanban matters to executives because it is honest infrastructure for operations. The board is a live map of where work actually is and where it piles up — the age of the oldest card in a column is often the most damning metric in the building. WIP limits encode a truth most organisations resist: starting more work makes everything slower; finishing work is what counts. Because Kanban fits work that arrives on demand (support, maintenance, incident response, intake), it coexists naturally with Scrum — many organisations run Scrum for product builds and Kanban for the operational stream that serves the same systems.

When You'll Meet It

In operations, support, and platform teams, and in any workflow review. If you want one question: 'show me the board' — then look at the oldest card in each column and ask what it is waiting for.