Decrease back-and-forth

Decreasing the number of cycles in a workflow by setting KPI which tracks the number of times an issue gets returned in a certain status.

There are a number of KPIs that may be created using same technique:

  • ‘Reopen iterations’ for QA team, the one that verified the issue.
  • ‘Code Review Iterations’ for Dev team to improve quality of code.
  • ‘Testing Iterations’ for QA and Dev team to improve attention to detail on each level of a certain feature verification.
  • ‘In Progress Iterations’ for Project manager, Product owner that will improve quality/detail of the requirements.

Here is an example goal definition: Max 20% of total issues to exceed 1 “Reopen iterations”. The KPI will help to decrease the number of not well verified Stories or Defects by the QA team.

Please check the KPI configuration steps below:

Step 1: Define 2 data sources. One with the All issues and the other that contains only the one with more than one reopen iterations. If you don’t have such field please check the following article how to easily add it.

Step 2: Select the data source from which will be calculated the metric value ‘Number of issues’.

Step 3: Set Display By to ‘Tested By’. If you don’t have such a field you may refer again the article mentioned above.

Step 4: (Option) Set Stacked by to ‘Tested By’ to make the chart colorful.

Step 5: Switch-on Target section and select tab ‘% of Total’.

Step 6: Select target results to be evaluated per x-axis item. In the case above is used the user in field ‘Tested by’.

Step 7: Select the data source for the target metric value calculation.

Step 8: Set target level value.

Step 9: Set target as negative. When ‘Exceeding is’: Bad the results achieved above the target are considered negative.

Step 10: Under ‘More Settings’ section enable ‘Warning threshold’.

Step 11: Under ‘More Settings’ section switch on ‘Custom Target Label’ and set it with alias which indicates on the chart that the target is negative.

Recording: Please check the following recording with the detailed configuration settings:

Check this 3 min recording here on how to config your JIRA to capture KPIs based on:

  • users such as ‘Tested by’, ‘Developed by’, ‘Reopened by’, ‘Reviewed By’
  • dates such as ‘Testing Started’, ‘Development Started’ etc.
  • counters such as ‘Testing Iterations’, ‘Reopen iterations’, ‘Review Iterations’ , etc…