Monitor your cycle time distribution. Predict issue delivery times. Track your delivery performance.
The Cycle Time Histogram for Jira displays the cycle time frequency distribution of the completed issues in your workflow. The vertical axis displays a frequency, while the horizontal axis shows your cycle times. By monitoring the distribution of your cycle times, you can evaluate the variability in your process.
A Cycle Time Histogram that displays a big hump on the left, alongside a significantly long tail to the right, is indicative of an unpredictable, highly varying cycle time. This denotes that your process is inconsistent. To work towards more predictability for your delivery times, consider establishing a WIP-limited pull system.
The Cycle Time Histogram for Jira uses historical cycle time data to forecast dependable delivery times. Percentile lines show the probability that your team will complete an issue within certain cycle time. The higher the percentile line, the higher the likelihood of delivering your work on time.
Use the percentile lines to define your service level agreements. Firstly, discuss the different levels of confidence with your clients and stakeholders, then define your SLAs in accordance with their optimum comfort level. We would recommend using the 85th percentile line, at least to begin with.
Your average cycle time is an indicator of your team’s performance. In the Cycle Time Histogram for Jira, we provide the mean, median and mode average of your cycle times, alongside line charts of how these trends build over time. Ideally, the lines should stay close together, and either remain at an even rate or go down in sync.
Select your average and track its line profile! If the line goes up, this means that your team needs more time to complete their issues. If this is the case, you might need to reevaluate your WIP limits or set about altering your process policies in order to establish a faster delivery workflow.