Great teams need great tools…
We set out to build something fundamentally better.
To cross the red line…
The Red Line Burndown was built on the premise that understanding your resource model and how a project is progressing against the assumptions in that resource model are critical to project execution. When projects cross the point of no return – when they cross the Red Line – teams are left with few options to bring the project back on track.
We set out to make it easy to define and visualize the resource model for a project along with error bars to account for the natural uncertainty that exists in all projects. Users can define the Plan Anchor date that represents when the project scope was finalized for tracking. All resource model assumptions are tied to this date.
Whether you’re working with story points or time-based projects, the Red Line Burndown makes it easy to understand whether the project is on track to stay within the boundaries of those resource model assumptions or it’s on a path to cross the red line.
Multiple Burndowns on one chart…
Our first of kind feature enables teams to visualize multiple burndowns on the same chart. This is especially valuable when analyzing past performance, understanding where the project is on-track and where there are critical issues lurking.
Each Additional Burndown is constructed by using a logical AND operator to identify the issues that exist in both the Primary Filter or JQL Query AND this additional burndown – aka it shows the subset of issues from the original query that match the Additional Burndown query.
Analyze Burndown Changes…
One of the most difficult things to figure out when looking at a burndown is which changes are contributing to major increases or decreases in the remaining work left in the project.
We tackled this problem by calculating the net change for every single issue in the burndown on every single date. These changes are presented in a sortable table below the burndown. Users can filter the table by zooming in on the chart or manually selecting start and end dates. Each series displayed on the chart can be selected for analysis.
Clicking on a row in the table instantly pops the tooltip on the chart so you can quickly identify from both the chart and the table how changes are affecting the project. Red text indicates increases in remaining scope and green indicates decreases.
Know your actual velocity (or utilization)…
Calculating velocity or utilization over time often involves downloading data, performing analysis, and sometimes iterating multiple times. We calculate the per developer velocity (story point mode) or average utilization (time-based mode) on a weekly basis and overlay that as a series on the chart so that you can easily see how your team is performing against the assumptions in your resource model.
Metrics that drive backlog health…
Have you ever scrutinized a burndown chart only to later realize that a significant number of the issues lacked an estimate? At the top of the Red Line Burndown chart, a set of metrics makes it easy to understand current backlog health. How many tickets aren’t estimated, what’s the average estimate, how many issues are in each status?
Highlight Critical Milestones and
Project End Date…
Keep your team and stakeholders aligned by clearly visualizing key project dates directly on the chart. Milestones appear as flag icons with user-defined labels, while the project end date is marked with a distinctive checkered flag. This makes it easy to communicate progress, expectations, and deadlines at a glance.
It’s your data…
you can download it if you want to!
- Users can download all the series data as csv with a single click
- Analyze Burndown Changes data can also be downloaded as csv
Data and Privacy are Protected through the
Runs on Atlassian Program
Data for this app is stored in each customer’s Atlassian Cloud instance, which means the app is:
- Hosted on Atlassian
- Data stored within Atlassian
- Data residency compliant