What is Average Days to Resolve Stories ?

The average days to resolve KPI is the average number of days it takes for a new story to be resolved.

How to calculate Average Days to Resolve Stories?

Step 1: ‘Add a new Days Between Dates’ JIRA metric and click ‘Save.’

What does the JQL query mean?
This JQL query specifies the project and selects all the stories that have been assigned a resolution date between the start and end of the day. If a story doesn’t have a resolution date then it will not have been resolved there we will not want to select it.
Tip: The Days Between Dates metric also allows you to select a start and end date for the time period you want to select the stories for.  

Step 2: Select ‘Convert to KPI’, add a new KPI and click ‘Save.’

Step 3: Add the ‘Closed Stories’ metric to the KPI.

Visualisation Examples:

Below are a couple of examples of how you might visualise the Average Days to Resolve Stories KPI.

 

Pros:

The Average Days to resolve stories KPI helps to measure human effort to show how efficient your team is getting tickets through the system, whether they are being worked on, blocked etc.
This insight will better equip you for delivery planning so that you can maximise productivity for each new release.

Cons:

If you have a process in place that is not correctly managed, then this KPI is not going to show you a true reflection of how efficient your team is. Ensuring that there is a process in place will ensure you have an accurate picture of what to expect.

Relevant software project management KPIs:

If you are adding the Average Days to Resolve Stories KPI to your software project management report, you may also want to consider tracking these other KPIs:

  • Time Spent in Dev/QA
  • Estimates Vs Actual
  • In Progress Stories
  • Completed Stories
  • Stories Passed Due Date
  • Time Spent in Development/QA

Need KPI Reports to get you started? Check out our proof of value program here

Did this answer your question?