What to Measure and Why: Metrics in Kanban
You might have heard the saying “what gets measured gets managed”. Monitoring progress and measuring performance is a key component of the Kanban Method – both for tracking your project and making your process more efficient over time.
Here we will explain the specific metrics & analytics in Kanban that you should be using to monitor your team performance and your process efficiency and delivery times, as well as the red flags to watch for that signal trouble ahead.
Average Cycle Times
Cycle time measures how much time a task spends going through your process. Cycle time differs from lead time in that it is only measured from when your team starts working on the task.
Cycle time, then, is the metric that directly measures how long it takes your team to deliver a task. Low cycle times means your team is working efficiently, high cycle times indicate that something is stalling your process. Keeping average cycle time down keeps your lead times down, and keeps your customers satisfied.
You can see how your cycle times evolve over time using a cycle time histogram and use them to predict future work delivery times. In the plot below we can see from the percentile lines that once your team starts working on a task it has a 50% chance of being completed in 7 days and a 95% chance of being completed in 45 days.
Whereas cycle time measures how long it takes an individual task to go through your process, the throughput metric measures the total amount of work delivered in a certain time period. Throughput only measures completed work items – nothing that is still in progress gets counted.
The reason throughput is such a handy metric in Kanban is that it can be used to accurately forecast how much work your team is able to deliver going forward. Consider a Kanban team whose throughput for each of the past 5 weeks was 3, 7, 4, 5, and 6, giving an average throughput of 5 tasks per week. Without knowing anything about the tasks themselves, we can estimate that this team will keep delivering approximately the same amount of work – 5 tasks – every week.
Throughput over time is used to track your team performance and is measured using the throughput histogram. This maps how frequently your team achieves a certain throughput over a period of time. From the chart below, we can see this team has a median output of 4 items per day over this month.
By tracking your throughput over time, you can directly see how your team’s overall performance is changing. Ideally, throughput should stay the same or increase – a decreasing throughput indicates that something is negatively affecting your team’s ability to deliver and needs additional attention.
Work In Progress
A key component of the Kanban Method is limiting Work In Progress (WIP) to improve your team’s efficiency. Think about it – do you get work faster when you split your attention between many tasks, or when you choose one to focus on?
The optimum WIP limit for your team will depend on several factors such as the size of your team, however a good place to start is setting the limit at around the number of people in your team – this way, everyone can focus on one task at a time.
The two metrics in Kanban which best measure your team performance are cycle times (how fast work gets done) and throughput (how much work is delivered). These metrics are the ones to watch to make sure you are delivering results to your customers!
Cycle time, throughput and WIP are connected by Little’s Law. This formula applies to any system which meets Little’s Law assumptions.
Cycle Time = WIP/Throughput
Little’s Law shows the relationship between the three basic flow metrics, and that changing one will have an effect on the other two. For example, for a reduction in cycle time, WIP must decrease.
Short cycle times and high levels of throughput are signs of good team performance, but another thing to look out for is consistency. From the cycle time histogram and throughput histogram, you can not only see the average value of these metrics but also how this data is distributed over a period of time. When your values are spread over a smaller range, your future predictions are naturally more accurate.
Cumulative Flow Diagram
The Kanban Method primarily deals with incremental improvements in efficiency. It is most powerful when applied over longer periods of time. We’ve already discussed how cycle time and throughput are tracked over time, however, the real star for examining process efficiency on a longer timescale is the cumulative flow diagram.
The cumulative flow diagram shows the distribution of tasks in each of the process states, accumulating over time. Each coloured band indicates how many tasks are present in each state of the process at a given time. Cycle time and lead time can be calculated straight from the diagram, but the real benefit of the CFD is how quickly you can get a visual assessment of the stability of your process.
Changes in your team performance can be seen at a glance from how the gradients of the bands change over time. An increase in gradient for the “Done” band means your team is delivering work faster. On the other hand, a sharp increase in the gradient of the “In Progress” band indicates a bottleneck is beginning to develop.
WE UNCOVER THE EFFICIENCY OF YOUR WORKFLOW
Optimise your performance with Kanban analyticsExplore Your Data Now
The biggest red flag that your performance is about to suffer is the bottleneck – increasing backlog or work in progress that is not being completed. The bottleneck signals that your team does not have the resource capacity to handle the amount of work assigned to them in a timely manner.
Using metrics & analytics in Kanban you can spot bottlenecks as they occur: signs to watch out for increasing cycle times, decreasing throughput and sharp increase in gradient in your cumulative flow diagram.
When you begin to see signs of a bottleneck, it’s time to take a close look at why this could be occurring – is an external requirement causing items to get stalled? Has your work in progress limit crept up without you realising? Do changes in the roles of your team mean tasks should be assigned differently? By taking action quickly, you should be able to eliminate bottlenecks before they become a problem.
What metrics & analytics do you use to track your team performance? What was the most important insight you learnt from your data and how did you act on it? Tell us about your experience in the comments!
Meet the Author
Sonya Siderova is a passionate product manager and a driving force behind Nave, a Kanban analytics suite that helps teams become more efficient through data-driven decision making. When she's not catering to her two little ones, you might find Sonya absorbed in a good heavyweight boxing match or behind a screen crafting a new blog post.
A Big Thank You from Nave!
The Cycle Time Histogram for Trello shows the overall distribution of the completion times of the tasks in your pro… https://t.co/sVpW5si6qAFollow
In Kanban, throughput is one of the key measures of flow efficiency. Learn how to track your workflow performance o… https://t.co/I3nrBKlLrRFollow
Nave’s range of Kanban analytics helps you spot performance trends at a glance. Select your platform and improve yo… https://t.co/B7AFPCmi3LFollow
Effective changes are built upon data. In this article we’ll take a look at how you can use Kanban analytics to und… https://t.co/sOkemEJmCuFollow
Measure and improve your delivery performance with our advanced Kanban analytics for Asana projects. See a dashboar… https://t.co/aS9s3asn1tFollow
Are you ready to recap the benefits Kanban analytics can bring to your workflows? Choose your platform, and get sta… https://t.co/r2MHJRo9wWFollow
What would the perfect company be like and how to improve people commitment within an organization.… https://t.co/irMK4TYfRCFollow
Immersive charts for your Jira projects. Get more done, faster, with Nave analytics on Jira. Start your free 14-day… https://t.co/8x6cRaMPA3Follow
Prioritization in Kanban backlog revolves around your customer value and business needs. Find out how to grow as a… https://t.co/2x8R5wF7q9Follow
Rely on data, not instincts. Nave Power-Up for Trello builds immersive analytical charts over your Trello boards. T… https://t.co/bz3R5X2a0SFollow
Try our advanced Kanban analytics suite for free on your favorite tool and start leveraging the power of data-drive… https://t.co/e3sQfTPlpAFollow
Everyone wants to run their projects more effectively. That’s where Kanban comes in – the Japanese system that revo… https://t.co/pOPywTYnPZFollow
When we adopt Kanban, we want to achieve shorter lead time, higher delivery rate and better flow efficiency. How do… https://t.co/ApzaYG3wXBFollow
Are you ready to recap the benefits Kanban analytics can bring to your process? Get started with Nave today!… https://t.co/Wns13SVyK9Follow
To make your processes more efficient, first you need to identify where you are falling behind. Learn how to recogn… https://t.co/pgaqhrJQ2ZFollow
Take your training and consultancy sessions to a whole new level. With Kanban analytics on their existing tools, yo… https://t.co/a8OUJtkhg8Follow
There are three ways in which leaders can influence culture: how they make decisions, how they communicate, and the… https://t.co/FbOGIYNoCzFollow