Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system, based on the average waiting time of an item within a system and the average number of items arriving at the system per unit of time. The long-term average number L of customers in a stationary system is equal to the long-term average effective arrival rate λ multiplied by the average time W that a customer spends in the system

Little’s law variables:

  • L = The average number of work items in a queuing system / Work In Progress (WIP).
  • λ = The average number of items arriving at the system per unit of time / The long-term average effective arrival rate / Throughput / The rate at which the items go in and out of the system.
  • W = The average waiting time a work item spends in a queuing system / Lead time.
Littles law - Kanban adaptation

Example 1

On average 30 cars come to the fast food takeaway every hour. They usually spend 6 minutes there (0,1 hour). L= 30×0.1= 3 cars are usually in the line.

Example 2

A team takes on 24 items they usually finish in four weeks and works on them simultaneously.

Littles law - example 1

but if half the items are being worked on at the same time

Littles law - example 2

which enables lowering cycle time to half, meaning that the value will be delivered faster, with no other improvements.

What is it for:

  • Exposes the real performance
  • Provides predictability
  • Helps to reduce/manage multitasking
  • Helps to balance the work in progress and Lead time
  • Enables setting the WIP limits
  • Reduces Throughput which increases the Lead time

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.