JiraIssue TrackingTeam Capacity Utilisation
Team Capacity Utilisation measures the proportion of available team capacity that is actively allocated to Jira issues. It compares assigned workload against available capacity, accounting for team member availability, leave, and non-project commitments.
Jira metric
Capacity Utilisation = (Allocated Story Points / Available Capacity) × 100
Team Capacity Utilisation measures the proportion of available team capacity that is actively allocated to Jira issues. It compares assigned workload against available capacity, accounting for team member availability, leave, and non-project commitments.
Full guide: definition, formula, and benchmarksHow to calculate Team Capacity Utilisation
Capacity Utilisation = (Allocated Story Points / Available Capacity) × 100
Why Team Capacity Utilisation matters for Jira users
Understanding how team capacity is distributed across work types, such as features, bugs, and technical debt, reveals whether investment is aligned with strategic priorities. It also ensures teams are neither overloaded nor underutilised.
For Jira teams, capacity utilisation data supports evidence-based conversations about resourcing. It helps managers identify teams with spare capacity for new initiatives and teams that need relief before they burn out.
Driver
Conversion rate
Outcome · 58% contribution
Revenue
Understand and act on Team Capacity Utilisation with KPI Tree
KPI Tree calculates capacity utilisation from Jira sprint and workload data in your warehouse. Place this in your resource management tree alongside velocity and cross-team dependency metrics.
Assign RACI ownership to engineering managers for capacity balance. Set alerts for utilisation rates that fall outside the optimal 70-85% range.
Get started with your Jira data
MCPPull metrics from Jira directly through the Model Context Protocol.
Connect your existing warehouse where Jira data already lands.
Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.
Related Jira metrics Ready to add to your trees.
Sprint Velocity
Issue TrackingSprint Velocity = Total Story Points Completed per Sprint
Sprint Velocity measures the total story points or issue count completed by a team in each Jira sprint. It provides a rolling baseline of team capacity that is used for forecasting future delivery and calibrating sprint commitments.
View metricCross-Team Dependency Analysis
Issue TrackingCross-Team Dependency Analysis maps the network of issue links, blockers, and handoffs between different Jira projects and teams. It quantifies how often teams depend on each other and measures the impact of those dependencies on delivery timelines.
View metricCode Review Cycle Time
Issue TrackingCode Review Cycle Time = Review Completion Date − Review Start Date
Code Review Cycle Time measures the elapsed time between when a Jira issue enters a code review state and when it exits, either approved or requiring changes. It captures the efficiency of the review process as reflected in Jira workflow transitions.
View metricUser Productivity Analysis
Issue TrackingUser Productivity Analysis examines individual contributor patterns in Jira, including throughput, cycle time, issue type distribution, and work consistency. It identifies productivity trends and factors that influence individual effectiveness, supporting coaching and team optimisation.
View metricExplore Team Capacity Utilisation across integrations
All Jira metrics
Backlog Health AnalysisBlocked Time PercentageCode Review Cycle TimeComponent Quality TrendsCross-Team Dependency AnalysisCycle TimeDefect DensityEpic Progress TrackingEscalation Pattern AnalysisFlow EfficiencyIssue Age DistributionIssue Resolution RateLead TimePriority Distribution AnalysisRelease Burnup AnalysisSprint Burndown AnalysisSprint Commitment AccuracySprint Goal Achievement RateSprint VelocityStory Point Estimation AccuracyTeam Collaboration IndexTechnical Debt RatioUser Productivity AnalysisVersion Release Success RateWorklog AccuracyEmpower your team to understand and act on Jira data
Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.
