Cycle Time Scatterplot
The analytics in Kanbanize work per board. Click the Analytics icon on the top of each board to access the Analytics page.
The Analytics screen presents 5 categories: Cycle Time, Throughput, WIP, Flow, Forecasting, each available as a tab item on the page. Click on a tab button to view the charts for each of the respective metrics. The Scatter plot belongs to the Cycle time category.
Notes: Before start using the analytics make sure that you have configured the Cycle time tracking for the respective board. You can choose which columns from your workflow to be included in the analytics as well as for the calculation of the card "cycle time".
To learn how to configure cycle time per board, please check the dedicated article.
Note: If you checkmark the "Ignore Cycle time" configuration, the system ignores the current Cycle time configuration.
Respectively, the selected Analytics module accounts and visualizes the time cards spend in each of the process stages. This allows having an in-depth analysis of both value-adding activities and“queues”, when it is necessary.
You can checkmark this option only if a single workflow is selected.
Introduction to Scatter plot:
The cycle time Scatterplot chart is a representation of how long it takes to get things done for individual items on your Kanban board. It visualizes the work items that have been completed on a given board (inside single or multiple workflows).
The chart visualizes the cycle time of tasks within a predetermined time frame. It also gives information when the cards' completion in the selected workflow can be expected. The certainty of this is measured with percentiles.
To learn more about the scatter plot concept, please visit our blog.
How to set up the scatter plot?
From the left side of the panel, you can control which data you can see on the chart within a predetermined time frame.
First, you define the timeframe ("Requested After" date and "Finished Before" date).
Important: The chart will visualize only cards that have entered your flow after the "requested date" that you define. In case that the cards were in your flow before the requested date and are completed within the "finished before" date, they won't be displayed.
Then you select the workflows that you want to analyze using the Scatterplot.
The graph takes into consideration all cards from the selected workflows. Note that you can add single or multiple workflows.
In addition, you can apply extra filters (Add cards filter). For example, you may want to see only cards with high priority or cards that are of a certain type.
How does this chart work?
Across the "x" axis is a representation of time i.e. Completion date. You can see the dates across the button of the chart.
On the "y" axis is the Cycle time in days.
Every time when an item is completed, the system plots a dot on the vertical against the date of completion and where it goes depends on the cycle time. For example: on April 24th, an item was completed and it took 9 days to get done.
A lot of the dots have small numbers inside. It means that the same number of items have been finished on that day. On hover, you can see the card IDs.
Important:
The analytics use one calendar day as the lowest possible time unit.
For example:
The card was created 30 minutes ago and was moved to "In progress". The system shows 1 day for this card. The card was created late yesterday at 23:00 P.M. and you take a look at the chart in the morning at 9:00 A.M. (i.e. around 10 hours after the creation). The system will show 2 days as the card has been created yesterday and is still being worked on Today.
The Calendar time unit is used for analytics due to the fact that most of the modern Kanban systems are driven by client requests. As such, clients expect exact delivery dates or ranges that are calendar-based. They do not care about holidays, working hours, man-days, cycle, and lead times.
That being said, the Cycle Time Scatterplot allows for recalculation based on working days.
Note: the X axis (where applicable) would still display all calendar days/weeks.
The selection of working days recalculates the cycle time for all cards shown in the graph, but they do not change their position in time. Let's say we have a card that was moved to ‘In Progress’ on a Wednesday e.g. 06.01.2021 and was completed on Saturday 09.01.2021 and the team is working from Monday to Friday.
If no working days option is selected, the card's cycle time would be calculated as 4 days.
If the working days (Mon-Fri) option is selected, that card's cycle time will be recalculated from 4 days to 3, but the point for it on the Cycle Time Scatterplot would still remain on the line corresponding to the date it was completed on (09.01.2021).
In case that you need precise cycle and log times for internal reporting, use the Advanced search capabilities with the different charts views and widgets.
Hover on the Card ID to open the respective "Work Item Details" box. It contains specific information relevant to the card. In addition, you can check the time this card has spent in every stage of the workflow.
Besides showing you some visual representation of how work actually happens inside the board, this chart is important for one other reason.
It provides a probabilistic view that is activated via the percentiles (50%, 70%, 85%, 90%), which you control from the Chart Controls. Select the percentiles for the corresponding control.
If you go all the way to the left following the horizontal lines, you will see a number for each of those lines.
- 95% -> 11 days
- 85% -> 6 days
- 70% -> 3 days
- 50% -> 2 days
What's that telling us?
Let's start with the 50% percentile. If you draw a horizontal line all across the chart, it will cut the dots in half - 50% of the dots will be below the line and 50% of them will be above the line.
The chart is telling us that 50 % of those items took 2 days or less to be completed. An alternative assumption might be that when an item enters our process, it has a 50% chance to be completed in 2 days or even less.
Imagine that you get a new request coming into this workflow. You naturally ask the question: How much time I need to get this done? Then you can instantly say that there is 95 % probability that your team will complete the work items within 11 days as long as its something like what you used to do here.
If it is not something radically new, then 11 days will be more than certain to be sufficient.
This chart allows you to forecast work on an individual work item level.
You can calculate the rest of the percentiles in the same way. These percentiles are important because they show us how much risk we are willing to take. If we are fine being wrong 50% of the time, we will say that 2 days are needed to complete any card on this workflow.
If we prefer to stay on the safe side and be more accurate in our forecast, then we will interpret the process using the 85% or 95% percentile, which gives a higher level of certainty.
Practical Tips:
- Keep the dots as close to the "x" axis as possible, because that's how you decrease cycle time and deliver faster.
- Pay attention if the dots tend to grow on the right. If they do, it means that your cycle time is going up and you are getting slower over time. Investigate the causes behind delayed tasks and take some actions to introduce process improvements.
- You can mark the cards that have been blocked using the "Blocked items" control to the right of the chart. You can toggle on and off which cards have been blocked. It is a good visual indicator, which gives you an idea of how many cards have been blocked.
