R&D Management 27 min read

How to Measure and Optimize Your Software Development Process with Key Metrics

This guide details a comprehensive set of software development metrics—including agile velocity, code quality, continuous integration, technical debt, unit and smoke testing, test automation, quality process, and continuous delivery—explaining their definitions, data sources, calculation methods, reference standards, and responsible platforms to help teams monitor and improve performance.

Software Development Quality
Software Development Quality
Software Development Quality
How to Measure and Optimize Your Software Development Process with Key Metrics

Agile Process

Story Completion Rate: Completion rate of story points in the most recent sprint (completed story points / initial story points * 100%). Data source: JIRA. Calculation details and sprint definition are provided.

Unplanned Stories: Ratio of story points added after sprint start to initial story points. Data source: JIRA.

Task Completion Rate: Ratio of completed sub‑tasks to total sub‑tasks in the current sprint. Data source: JIRA.

Backlog Volume: Sum of story points of unfinished stories not in an active sprint. Data source: JIRA. Calculation: sum(unfinished stories) * 3 (average 3 points per story).

Delivery Cycle: Average delivery time of stories in the most recent sprint (TPM acceptance time – story creation time, excluding holidays). Data source: JIRA.

Sprint Throughput: Total completed story points in the most recent sprint. Data source: JIRA.

Team Productivity: Throughput divided by (unique assignees * working days) for the most recent sprint. Data source: JIRA.

R&D Process – Coding

Total Code (KLOC): Sum of code lines across all pipelines. Data source: GIT.

Code Commits (last 2 weeks): Number of commits in the last 14 days. Data source: GIT.

Code Changes (KLOC, last 2 weeks): Additions + deletions in the last 14 days. Data source: GIT.

Continuous Integration

Integrated Pipelines: Total number of pipelines connected to DevOps.

Active Pipelines (last 2 weeks): Pipelines with build records in the last 14 days. Data source: DevOps.

CI Runs (last 2 weeks): Total number of continuous and manual builds in the last 14 days. Data source: DevOps.

Integration Success Rate (last 2 weeks): Successful builds / total builds in the last 14 days. Data source: DevOps.

Technical Debt

Technical Debt (days): Accumulated debt days for the latest Master branch build. Data source: DevOps.

Technical Debt Density (days/KLOC): Debt days divided by total code lines. Data source: DevOps.

Code Defect Count: Total defects from Sonar scans of the latest Master build. Data source: DevOps.

Code Vulnerability Count: Total vulnerabilities from Sonar scans of the latest Master build. Data source: DevOps.

Unit Testing

Overall Coverage: Weighted unit‑test coverage across front‑end, back‑end, and mobile pipelines. Target > 25%.

Mobile Coverage: Coverage for apk/ipa pipelines. Target unspecified.

Web Coverage: Coverage for H5 pipelines. Target > 25%.

Backend Coverage: Coverage for tomcat/boot/pom pipelines. Target > 25%.

Test Execution Count (last 2 weeks): Total unit‑test executions in the last 14 days. Data source: DevOps.

Test Case Count: Total unit‑test cases. Data source: DevOps.

Test Screening Result: Pass/Fail result of unit‑test screening. Data source: DevOps.

Smoke Testing

Total Cases (last 2 weeks): Number of smoke test cases executed via DevOps and JIRA.

Planned Executions (last 2 weeks): Number of planned smoke test runs via JIRA and DevOps.

Planned Overall Pass Rate (last 2 weeks): Passed plans / total plans.

Case Execution Count (last 2 weeks): Executed smoke test cases count.

Case Overall Pass Rate (last 2 weeks): Passed cases / total cases.

Test Metrics

Automated Test Case Count: Number of automated test cases created by test engineers. Data source: Quality Platform.

Automation Ratio: Automated cases / total test cases (JIRA). Data source: Quality Platform & JIRA.

Test Plan Execution Count: Number of automated test plan executions in the last 2 weeks. Data source: Quality Platform.

Automation Plan Pass Rate: Successful automated plan executions / total executions (last 2 weeks). Data source: Quality Platform.

Test Code Coverage: Coverage from the most recent completed test plan (Jira) as recorded in DevOps.

Quality Process

Jira Activity (last 2 weeks): Number of Jira operations (issues, tasks, bugs, test plans, etc.) performed. Data source: DevOps.

Legacy Defect Total: Number of unresolved defects older than 14 days (excluding closed/rejected). Data source: JIRA.

New Defect Total (last 2 weeks): Number of newly created defects in the last 14 days. Data source: JIRA.

Average Defect Fix Time (last 2 weeks): Average time from defect creation to closure, calculated in working hours (08:00‑20:00). Excludes rejected or postponed defects. Target < 2 days.

Defect Density: Defects per story point. Calculated differently for Agile and Waterfall projects. Target < 0.3 defects per KLOC for waterfall.

Mid‑Level+ Defect Ratio (last 2 weeks): Ratio of mid‑level and above defects to all new defects. Target < 60%.

Defect Reopen Rate (last 2 weeks): Reopened bugs / total bugs (including production). Target < 5%.

Defect Fix Rate: Closed defects / total defects. Data source: JIRA.

Continuous Delivery

SIT Delivery (last 2 weeks): Number of releases to SIT environment.

SIT Success Rate (last 2 weeks): Successful SIT releases / total SIT releases.

UAT Delivery (last 2 weeks): Number of releases to UAT environment.

UAT Success Rate (last 2 weeks): Successful UAT releases / total UAT releases.

PRE‑STD Delivery (last 2 weeks): Number of releases to PRE‑STD environment.

PRE‑STD Success Rate (last 2 weeks): Successful PRE‑STD releases / total PRE‑STD releases.

PROD Delivery (last 2 weeks): Number of releases to PROD environment.

PROD Success Rate (last 2 weeks): Successful PROD releases / total PROD releases.

Defect Escape Rate

Last 90 Days: Ratio of mid‑level+ production defects to total mid‑level+ defects (production + non‑production) over the past 90 days. Target < 5%.

All calculations are performed by the DevOps or Quality platforms as noted for each metric.

TestingDevOpscontinuous integrationagilesoftware metrics
Software Development Quality
Written by

Software Development Quality

Discussions on software development quality, R&D efficiency, high availability, technical quality, quality systems, assurance, architecture design, tool platforms, test development, continuous delivery, continuous testing, etc. Contact me with any article questions.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.