Skip to main content

Throughput Metrics

Measure development output and activity trends using commits, pull requests, and merge frequency.

author avatar
8 articles by 1 author

Code Changes Metric

Code Change Rate measures the pace of engineering output by tracking all code changes—new code, refactors, and rework—relative to time passed in an iteration, providing a true in-progress signal beyond task status alone.

Commits Metric

Track development activity and collaboration trends with the Commits Metric in LinearB, offering insights into commit frequency, team output, and workload distribution.

Deploy Frequency Metric

Deployment Frequency measures how often code is released to production, helping teams assess delivery velocity, confidence, and agility across services. Higher frequency indicates faster cycle times and stronger DevOps maturity.

Done Branches Metric

The Done Branches Metric tracks the number of branches merged where a contributor was involved, offering a clear signal of work completion and team momentum throughout a sprint or milestone.

Merge Frequency Metric

Definition. Merge Frequency measures the total number of pull requests (PRs) merged within the selected time range. It reflects how frequently code changes are successfully integrated into the main b…

PRs Opened Metric

Definition. PRs Opened measures the total number of pull requests (PRs) created during the selected time range. It reflects how many new code review workflows were initiated. This metric includes all…

Reviews Metric

The Reviews Metric tracks the total number of review actions taken on pull requests, offering insight into team collaboration, code quality practices, and individual contributions to the review process.

Throughput Metrics

Purpose. Throughput Metrics measure engineering output and activity volume. They help you understand how much work is flowing through the system over time (for example, commits, pull requests, review…

Contact