The Service level expectation graph displays the average time needed to complete items for the selected period.
It also displays the item's code and name, its type, cycle time, cycle time breakdown, and its delivery date. You can display this data by sprint or week, as you prefer. However, note that if a Kanban-type board has been linked to your Axify project, the "sprint" option will not be available in the filters at the top of the page.
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).
Reading the graph
For the following graph, the period displayed corresponds to the last three months, and the display mode is by week. On average, we can see that 85% (85th percentile) of the items are delivered in 7 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.
This graph also includes a variation indicator, which compares the average service level expectation for the current period to the average SLE for the previous period. To learn more about the variation indicator and its calculation, check out this article!
For example, for one week, we can see that an item had a cycle time close to 32 days, while 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.
Since this graph is interactive, hovering over an item with your mouse will display more details for that item.
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.
Calculating the metric
As soon as an item moves to an active status (usually the 2nd column of your board), its cycle time is compiled and the counter stops as soon as the item moves to a completed status (usually the last column of the board). The time spent at each stage of the development cycle is also calculated, allowing you to know the percentage of the total processing time allocated to each stage.