kanban: continuous flow

Kanban traces back to the Toyota Production System, later adapted to knowledge work. It centers on a visual board with columns representing workflow stages, and WIP (work-in-progress) limits that cap how many items can sit in each stage at once — forcing the team to finish work before starting more, rather than starting everything at once and finishing nothing.
Unlike Scrum, Kanban has no prescribed roles, events, or fixed-length iterations — it's a continuous-flow system layered onto whatever process already exists, which makes it a lighter starting point. It tends to fit unpredictable, continuously arriving work (support tickets, ops incidents, bug triage) better than Scrum's fixed sprints, which assume work can be planned in batches ahead of time. Kanban's core health metrics — cycle time and throughput — are the same ones worth watching on any team.

extreme programming (xp): engineering discipline

Extreme Programming (XP) focuses specifically on engineering practices rather than process or ceremony: pair programming, test-driven development, continuous integration, small and frequent releases, and collective code ownership. Where Scrum and Kanban organize how work flows, XP is about the technical discipline that keeps the code itself healthy while that work is happening — the two layers complement each other rather than compete.

lean: eliminating waste

Lean, also rooted in the Toyota Production System, centers on maximizing value by eliminating waste. Applied to knowledge work, common wastes include partially done work, unrequested extra features (gold-plating), knowledge lost through poor handoffs, constant task-switching, waiting/delays, and defects. Lean's other core idea — optimize the whole system, not just local parts — echoes the same lesson as a resource-critical path: making one piece locally faster doesn't help if it isn't where the actual bottleneck is.

how they combine

These aren't mutually exclusive choices. Kanban and XP are a very common pairing — a Kanban board for visualizing flow, XP practices for code quality underneath it. Some teams run Scrumban — Scrum's cadence and roles combined with Kanban's board and WIP limits. Lean functions less as a competing framework and more as an underlying philosophy about waste that shows up inside all of the others.

a short example

A platform team splits into two working modes. The feature squad builds new functionality in two-week Scrum sprints, because that work arrives in plannable batches. The on-call/support squad handles bug reports and infrastructure requests that arrive continuously and unevenly — sprint boundaries would just get broken constantly — so it runs a Kanban board with WIP limits instead. Both squads still practice code review and continuous integration, XP-style engineering discipline, regardless of which outer framework organizes their work.

practical notes

Which framework matters less than staying honest about which one is actually being followed. Mixing Scrum ceremonies with a Kanban mindset without acknowledging the switch — sprint planning for work that keeps arriving unpredictably mid-sprint — tends to produce confusion, not the best of both worlds.

related topics

reference