1. Introduction to the Analytics in Kanbanize
The Analytics module helps you identify bottlenecks and provides predictability of your workflow so that you can make better data-driven decisions. Analytics can be used to run reports on the working process and provide a visual representation of the data on the selected board.
Important: The analytics in Kanbanize work per board.
2. Types of charts/graphs within the Analytics module
The Analytics screen presents 7 categories: Cycle Time, Throughput, WIP, Flow, Blockers, Forecasting, Deprecated Analytics, each available as a tab item on the page. Click on a tab button to view the charts for each of the respective metrics.
Cycle Time Analytics
Cycle Time 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.
Cycle Time Histogram - The Cycle time histogram is similar to the Cycle time Scatterplot, but it visualizes the data differently. The Cycle time histogram aggregates the data and gives you the cycle time-frequency distribution of the completed cards in your workflow.
Cycle Time Heatmap - The Cycle Time Heatmap is a graphical representation of cycle time on a matrix that uses various shades of different colors to help distinguish the collected data in each cell of the matrix.
Throughput Histogram - The Throughput histogram aggregates the data and gives you the distribution frequency of Throughput on the selected workflow. It visualizes how productive your team was. This is measured by the number of tasks finished each day for the defined time frame.
Throughput Run Chart - The Throughput Run Chart in Kanbanize helps you visualize how much work you can deliver every day. The chart displays the data plotted over time, and it helps find trends or patterns in your process.
WIP Run Chart - The WIP Run Chart helps you visualize how much work in progress your team has over a selected time in the selected workflow. The chart displays data plotted over time, and it helps find trends or patterns in the process.
Cumulative Flow Diagram - The Cumulative Flow Diagram aims to show the stability of your process over time. It tracks and accumulates each task that has ever entered or progressed to any stage of your workflow.
Flow Efficiency - The Flow Efficiency chart will automatically gather data from every card that passed through your Kanban board during the time frame of your choice to accumulate the overall flow efficiency for the period.
Blocker Clustering - The Blocker Clustering Chart is a graphical representation of the time and number of times cards have been blocked. It is a heatmap that uses various shades of different colors to help visualize the collected blocker data.
Monte Carlo How Many - The "How Many" Monte Carlo simulation aims to tell you the minimum amount of work items that you can get done within the next “x” days. For example, you can use it if you’ve got a deadline scheduled for July 7th and you wish to know how many tasks can be finished by then.
Monte Carlo When - The "Monte Carlo - When" simulation is the other way around compared to "Monte Carlo- How Many." The "Monte Carlo - When" chart aims to tell you when you can expect the team to finish a specific number of tasks that you are yet to start working on.
3. Analytics - Tips and Disclaimers
Note: Before using the analytics, make sure that you have configured the Cycle time calculation for the respective board.
To learn how to configure cycle time per board, please check the dedicated article.
* 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.
Important: The analytics use one calendar day as the lowest possible time unit.
The card was created 30 minutes ago and was moved to "In progress." The system will show 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.