If you’re a project manager or an Agile enthusiast, mastering the ins and outs of “kanban cycle time” can be a game-changer for your team’s productivity. As the lifeline of the Kanban method, understanding how to measure and optimize cycle time can greatly improve the flow of work. In this comprehensive guide, we’re going to break down everything you need to know to harness the power of Kanban cycle time.
Cycle time next to its neighbours
| Measure | Starts | Ends |
|---|---|---|
| Cycle time | Work starts | Work finishes |
| Lead time | Request or commitment | Delivered |
| Processing time | Active work begins | Active work stops |
| Work item age | Work starts | Today (for unfinished items) |
What is Kanban Cycle Time?
Kanban cycle time is the total elapsed time from when work starts on an item (i.e., when it is moved from the “to-do” column) until it’s fully completed (moved to the “done” category). It’s essentially a measure of how long it takes for one task to make its way through the entire Kanban board—a visual representation of your workflow.
Why is Tracking Cycle Time Important?
Tracking cycle time is a pivotal part of Kanban because it provides actionable insights into your team’s efficiency. By understanding how long tasks take, you can:
- Identify bottlenecks in the workflow
- Improve future estimations for project timelines
- Enhance resource allocation
- Increase customer satisfaction through better delivery predictions
- Foster a continuous improvement culture within your team
How to Measure Cycle Time
To effectively measure cycle time, you need to track two key points for every task: when work started and when it was completed. Many digital Kanban tools provide this functionality automatically. However, if you’re using a physical board, documenting these points with timestamps is crucial.
The cycle time formula is simple:
“`markdown
Cycle Time = Completion Date – Start Date
Tips for Reducing Cycle Time
Reducing cycle time is about smoothing out your workflow to eliminate unnecessary delays. Here are some strategies to implement:
- Limit Work in Progress (WIP): By capping the number of tasks that can be worked on simultaneously, teams are encouraged to finish current tasks before starting new ones.
- Implement Pull Systems: Only start new work when there’s a demand for it, rather than pushing tasks into the workflow regardless of current capacity.
- Use the Right Metrics: Alongside cycle time, monitor throughput and work item age to get a comprehensive view of your workflow efficiency.
- Continuous Improvement: Regularly review your team’s performance and make small, incremental changes to enhance workflow.
Visualizing Cycle Time with a Cumulative Flow Diagram
One of the most powerful tools to visualize and analyze cycle time is the Cumulative Flow Diagram (CFD). A CFD can help you track the number of tasks in each stage of your workflow over some time, highlighting potential bottlenecks.
Common Pitfalls in Cycle Time Analysis
Beware of common pitfalls when analyzing cycle time:
- Not accounting for outliers: Some tasks will naturally take longer than others. Focus on your process’s average time, and understand the context for outliers.
- Focusing too much on speed: Speed is important, but not at the cost of quality. Ensure quality standards are met, even if that slightly increases cycle time.
Reading a cycle time scatter plot
Plot each finished item as a dot, with the finish date across and the cycle time up. Draw a line at the 85th percentile. Dots well above the line are items that waited or were too large. Most teams see a few of these, and looking at each one usually reveals a cause, such as a missing review, an unclear requirement or a dependency.
| Pattern | What it suggests |
|---|---|
| Tight cluster, steady line | Predictable process |
| Wide spread | Inconsistent item sizes or frequent blocking |
| Line rising over weeks | Growing WIP or a new bottleneck |
| Two clear bands | Two types of work mixed; track them separately |
Ways to reduce it
- Lower WIP limits so people finish before starting.
- Split large items so they fit one cycle.
- Remove waits: review queues, approvals and environments usually hide the most time.
- Swarm on the oldest item before taking something new.
- Track blocked time separately so it is visible, not buried in the number.
Cycle time ties to throughput and WIP through Little’s Law, and the measures sit alongside other Kanban metrics. For training, see Team Kanban Practitioner (TKP) (8 hours, $550) and Kanban Management Professional (KMP) (32 hours, $2,200).
Additional discounts are available. Contact us to know more.
Conclusion
Kanban cycle time isn’t just another metric—it’s a crucial element in understanding and improving your workflow. By taking the time to assess and refine your approach based on cycle time, you can help your team work more efficiently and deliver a consistent, quality output.
Whether you’re a seasoned Kanban user or just getting started, recognizing the role cycle time plays in project management can open doors to improved strategies and workflows. Keep these tips in mind to ensure that your project not only runs smoothly but also continues to evolve and improve over time.
As you continue to navigate the intricacies of kanban cycle time, consider elevating your expertise further with AgileFever’s Kanban System Design (KSD) certification. This course will not only solidify your understanding of cycle time but will also provide you with comprehensive training on the principles of the Kanban method. With the KSD certification, you’ll gain the skills necessary to build efficient, high-performing teams, and truly master the art of workflow optimization. Join a community of forward-thinking professionals and take the next step in your Agile journey. Sign up today to learn more about how Kanban can revolutionize your project management strategy.
More questions answered
What is a good cycle time?
It depends on the size of the items and the work. Compare your own team over time, and aim for a falling and narrowing trend rather than a target from another company.
Should I include weekends in cycle time?
Pick one approach and keep it. Many teams count calendar days. Some count working days. Mixing the two makes the numbers hard to compare.
Is cycle time the same as lead time?
No. Cycle time starts when work starts. Lead time starts when the request arrives, so it includes the wait before work begins.
Last reviewed October 2026 by the AgileFever editorial team.