Kanban defined!

A visual management tool used to visualize the development process, identifying the status of work items in real-time. Columns usually represent process steps (e.g., To Do, Doing, Done).

A constraint applied to a specific column or the entire board that limits the maximum number of items allowed in that stage. It forces the team to finish work before starting new tasks.

A production method where work is only started (pulled) when there is demand or available capacity, rather than being forced (pushed) onto the team by management.

The time it takes for a task to move from the moment work begins (e.g., entering the "In Progress" column) to the moment it is completed.

The total time elapsed from the moment a customer makes a request to the moment the work is delivered. It includes the time the request spent sitting in the backlog.

A visual representation of a work item. It contains critical information such as the task description, assignee, due date, and class of service.

Horizontal rows on a Kanban board used to categorize work types, such as different projects, teams, or urgency levels (e.g., a "Fast Lane" for expedited work).

The movement of work items through the Kanban system. The goal of Kanban is to maximize smooth, continuous flow and minimize stoppages.

A stage in the process where work piles up because the capacity of that stage is less than the demand placed upon it, slowing down the overall flow.

A specific area chart used in Kanban to show the status of work items over time, helping to identify bottlenecks, cycle time trends, and scope creep.

The number of items passing through a system or process (completed) over a specific period of time (e.g., 5 cards per week).

A Japanese philosophy of continuous improvement. In Kanban, it refers to the practice of constantly tweaking the process to improve efficiency and quality.

The agreed-upon rules for how work is done, documented and visible to everyone. Examples include "Definition of Done" or criteria for pulling a card into the next column.

A categorization of work items based on their cost of delay or urgency (e.g., "Expedite," "Fixed Date," "Standard," "Intangible").

An issue or dependency that prevents a work item from moving forward. In Kanban, these are often visualized with a pink or red sticker on the card.

The average number of items in a stable system (WIP) is equal to the average completion rate (Throughput) multiplied by the average time an item spends in the system (Cycle Time).

A regular meeting where the team selects the most important items from the backlog and moves them into the "To Do" or "Ready" column, up to the WIP limit.

The specific point in the process where the team agrees to work on an item and the "clock starts" for Lead Time. Before this point, the item is just an option.

The point in the process where the work is considered finished and is handed over to the customer or end-user.

A management strategy that aligns raw-material orders or work initiation directly with production schedules, minimizing inventory costs and waste.

A forecast of how long a work item should take to complete, based on historical data (e.g., "85% of our standard tasks are finished in 4 days or less").

Available capacity or "idle time" in the system. In Kanban, slack is viewed positively as it allows the team to handle variability or focus on improvements (Kaizen).

Mechanisms put in place to review the process and the product, such as the Service Delivery Review or Operations Review, to ensure the system is working effectively.

The rhythmic cycle of meetings and reviews (e.g., daily stand-ups, weekly replenishment) that keeps the Kanban system organized and predictable.

The core principle of making work visible. If you can't see the work, you can't manage it. This allows the team to understand the current state of the system instantly.