Workload & Effort Metrics
Workload & Effort Metrics provide visibility into how much work exists, how much work is completed, and how much effort is spent.
They focus on quantity and effort, helping teams understand capacity usage, workload distribution, and operational execution.
Unlike Time Metrics, which analyse flow and duration, these Metrics focus on how much work and effort is involved, not how work moves through the system.
What These Metrics Help You Understand
Workload & Effort Metrics are designed to help answer:
- How much work is planned or remaining?
- How much work was completed in a given period?
- How much effort was spent?
- Who contributed effort and where?
- How is work and effort distributed across teams, work items, or workflow stages?
Key Characteristics
Workload & Effort Metrics share the following characteristics:
Effort-Based, Not Flow-Based
These Metrics measure work and effort, not how smoothly work moves through the system.
They complement Time Metrics by focusing on volume and effort rather than duration.
Based on Actual Data
They rely on explicit data captured in the system, such as:
- Story points
- Estimates
- Logged work (worklogs)
Designed for Period Analysis
Workload & Effort Metrics are typically analysed over time periods such as sprints, weeks, or months.
This makes them suitable for planning, tracking, and reporting.
Attribution-Oriented
These Metrics help answer:
- Who did the work
- Where effort was spent
- How much effort was involved
They support accountability, ownership analysis, and workload balancing.
Metrics in this category
- Story Points Total — totals the story points associated with the work items in your report
- Story Points Remaining — totals the story points not yet completed at a specific point in time
- Story Points Completed — totals the story points delivered during a selected time period
- Original Estimate — totals the initially estimated effort for work items, from Jira's Original Estimate field
- Remaining Estimate — totals the estimated effort still required, from Jira's Remaining Estimate field