Balance & Activity Metrics

Purpose

Balance & Activity Metrics measure workload distribution, contributor engagement patterns, and branch concurrency across teams. They help identify whether work is steady or bursty, parallel or concentrated, and how development activity is distributed over time.

These metrics focus on behavioral patterns rather than output volume or delivery speed.

Metrics Included

The following metrics belong to the Balance & Activity family:

• Active Days
• Active Branches
• Done Branches

Each metric definition, calculation formula, normalization logic, and display behavior is documented in the Metrics Glossary.

How These Metrics Work Together

Balance & Activity metrics describe contribution patterns from complementary perspectives:

• Active Days measures how consistently contributors perform Git activity over time.
• Active Branches measures how many branches are concurrently in progress, indicating parallel work streams.
• Done Branches measures how many branches were completed (merged), reflecting branch-level completion activity.

Used together, these metrics distinguish between high concurrency vs low concurrency workflows, steady vs bursty contribution patterns, and concentrated vs distributed branch activity.

Dashboards That Use Balance & Activity Metrics

Balance & Activity metrics appear in:

• Developer Experience Dashboard

These views are often used alongside Throughput and Quality metrics to provide context on contribution patterns.

Related Metric Families

Balance & Activity metrics often correlate with:

• Throughput Metrics (output volume vs. how consistently work occurs)
• Quality Metrics (bursty delivery may correlate with higher rework or reduced review rigor)
• Delivery Metrics (irregular activity patterns can influence PR lifecycle timing)

Configuration Dependencies

Balance & Activity metrics rely on:

• Git activity ingestion (commits, PRs, reviews)
• Accurate attribution of activity to users and teams
• Branch state tracking

Troubleshooting

If Balance & Activity metrics appear inconsistent:

• Confirm Git activity exists during the selected time range.
• Validate team and user mapping is correct for the selected scope.
• Ensure repositories are connected and syncing normally.

For detailed troubleshooting guidance, see: Troubleshooting.