What is lead time?
Quick definition
The total elapsed time from when work is requested until it is delivered to the customer or user, measured from initial request to final completion.
Lead time is a critical metric in Kanban and agile workflows that measures the complete duration a work item spends in your system from request to delivery. Unlike cycle time, which starts when work begins, lead time includes the entire waiting period before work actually starts, such as time spent in backlog or queue. This metric helps teams understand customer-facing responsiveness and identify bottlenecks in their workflow, including prioritization delays.
In software development and AI agent workflows, lead time encompasses all delays: prioritization wait, queue time, active work duration, and testing phases. For developers using Kanban boards or managing agentic workflows, tracking lead time reveals whether delays stem from insufficient WIP limits, unclear prioritization, or actual execution time. Lower lead times indicate better responsiveness to customer needs and faster value delivery.
Lead time is essential for capacity planning and setting realistic delivery expectations. Teams measuring lead time can identify systemic inefficiencies, optimize their pull-system, and establish service level agreements with stakeholders. In AI agent orchestration, lead time helps measure end-to-end latency from user request to agent completion.
Example
How it shows up in practice
If a task is created on Monday morning and deployed on Friday afternoon, the lead time is approximately 4.5 days. This includes time waiting in backlog, time in sprint planning, actual development, code review, and deployment.
Frequently asked questions
What is the difference between lead time and cycle time?
Lead time measures from request creation to delivery, including all waiting periods. Cycle time measures from when work actually starts (like sprint start) until completion. Lead time is always greater than or equal to cycle time.
Why is lead time important for developers?
Lead time helps developers understand customer impact and identify delays in their process. It reveals whether bottlenecks exist in prioritization, queuing, or execution phases, enabling process improvements.
How do Kanban WIP limits affect lead time?
Proper WIP limits reduce lead time by preventing excessive work accumulation in queues and ensuring work moves smoothly through the system. Overly high WIP limits increase lead time due to longer wait times.
Can lead time be tracked automatically?
Yes, modern project management tools and AI systems can track lead time by recording task creation timestamps and completion dates. Kanboard and similar tools provide lead time analytics automatically.