What Is Kanban

What does Kanban mean?

Kanban is a visual method for managing and processing work, built around visualizing what a team is doing, limiting how much work is in progress at once, and maximizing flow through the system. Per Atlassian, Kanban's core values are respect for people and continuous improvement, and it is deliberately a start with what you do now method, meaning a team does not need to overhaul its existing process to begin using it. A kanban board makes work visible as cards moving through columns representing stages, and work-in-progress limits on those columns are what actually force a team to finish current work before pulling in new work, rather than starting everything at once. Removing that limit quietly turns the board back into a to-do list with no real constraint on how much work is in flight.

Why Kanban matters for product managers

Builders Camp's Beyond Agile certification quiz asks students directly what the primary focus of the Kanban framework is, and the correct answer names flexibility, waste reduction, and strict work-in-progress limits suited to small, experienced teams, not fixed sprints or rigid, structure-heavy delivery. That framing matters for a PM choosing a delivery model, since Kanban and Scrum solve different problems: Kanban suits continuous, unevenly-sized work like support-adjacent product tickets, while sprint-based frameworks suit work that benefits from a fixed planning cadence. Picking the wrong one for the shape of the work is a common early mistake: forcing sprints onto unpredictable support-driven work just relocates the chaos into a two-week box instead of removing it. For a side-by-side view of how Kanban's flow model compares with Scrum's Sprints and Shape Up's six-week cycles, see Scrum vs Kanban vs Shape Up.

Kanban example

A product team handling a mix of small bug fixes, mid-size feature work, and occasional urgent customer escalations finds sprint planning breaks down every time an escalation forces a mid-sprint replan. Builders Camp's Beyond Agile material recommends Kanban here specifically because the work is too uneven in size and urgency for fixed sprints to handle cleanly; a strict work-in-progress limit on the in development column keeps the team from starting five things at once, and the visible board makes it obvious when an urgent item is genuinely worth interrupting current work instead of quietly bypassing whatever prioritization matrix the team normally uses. Over a few weeks, the limit itself becomes the team's clearest signal of whether it is genuinely overloaded or just feels that way.

How Builders Camp teaches Kanban

Beyond Agile, a 1 week bootcamp with 1 live session and 11 microlessons taught by Andre Albuquerque, tests Kanban directly in its certification quiz as part of comparing delivery frameworks beyond standard Scrum. Project Management for Product covers the execution discipline that keeps a Kanban board's work-in-progress limits actually enforced day to day. See the Beyond Agile bootcamp for the full curriculum.