Sprint Burndown Charts with Sub-Tasks that Scale Across Multiple Teams in Jira

What is a Burndown Chart?

A burndown chart is used to visualize the work left to be done in any given sprint compared to the ideal velocity in the same timeframe. They help agile teams keep at an ideal pace of work in order to ship products on schedule.

Sprint burndown chart

The Problem with Burndown Charts in Jira

Burndown charts in Jira only exist for each board and do not scale across multiple teams for projects. Jira's burndown charts also don't account for sub-tasks in their calculation for work to be done.

To get around this, team leads manually export data and use Excel or other costly data visualization tools to create the report they need.

Once the data is exported it gets divorced from the real data stored in Jira, reducing the effectiveness of the report.

Management needs these charts to make timely changes in processes and personnel to make sure projects keep on track and they need to do so looking at data in real-time.

VisualScript's Burndown Chart Report

Large scale projects with multiple teams and sub-tasks need a better solution.

VisualScript's burndown chart provides cross team and cross sprint visibility and lets you properly account for sub-tasks. It's a more flexible and powerful alternative to the built-in Jira burndown chart.

VisualScript's burndown chart:

  • Works across teams for the whole project
  • Includes sub-tasks
  • Gives users the option to not use story points if they don't want them

VisualScript is also fully customizable so you can easily customize and tweak the built-in burndown chart to match your needs.

How it Works

To generate a Sprint Burndown Chart using VisualScript, you'll need VisualScript installed on your Jira instance. Once VisualScript is added to your instance, you can add a VisualScript gadget to your dashboard. When the VisualScript gadget is added to a dashboard, you'll see a list of available reports to run. The built-in reports will be in a folder called "Built-In Reports".

Choose "Jira Sprint Burndown" to add to your dashboard.

You'll be asked to provide a project key, the sprint name, and specify whether you want to include story points or not. You'll also need to enter your team's story point capacity.

If you choose to track story points, make sure all issues in your selected sprint have story points assigned to them.

Once your Sprint Burndown is generated, you'll see storypoints on the left y-axis and days across the right x-axis. The black line sloping from left to right that represents your ideal trajectory for progress. Your team's capacity will be represented by a blue line.

The target burn rate is the amount of work that needs to be completed per day to complete all work by the end of the sprint. The actual burn rate represents the speed at which your team is actually getting through work.

Your team's velocity is the actual burn rate. This will let you know how much work they'll finish during the sprint.

VisualScript burndown chart using parameters

Customize to Fit Your Needs

While VisualScript offers a turn-key, no-code solution that will work out of the box for many teams, you can also easily make adjustments to create a custom report.

VisualScript comes with a built-in SDK that makes it easy to generate custom reports that fit your teams' needs. We even have friendly engineers who will help you get started.