Our top 14 Software Quality KPIs

Posted by
Conor Graham Oct 3, 2018 3:58:20 PM

At ServiceClarity we believe that in order to be truly effective in monitoring and tracking development processes, every organisation requires KPIs that are custom to their data.  This allows them to completely optimise their processes while ensuring that they have accurate reports to empower how they make decisions.

However, it can be really difficult coming up with KPIs.  So we decided to put together a list of 14 Development KPIs that you should be implementing in to your engineering processes.

1. Active Stories

Description: The number of unfinished, new or in progress stories in the project on any given date. 

Insight: This is the no. of stories that are yet to be completed.

2. Average Story Size (Story Points)

Description: Average no. of story points per story in progress on any given date.  

Insight: 50% organisations don’t have everything estimated so it’s difficult for a project manager to get an answer to how much work they have to do. This KPI uses past estimates to get an idea of the typical(average) estimate and then converts the backlog into an estimate of estimates.

3. Estimated Story Point Backlog 

Description: Using the average story size and the number of outstanding stories currently without estimates calculate an estimate of the total number of outstanding work in terms of story points.

Insight: This will provide you with another method to estimate the backlog using story points.

4. In Progress Estimates

Description: The total time estimated (in man days) for all in progress or in review stories on a given date.

Insight: This KPI will provide an estimate of how long it will take for the stories that are in progress to hit done in man days.

5. In Progress Stories

Description: The number of stories in progress, or in review, on a given date.

Insight: This is the current work in progress (throughput) in no. of stories. 

6. In Progress Story Points

Description: The total number of story points in progress or awaiting review on a given date.

Insight: This provides the work in progress in story points

7. Average Story Estimates (Hours)

Description: The average number of estimated hours per story in progress on any given date.

Insight: Another method for helping to estimate. This really is the amount of work in progress in hours. 

8. Assigned Stories

Particular Project (stories)
Description: The number of unfinished, new or in progress, Stories in the Platform project, that have been assigned to someone, on any given date. 

Insight: This is the no. of unfinished stories that have been assigned but not completed.

9. Story Estimates Vs Actuals (%)

Description: The percentage difference of estimated time vs recorded time spent of stories closed on a given date. 

Insight: Are you under-estimating or over-estimating?

10. Rejected Stories

Description: The count of stories completed as "Invalid" on a given date.

Insight: What % of stories are being rejected? Also determines if you have a high reject ratio.

11. Completed Stories

Description: The count of stories completed as "Done" on a given date.

Insight: How many stories have been completed?

12. Estimated Backlog (Days)

Description: Using the average estimated size (in hours) and the number of outstanding stories currently without estimates calculate an estimate of the total number of outstanding work in man days.

Insight: This uses past trends to calculate an estimation of your backlog in days.

13.Completed Time Spent 

Description: The total time (in hours) recorded as "spent" on stories closed on a given date.

Insight: Time Spent is the ACTUAL time recorded by the assignee i.e how long they say that the spent on the completed tasks. This can be a good guide to assisting with billing, costs and tracking budget.

14. Stories Passed Due Date

Description: The number of stories that were still in an active state, In Progress or In Review, after their due date had passed. 

Insight: How many stories did not meet their due date for this particular project?

Get a sample software quality report, custom to your data, and start tracking your KPIs making sure your software is always delivered at high quality: View Report

Topics: DevOps Reporting, KPI Reporting, JIRA, Time Tracking, DevOps

Subscribe to Email Updates