> ## Documentation Index > Fetch the complete documentation index at: https://docs.heygarth.ai/llms.txt > Use this file to discover all available pages before exploring further. # Jira metrics ## Overview The Jira Metrics Dashboard provides visibility into sprint execution, delivery performance, work-in-progress management, and team predictability. It helps engineering managers, scrum masters, and delivery leaders monitor sprint health, identify bottlenecks, and ensure consistent delivery outcomes. The dashboard is designed to provide actionable insights into sprint progress, team velocity, workflow efficiency, and delivery reliability across Jira-managed projects. ## Sprint Health Metrics ### What is it? A summary section displaying key indicators that measure sprint health, delivery performance, and workflow efficiency. ### Why is it important? Provides a quick overview of team performance and highlights potential risks that may impact sprint delivery. ### Where does it exist? Top section of the Jira Metrics Dashboard. ### Metrics Included **Aging WIP** Displays the number of work items that have remained in progress longer than expected. **Blockers** Displays the number of active blockers preventing work from progressing. **Cycle Time** Displays the average time required for a work item to move from active development to completion. The metric may also include: * P50 Cycle Time * P90 Cycle Time to help teams understand median and upper-bound delivery performance. **Predictability** Measures how consistently the team delivers committed work within a sprint. ### Use Cases * Monitor sprint health * Identify workflow bottlenecks * Detect delivery risks early * Improve sprint execution * Measure delivery consistency ## Velocity: Commit vs Delivered ### What is it? A delivery performance chart comparing committed work against completed work across sprints. ### Why is it important? Helps teams understand whether sprint commitments are realistic and whether delivery goals are being achieved consistently. ### Where does it exist? Middle section of the dashboard. ### Metrics Included **Committed** Represents the amount of work planned and committed at the beginning of a sprint. **Delivered** Represents the amount of work completed and delivered during the sprint. ### Use Cases * Evaluate sprint planning accuracy * Measure team delivery performance * Identify overcommitment trends * Improve sprint forecasting * Monitor velocity consistency ## Sprint Burndown ### What is it? A chart that tracks the remaining work throughout a sprint. ### Why is it important? Provides visibility into sprint progress and helps teams determine whether work is being completed at the expected pace. ### Where does it exist? Bottom section of the dashboard. ### Metrics Included **Remaining Work** Displays the amount of work left to be completed during the sprint. **Burndown Trend** Shows how quickly the team is reducing the remaining workload. **Sprint Status Indicators** May display indicators such as: * On Track * Slight Lag * At Risk depending on sprint progress relative to planned completion. ### Use Cases * Track sprint progress * Identify delays early * Monitor workload completion * Improve sprint execution * Support daily standups and sprint reviews ## Controls and Filters ### What is it? Interactive controls used to customize dashboard data and reporting views. ### Why is it important? Allows users to analyze sprint performance across different projects and Jira boards. ### Where does it exist? Top-right section of the dashboard. ### Features **Project Filter** Allows users to select a specific project and view Jira metrics associated with that project. **Board Selector** Allows users to switch between Jira boards and analyze metrics for a specific team or workflow. ### Use Cases * Compare team performance * Analyze project-specific metrics * Review board-level delivery trends * Monitor multiple teams from a single dashboard ## Dashboard Refresh ### What is it? A refresh control that reloads dashboard data from Jira. ### Why is it important? Ensures users are viewing the latest sprint and delivery information. ### Where does it exist? Top-right section of the dashboard next to the board selector. ### Use Cases * Refresh sprint metrics * View newly synchronized Jira data * Validate recent updates * Ensure reporting accuracy ## Key Use Cases ### Sprint Performance Monitoring Track sprint execution and delivery outcomes across engineering teams. ### Delivery Predictability Analysis Measure how consistently teams deliver committed work. ### Workflow Optimization Identify blockers, aging work items, and process inefficiencies. ### Team Velocity Tracking Monitor delivery trends and improve sprint forecasting. ### Agile Delivery Reporting Provide engineering leadership with visibility into sprint health and delivery performance.