Table of Contents
Little’s Law is a fundamental principle in queuing theory that relates the average number of items in a system, the arrival rate, and the average time an item spends in the system. Applying this law to Agile workflows can help teams optimize their throughput and improve efficiency.
Understanding Little’s Law
Little’s Law is expressed with the formula:
Work In Progress (WIP) = Throughput × Cycle Time
Where:
- Work In Progress (WIP): The number of tasks in progress at any given time.
- Throughput: The number of tasks completed per unit of time.
- Cycle Time: The average time to complete a task from start to finish.
Applying Little’s Law in Agile
Agile teams can use Little’s Law to identify bottlenecks and optimize workflow. By measuring cycle time and throughput, teams can determine the optimal WIP levels to maximize productivity without causing delays.
For example, if a team completes 10 tasks per week with an average cycle time of 2 weeks, the WIP should be around 20 tasks to maintain steady flow.
Calculations for Optimization
To improve throughput, teams can focus on reducing cycle time or increasing capacity. Calculations can help set realistic WIP limits and forecast delivery timelines.
For instance, if a team wants to increase throughput to 15 tasks per week and maintains a cycle time of 2 weeks, the WIP should be approximately 30 tasks.