Course contentsShow
← Software Engineering
Lesson 1592 of 1,93346. Agile MethodologiesFree lesson

Kanban Origins and Principles

The Toyota Production System roots of Kanban and its core principles of visualizing work and limiting WIP.

Kanban Origins and Principles

What you'll learn: How Kanban emerged from Toyota's manufacturing floor and what core principles make it effective for managing software work.

From Factory Floor to Software Teams

Kanban didn't begin in software—it originated in the Toyota Production System (TPS) during the 1940s-50s. Toyota needed a way to manage inventory efficiently and respond quickly to customer demand. They invented a "pull" system using visual cards (kanban means "signboard" in Japanese) that signaled when new parts were needed. A worker would only produce items when there was actual demand, preventing overproduction and waste.

This approach revolutionized manufacturing by emphasizing just-in-time production and continuous flow.

Core Principles Applied to Software

When Kanban was adapted for software development in the mid-2000s, it retained these foundational principles:

1. Visualize Work

Make all work visible on a board with columns representing workflow stages (e.g., "To Do," "In Progress," "Code Review," "Done"). Each task is a card moving across the board. Just like Toyota's factory floor, seeing the flow helps identify bottlenecks and blockers immediately.

Analogy: Imagine traffic on a highway—if you can see where cars are backing up, you know where the problem is.

2. Limit Work in Progress (WIP)

Set maximum limits on how many tasks can exist in each column simultaneously. This prevents team members from juggling too many things at once, which reduces context-switching and improves flow efficiency. In Toyota's system, this meant not building more parts than needed; in software, it means not starting new features until current ones move forward.

Key Takeaway: Kanban brings Toyota's manufacturing wisdom to software: visualize your workflow and limit WIP to create steady, sustainable flow and quickly identify where work gets stuck.