Lead Time and Cycle Time
Level 3 Β· Kanban
The three numbers that show how work flows: lead time, cycle time and throughput. How they fit together, and how a flow chart shows where work piles up.
Course contentsLesson 11 of 19
Level 1 Β· What agile is
Level 2 Β· Scrum
Level 3 Β· Kanban
Level 4 Β· Stories, sizing and tracking
Level 5 Β· Other methods and scale
After this lesson you can
- Tell lead time from cycle time
- Work out cycle time from WIP and throughput
- Read a cumulative flow diagram
12 mincovers 4 glossary entries
Worth reading first: Kanban Board and WIP Limits
How fast work flows, in three numbers
Lead time is how long a piece of work takes from the moment it is asked for until it is delivered. Cycle time is how long it takes from when work on it starts until it is done. A request made on 1 March, started on 10 March and done on 14 March has a lead time of 13 days and a cycle time of 4.
The gap between the two is time spent waiting in a queue. In that example it is 9 days, more than twice as long as the work. Customers feel lead time, because they count from when they asked. So shrinking the queue often helps them more than working faster.
Throughput is how many items a team finishes in a set time, such as 5 a week. It counts finished items, not started ones, and needs no sizing. Teams use it to forecast. If a team finishes about 5 a week, 20 items will take about 4 weeks.
The three are tied together. On average, the work in progress equals throughput times cycle time. A team with 15 items in progress that finishes 5 a week has an average cycle time of 3 weeks. Cut the work in progress to 10, and the same team gets a cycle time of 2 weeks.
That is why WIP limits work. With the same throughput, less work in progress means each item gets through faster. It is the maths behind finishing more by starting less. The rule holds for averages over time, not for one card.
A cumulative flow diagram, or CFD, draws all of this at once. Each step on the board is a coloured band, stacked on the others, day by day. The height of a middle band shows the work in progress there. The width across a band shows about how long items take.
A band that keeps getting wider means work is piling up in that step. The common mistake is tracking only the average. Two teams with a 5-day average are very different if one is always 4 to 6 days and the other runs from 1 day to 20.
Worked example
Emma halves her lead time
Emma's design team has 30 requests in its queue and finishes 6 a week. A new request waits about 5 weeks before anyone starts it, then takes 4 days of work.
She stops taking new requests until the queue is down to 12. The team still finishes 6 a week, but the wait falls to about 2 weeks, and lead time drops by more than half.
The words for this lesson4
Check yourself
A team has 12 items in progress and finishes 4 a week. What is its average cycle time?
Finished this lesson?
Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.