Feature overview
Agile Reports and Gadgets help Agile and SAFe teams track delivery performance, forecast outcomes, and visualize progress directly in Jira. The bundle includes eight apps:
Together, they provide a complete view of delivery speed, flow efficiency, predictability, and scope dynamics.
Who will benefit from Agile Reports and Gadgets
The charts would be beneficial for various roles in Agile and SAFe.
Team level
Scrum Masters
Product Owners
Agile Team Leads
Cross-team level
Delivery Managers
Program Managers
Release Train Engineers
System Architects / Solution Managers
Organization level
Portfolio Managers
C-level Executives
Agile transformation
Agile Coaches
Key features
1. Define what you analyze
Configure the chart scope
Include work from multiple Scrum and Kanban boards, projects, releases, initiatives, or custom JQL queries. You can also define the time period shown in the chart - select a number of past sprints, set a custom date range, and include or exclude closed, active, and future sprints.
Filter data
Narrow down the view with advanced filters. Focus on a specific sprint, epic, release, issue type, or user, or apply a custom JQL query to analyze the exact slice of work that matters most.
2. Measure delivery performance
Track velocity metrics for teams and individuals
Track the key metrics that drive sprint planning and delivery: initial commitment, final commitment, rollover, added or removed scope, estimation changes, completed work, and unfinished items. Monitor results across one or multiple teams, or switch to the individual view to analyze personal contributions.
Learn more about the Cross-team velocity chart and the Individual velocity chart
Compare velocity across multiple teams in a single view
Compare how multiple teams deliver work over time on a single chart, with each bar representing a different team. Switch between metrics to shift the focus, or use the checkboxes below the chart to show or hide teams.
Learn more about the Benchmarking velocity chart
Analyze delivery speed with Cycle time
Measure how long it takes to complete work items using Cycle time or Lead time metrics, and visualize how delivery performance evolves.
Use the Cycle time histogram to see how durations are distributed (which items are delivered within typical timeframes and which are delayed). The Cycle time trend chart will help you to track how averages, medians, or percentiles change across sprints, weeks, or months.
Learn more about Cycle time histogram chart and Cycle time trend chart
Reveal where capacity is actually spent
Segment completed work by issue type, team, priority, or any custom field to see how your capacity is distributed. Stacked bar charts make it easy to spot trends, such as an increasing share of bug work, rising operational load, or uneven contribution across teams.
3. Understand flow and stability
Monitor scope and workflow stability
Use the Burnup Flow chart to see how work enters, progresses, and leaves the system. Compare Arrival and Departure trends and observe changes in the To Do and In Progress areas to detect scope creep, confirm workflow stability, and ensure that work is completed at a sustainable pace.
Identify workload risks and bottlenecks
Use the Cumulative Flow Diagram with bands based on Statuses, and display only the In Progress statuses to visualize each workflow stage and spot where work starts to accumulate. Complement this gadget with the Time in status chart to see exactly where issues spend the most time. Break work down by In Progress and Waiting statuses to uncover queues, blockers, or inefficient handoffs between stages.
Learn more about the Cumulative Flow Chart and Time in Status chart
Validate delivery predictability
Use throughput distributions to assess output stability. Check whether your percentiles reflect typical delivery or are skewed by outliers, and see if the team delivers consistently or follows multiple delivery patterns.
4. Track progress against plan
Track progress over time with burnup and burndown charts
See Completed work, Remaining work, and Total work over time. Switch between burnup and burndown charts to highlight either progress made or work left. Add the Ideal burndown line in daily/sprint burndowns to compare the actual pace with the planned one.
Learn more about the Burnup chart, the Burndown chart, and the Sprint/Daily burndown chart
Benchmark against averages and targets
Use averages, medians, or percentiles from past sprints or time periods as benchmarks to understand what “normal” delivery looks like for your teams. To visualize whether actual performance aligns with expectations, add target lines.
5. Forecast outcomes and model scenarios
Model different delivery scenarios
Answer forward-looking questions with forecast scenarios in Burnup Burndown charts
When will the work be done if we continue at the current pace? → Min / Average / Max forecasts
What if we deliver faster or slower? → Target velocity, Target date, Velocity percentile
What if the remaining scope is smaller? → What-if remaining work
You can also refine assumptions by adjusting sprint length, applying a capacity allocation coefficient, or modeling scope growth.
Predict delivery dates
Estimate when and with what probability all remaining work is likely to be completed using a Monte Carlo simulation that runs 100,000 trials based on your team’s historical velocities. The simulation randomly samples past throughput for each future period to generate a distribution of possible completion dates, showing the earliest, most likely, and high-confidence outcomes.
Forecast scope completion
Decide how much scope you can confidently commit to by a fixed target date, using probability-based estimates derived from your team’s historical velocities. With 100,000 randomized trials based on past throughput, the chart generates a distribution of possible outcomes that shows how much work your team is likely to finish at different confidence levels. Use this view to make credible sprint commitments or set clear expectations with stakeholders.
Use alternative historical data for forecasts
Base your forecasts on the history that makes the most sense. If your current source doesn’t have enough data, or if its delivery history is irregular, you can bring in throughput from another board, project, release, or initiative.
6. Customize and explore the data
Customize calculations
Adapt how metrics are calculated to match your workflow. Select estimation fields, define custom Done statuses or from-to columns, choose between calendar and working time, or apply a default estimate for unestimated issues.
Drill into data
Click a sprint or interval on the chart to open its detailed breakdown. Inspect completed or remaining work and scope change, and group issues by any Jira field for clarity. Each item is linked back to Jira, so you can click through to investigate details.
Share and export
Share insights easily by adding charts as gadgets on Jira dashboards or embedding them in Confluence pages. For reporting outside Jira, export your data to CSV, PNG, or PDF.