DevOps work tracking
Microsoft's work-item tracking within Azure DevOps, offering Kanban boards with WIP limits and cumulative flow analytics.
- Kanban
- WIP limits
- CFD
- Cycle time
- Lead time
- Pricing
- Free plan + paid
- Deployment
- Cloud, Self-hosted
Kanban software gives a team an online kanban board where cards move through columns, with WIP limits and flow data built in. The tools on this page range from simple boards for one team to platforms that link many boards, so the right choice depends on how far your kanban practice has gone.
Who it's for
Software, IT, marketing and operations teams that want to see their work, stop starting too much at once and finish more. Many teams adopt it early in a lean program.
Showing 7 of 7 tools
DevOps work tracking
Microsoft's work-item tracking within Azure DevOps, offering Kanban boards with WIP limits and cumulative flow analytics.
Enterprise Kanban platform
Kanban-native work management platform (formerly Kanbanize) with portfolio boards, flow analytics, OKRs and X-matrix planning.
Digital daily management
Digital daily management system for process industries with shift handover, tier boards, routines and escalations.
Agile issue tracking
Atlassian's agile work tracker with Scrum and Kanban boards, WIP limits and control/cumulative flow reports.
Open-source self-hosted Kanban
Minimalist PHP Kanban board for self-hosting, with WIP limits, swimlanes, automation rules and a plugin ecosystem.
Enterprise Kanban
Enterprise Kanban tool (formerly LeanKit) linking team boards to roadmaps, OKRs and dependencies, with lean flow metrics.
Leader standard work and tiered meetings
Connected leader software for leader standard work, tiered meetings, gemba walks, LPAs and visual management boards.
The basics
Kanban software gives a team a digital board for knowledge work. Cards move through columns that match the real steps of the work, with limits on how much can be in progress.
It borrows from the kanban signal cards of the Toyota Production System. Shop-floor kanban for parts and materials is a separate category: e-kanban software. The kanban methodology guide covers the principles and practices behind the board.
The Kanban Guide describes three practices: defining and visualizing the workflow, actively managing items in the workflow, and improving the workflow. The kanban method page explains each.
A whiteboard and sticky notes work well for one co-located team. They make the team design its own columns and policies, which is the hard part.
Software earns its place when the team is remote, needs history for flow metrics, or wants boards to roll up into a portfolio view. The digital kanban guide covers the switch.
The routine it supports
How the listed tools are priced
Most project tools now offer a board view, so the question is what kanban board software adds. The answer is usually three things: WIP limits the board enforces, explicit policies on each column, and flow metrics such as cycle time and throughput taken straight from card history.
If you only need a shared to-do list, a board view in a tool you already pay for may be enough. If you want to practice the kanban method, check those three features first. The kanban project management guide shows how the practices fit together.
Many kanban tools have a free plan, usually limited by the number of users, boards or features such as reporting. Open source kanban software is another route: you host it yourself and keep the data on your own servers, in exchange for running updates and backups.
A free tool is a good way to learn whether the team will keep the board current. Before you commit, check whether you can export cards and history, because flow data is the part you will want to keep. The free kanban board guide covers the options, from paper to online boards.
Scrum tools are built around sprints: a backlog, a sprint board that resets every iteration, and velocity or burndown charts. Kanban tools are built around continuous flow, so the board does not reset and the main measures are cycle time, throughput and work in progress.
Many tools support both, and some teams run scrum events with a kanban board. If your team plans in fixed sprints, check that the tool handles sprints well. If work arrives continuously, such as support or operations work, a kanban-first tool usually fits better. The kanban methodology guide explains the differences in practice.
Buying guide
Who it's for: Software, IT, marketing and operations teams that want to see their work, stop starting too much at once and finish more. Many teams adopt it early in a lean program.
Enforced WIP limits
Limits per column and swimlane that the board shows and warns on. Without them, a digital board is a long to-do list.
Explicit policies
Space to write the definition of done and entry rules on each column, so the board explains itself to new people.
Built-in flow metrics
Cycle time, throughput and a cumulative flow diagram generated from the board itself instead of from exported data.
Blocker tracking
A way to flag blocked cards and record why, so you can find the most common causes of delay later.
Before you choose
FAQ
Sources
Written by the lean-stack editors following our methodology. Updated October 3, 2026.
For vendors
Submit it for review. Every tool is checked against our listing criteria and researched from public sources. Approved tools join their category in the next published batch.