I want to know as a scrum master which Jira metrics do you actually use to understand sprint health?

[Akankshya Mishra]

There are plenty of metrics available in Jira, but I’m curious about which ones Scrum Masters genuinely find useful.

If you had to choose only 5 metrics to put on a Scrum Master dashboard, what would they be and why?

Some examples I’ve come across are:

• Burndown/burnup
• Velocity
• Cycle time
• Lead time
• WIP
• Carryover
• Scope changes
• Blocked issues
• Workload distribution
• Bug ratio

Which metrics on this list do you not recommend using, and which important ones are missing?

I’m especially interested in metrics that help you make a decision or take action, rather than metrics that simply look good on a dashboard.

[Viswanathan Ramachandran]

Hi @Akankshya Mishra 

The 5 Metrics That Drive Action:

1. Work Item Age (Active WIP Aging): Shows how long active work is stuck right now.

   • Action: Swarm on aging items in daily stand-ups before the sprint fails.

2. Flow Efficiency (Active Time vs. Waiting Time): Exposes handoffs, queues, and dependencies.

   • Action: Fix system bottlenecks instead of telling devs to "code faster."

3. Blocked Time (Categorised by Root Cause): Quantifies systemic organisational drag.

   • Action: Use hard data to negotiate dependency SLAs and clear external blockers.

4. Planned vs. Delivered Ratio: Measures team predictability, not raw output.

   • Action: If <80%, reduce sprint loading or fix backlog refinement.

5. Escaped Defect Rate: Balances speed with quality.

   • Action: A spike signals rushed testing; pause feature push to tackle tech debt.

Skip These (Vanity / Counterproductive):

• Velocity: Easily gamed, causes story-point inflation, useless for cross-team comparisons.

• Burndown: Shows that you're late, but never why.

• Internal Bug Ratio: Penalises logging bugs, leading teams to hide technical debt.

Re: Work Item Age  - Stop looking backward at completed Cycle Time and start fixing aging work today.

• Work Item Age is simply the total elapsed time between when an active item started (moved to "In Progress") and today. Think of it as Cycle Time for work that isn't finished yet. 
• ex: If a story moved to "In Progress" on Monday and today is Thursday, its age is 4 days.

[Anastasiia Maliei SaaSJet]

On your point about “metrics that actually help me decide something” — I’d add Sprint Performance as a useful example.

In our Sprint Performance Report from the Time in Status app by SaaSJet, we focus less on a single final score and more on the signals that help explain why a sprint went the way it did:

• Committed vs. Completed — by Story Points, Work Item Count, or Original Time, depending on the board’s estimation method.
• Completion rate — including cases where it goes above 100% because additional work was added and completed during the sprint.
• Carryover / spillover — what wasn’t finished and moved to the next sprint.
• Scope changes — what was added or removed mid-sprint, which can otherwise make velocity look misleading.
• Workload by assignee — committed, added, and removed work can help reveal uneven workload or scope being redirected.
• Status time, flagged items, and logged time — useful for finding the reasons behind the numbers: work stuck in review/testing, too much WIP, blocked items, etc.

For the top chart, you can switch between Burndown and Team Velocity. I find velocity particularly useful for calibrating future commitments, while burndown helps understand the pace during the sprint.

Another useful part is that the report works with active sprints, so you can use it during the sprint rather than only looking back after it’s finished.

[Eduardo Anflor - MindPro]

Hi, @Akankshya Mishra 

It really depends on the process your company follows and the reporting needs managers have. For example, the most common metrics customers request from us are related to progress and volume. Charts like Velocity, Epic/Sprint Progress, cycle time, and Throughput are used to deliver this information.

 If you are open to a marketplace solution, I recommend Mindpro Insights. I work at Mindpro, and I believe the app can help with your use case.

It allows any user to easily create dashboards with 50+ gadgets you can choose from. The gadgets are interactive, which means that when you click on any chart segment, the entire dashboard adapts to your filter. You can also share these dashboards internally or with external users via the customer portal.

Some examples:

Lead/Cycle time, Throughput:

Epic Progress and Story points gauge:

 

Velocity, Sprint progress, and board filter:

I hope that helps.

Regards,

Eduardo