Maximise Customer Satisfaction: Kanban Cycle Time
The one question that project managers hate to hear – “How long will this take?”.
Being able to estimate how much time is needed for a team using the Kanban method to complete a client request lets project managers plan ahead and inspires client confidence. Kanban cycle time tracks the average time taken and the probability to complete any type of task within a project.
While cycle time can be used to assess your team’s efficiency, it can also be used to predict future task performance. Cycle time scatterplots are a great visual method to estimate task times and quickly spot problem areas. Reducing your cycle times means higher team productivity, faster delivery, increased customer satisfaction.
Kanban cycle time vs lead time
Kanban lead time is the time between a request being made and a task being released. It’s the total time the client is waiting for a task to be delivered. Lead time is frequently used from Kanban teams to evaluate customer satisfaction.
Kanban cycle time is calculating the actual work-in-progress time. It tracks how long a task stays in the different process stages. Keeping track of your cycle times enables you to measure your team performance. Low cycle times means that your team is efficient. High cycle times indicates stalls, bottlenecks and backlogs. Keeping cycle times down keeps lead time down – and fast lead times means high customer satisfaction.
Cycle time scatterplot
The horizontal axis represents a period of time. Tasks completed in this period appear on the cycle time scatterplot.
Each of the dots scattered across the graph represents a single task from your Kanban board. Тhe positions of the dots are determined by the date of completion. The vertical axis represents cycle time in days – the vertical position of each dot is determined by the number of days taken for the card to be delivered.
The dotted horizontal lines crossing the plot are called percentile lines. The line labelled with 50% signifies that half of the tasks have been completed within the corresponding number of days. Higher percentile means a greater chance of completing any type of assignment within a certain time frame.
Cycle time scatterplots are used to track team performance and define service level agreements by forecasting the cycle time on future assignments.
Measure cycle time
Kanban cycle time is the total amount of elapsed time between when a task starts and when a task finishes. Where a dot appears on the scatterplot shows the cycle time for that task. Tasks clustered along the bottom axis were completed quickly, while the higher a dot appears, the longer it took to complete. Using cycle time scatterplot you can easily compare how tasks of different type perform.
Track team performance using cycle time
Cycle time indicates how fast individual tasks on your Kanban board are being completed. Low cycle times mean that your team is performing well. By keeping performance high and cycle times down your team delivers results faster which means more happy customers.
Predict task completion time using cycle time scatterplots
Historical data can be used to predict future task performance and give accurate data-driven estimates to clients. Kanban teams use cycle time scatterplot percentiles as the most accurate approach to predict how much time a task will take.
Using the horizontal percentile lines, we can see that there is a 50% chance that any type of task will be completed within 8 days, and a 95% chance it will be completed within 72 days. The higher the percentile, the more likely that any assignment will be completed within that specific time frame.
WE UNCOVER THE EFFICIENCY OF YOUR WORKFLOW
Optimise your performance with Kanban analyticsExplore Your Data Now
How to improve your cycle time
Reducing your cycle times results in improved team efficiency and higher customer satisfaction. The key to keeping Kanban cycle time down is applying a limit on your work in progress. Think about it – are you faster when you give 100% to just one task, or when your focus is pulled in different directions?
The relationship between the three main Kanban metrics – cycle time, throughput and WIP – is described by Little’s Law . This formula applies to stable systems following Little’s Law assumptions. WIP limits enforce this by not allowing new tasks to be started before an outstanding task is finished.
Cycle Time = WIP/Throughput
Little’s Law states that changing one of the three metrics will have an effect on one or both of the others. For example, for cycle time to come down, WIP must decrease. WIP limits can be changed without making any drastic changes to your team. Little’s Law can be used to select an optimal work in progress limits.
By allowing your team to focus on just a few tasks and keeping priorities in order, stalled, half-finished tasks are not likely to pile up. Kanban cycle time scatterplot lets you quickly spot any impediments by analysing tasks that have much longer cycle time than the rest. Learn more about the most common cycle time scatterplot patterns to easily identify bottlenecks in your process. Once identified, you can begin to tackle the root cause of any delays. Try it and see!
Has analysing your progress helped you spot any bottlenecks? How do you keep track of your team’s cycle times? What steps have you taken to reduce your cycle times? Tell us about your experience in the comments.
Meet the Author
Sonya Siderova is an independent consultant who helps organisations deliver successful projects as a Product Manager and Agile Coach. She is a proud mother of a daughter and a son, and enjoys good food and heavyweight boxing championships. Sonya is a regular blogger and founder at Nave.
Many product managers appreciate the benefits of Kanban, but don’t know how best to prioritize tasks. How do we han… https://t.co/Zi9tBiItL4Follow
High flow efficiency is vital to sustaining a scalable, productive business. Learn how you can calculate, analyze a… https://t.co/OysMenyLeRFollow
Two Kanban roles, Service Request Manager and Service Delivery Manager have emerged to equip teams with important d… https://t.co/X2zVYhq1oeFollow
To make your processes more efficient, first you need to identify where you are falling behind. Learn how to recogn… https://t.co/UbIDPd3tfwFollow
Are long cycle times holding your business back? By following these tips and integrating data-driven analytics into… https://t.co/Xgxmq6CU6PFollow
The main flow metrics in Kanban let you monitor your productivity and give you the information to make data-driven… https://t.co/ndLIyWqNqDFollow
Large teams and complex projects face a common issue – the Kanban board becomes cluttered and hard to read. Learn h… https://t.co/auLny9yNnEFollow
How did supermarket restocking techniques revolutionize project management? Learn the history of Kanban and how it… https://t.co/WZUw8z8UqwFollow
Optimizing workflow efficiency is often at the forefront of project managers’ minds, but eliminating idle time isn’… https://t.co/ZmEK020Yu0Follow
To improve workflows, first you must understand how to identify problem areas. Learn how to recognise the most comm… https://t.co/1cpIY9wVOJFollow
Wasteful activities that add no value to your business, also called Muda, can have a detrimental effect on your pro… https://t.co/RG5ZTG3raqFollow
Though it's easy to focus on less complex tasks first, neglecting work in progress can put your team at immense ris… https://t.co/wi4QFY03AjFollow
The Kanban Method focuses on making iterative, incremental changes to workflows to increase efficiency and producti… https://t.co/He4AtSVJXzFollow
Two Kanban roles, Service Request Manager and Service Delivery Manager have emerged to equip teams with important d… https://t.co/N6uQzpDQLhFollow
What makes the difference between an effective daily standup and one that just wastes your team’s time? Our short g… https://t.co/IJU8u5Let3Follow
Are you always short on time and on budget, even though your team is motivated and skilled? Learn how our team at N… https://t.co/f5PKT4gdq1Follow
In this infographic, we’ll be explaining how to identify bottlenecks and stabilize your workflow with the cumulativ… https://t.co/IyNAPj0C2UFollow
When making forecasts, it is impossible to escape uncertainty. Monte Carlo simulation uses permutation of numbers t… https://t.co/1yB4d3nIaXFollow
Lasting change happens in increments, over time. Learn how applying Kaizen principles brings continuous improvement… https://t.co/D6hRs2LfWmFollow