Kanbanize is the leading Kanban software for agile project and portfolio management. It provides visibility across all projects and portfolios, connects planning with execution, and helps teams deliver faster.
What is the difference between Lead Time and Cycle Time in Kanban? How can you measure them and why should you do that? Find answers to these questions here.
Lead time and cycle time are widely used terms in the world of Kanban. However, very often, people get confused when trying to understand the difference between them and their importance. By the end of this reading, you will distinguish the terms easily and use them properly.
The business environment is dynamic, and it produces new customer demands constantly. These demands come to your company in the form of work requests.
Lead Time Definition:
Lead time is the period between a new task’s appearance in your workflow and its final departure from the system.
However, the lead time is better to be measured when a team member is committed to the new request. This way, the average lead time in a Kanban system will be much more accurate. Otherwise, new tasks can spend months in a waiting queue before somebody has the capacity to start them and the lead time increases dramatically.
When a new assignment appears on your Kanban board, it usually needs to be reviewed and discussed before it goes to the execution process. Naturally, the new task spends some time in a waiting queue before a member of your team has the capacity to start working on it.
Cycle Time Definition:
Cycle time begins at the moment when the new arrival enters the “in progress” stage, and somebody is actually working on it.
Professor John Little (Institute Professor at MIT) concluded after various researches that the more work we have in progress, the greater the system cycle time.
The equation became famous as Little’s law, and the cycle time formula looks like this:
Cycle Time = Work in Progress / Throughput
To make the most of this valuable information, you will need Kanban software to collect historical data for your workflow automatically. For example, Kanbanize is a powerful software solution equipped with a powerful analytics panel that can offer you all this information.
Cumulative flow diagram
One of the most convenient tools for measuring lead time and cycle time is the cumulative flow diagram. This chart tracks the total amount of your work items that enter your workflow and accumulates completed tasks over time.
The cumulative flow diagram allows you to quickly overview the average Lead time and Cycle time for a predetermined period.
"Kanban works, with 76% reporting Kanban to be more or much more effective than other methods."
Sometimes, a task can spend a lot of time in a waiting column before a teammate has the capacity to start working on it. This causes a greater gap between lead time and cycle time. Thus, assignments reach the completion stage slower.
To find where this problem comes from, you can use two of the most relevant analytic tools for that purpose (both part of Kanbanize analytics panel): Cycle time scatter plot and Heat map.
The first one gives you detailed information about all tasks' cycle time for a predetermined period of time. This way, you can locate tasks that took a greater amount of time to be completed.
The second one shows you data for the total amount of time that tasks spent in your workflow's different stages. It helps you understand where tasks spend the most time while progressing through your workflow.
Both tools will help you locate problematic parts of your work process and take action to eliminate them. You need to remember that work is an ongoing process, and it changes constantly.
Therefore, you have to monitor your workflow regularly and use the appropriate analytic tools. They help you to adjust your workflow and improve team efficiency.
Lead time and Cycle time are powerful statistics that:
During the 30-day trial period you can invite your team and test the application in a production-like enviroment.