The Service level expectation graph displays the average time needed to complete items, week by week, for the selected period.
It also displays the item's code and name, cycle time, and delivery date. Again, you can display this data by sprint or week, as you prefer.
Psst! Be careful not to confuse this graph with the one of the same name available in the Technical Axis since they do not use the same data (different sources for the two axes).
Example of use
For the following graph, the period displayed corresponds to the last three months, and the display mode is by sprint. Overall, on average, we can see that 85% (85th percentile) of the items are delivered in 6 days or less. However, we can also see that some items took longer to be delivered.
A purple dotted line indicates the 85th percentile mentioned above. This is the measure used to calculate the average delivery time per item.
For example, for one week, we can see that an item had a cycle time of 24 days. Since this graph is interactive, hovering over an item with your mouse will display more details for that item.
Other items show a much shorter cycle time, indicating a delivery time closer to the average cycle time visible in the Cycle time breakdown graph.
This may reflect a more complex task or a longer-than-average wait time for feedback.
Psst! This graph is a great way to analyze anomalies and identify potential blockers in your workflow. By displaying the code and name of the item, you will be able to inspect its history at the source to understand what has prolonged the processing time and avoid the situation from happening again.
To learn more about the variation indicator and its calculation, check out this article!