Measurement of durations : Metric definitions & SLAs

Abdellah TAHRI
Tera Contributor

For the measurement of durations , lead time (from the initiation of a work to it completion) or cycle time .
We have many solutions , but let’s focus on two solutions : Use of metric definitions & Use of SLA and Dashboard .

 

1 – Metric definition
Scripted metric definitions can be employed to effectively report on lead and cycle time for any type of tickets . As we are applying a script to make the calculation it’s possible to apply specific conditions .
To implement this, a scripted metric definition is created, specifying a script that calculates durations , lead time ... Once the metric definition is configured, it can be applied to dashboards and reports, providing insights. Indicators and widgets can be created to visualize lead and cycle time trends, facilitating data-driven decision-making .

 

Let’s take as an example , the User story , below the steps to follow :
1.Need to create Metric definition and schedule
•When creating metric definition need to consider sprint start date
•Schedule is complex to do for multiple region based on holiday
2.Need to create Database view table with metric definition- This Metric definition should contain sys id of custom created one
3.Need to create Indicator source with new data base view
4.Add script for the indicator source
5.Using indicator source and script, we need to create the indicator
6.Create a job to collect the data and add it to the indicator
7.Create a breakdown source
8.Create a breakdown and add a breakdown source(map)
9.Add indicator and breakdown to the widget
10.Add widget in the dashboard
11.Add breakdown source to the dashboard to show the story

 

2- Use of SLA with Schedule and Dashboard :
SLA definitions are used to create SLAs (Service Level Agreement) .

For the example above , let’s list the steps to follow:

1.Create SLA definition which should have the each state based on the story table
2.Create/ Use the schedule (schedule should be available on the platform level)
3.Create the database views using task_sla and rm_story table 
4.Create the dashboard
5.Create a Widget to show case the reports of the story state duration
6.Create widget to show the pivot table or heatmap
7.Create widget to show the bar table view

0 REPLIES 0