The beta version of the
Red Line Burndown
for Atlassian’s Jira
has been released in the
Atlassian Marketplace
At Crimsalytics, we develop high-quality apps to streamline project management, enabling teams to harness real-time project data for better performance and predictability.
Use Case #1 Agile Planning
We make planning Simpler & More Intuitive…
Whether you’re planning a sprint, a milestone or an entire project, clearly defining your capacity and resource model are critical to the success of the project.
The Resource Model feature allows you to specify the number of resources available between any given dates in your project and their velocity (story point mode) or utilization (time based mode). The chart shows the resource model – aka the Red Line – with a projection of when the project would complete if your velocity assumptions are realized.
Keeping track of the available resource capacity for a project can be difficult. The Budget feature allows you to define your team’s capacity on the burndown chart, so everyone clearly understands the intended plan. The Budget is represented by a horizontal line so the team sees how the project’s resource model and remaining work aligns with your resource capacity during planning and throughout execution.
Use Case #2 Tracking Projects
The burndown chart includes the ability to see multiple burndown data series on the same chart. By allowing users to define a JQL query to establish the primary burndown and JQL queries for additional burndowns, users can visualize how components of a project are contributing to the overall results. Some sample scenarios include monitoring:
- bugs as a function of the overall project
- various priorities as a function of the overall project
- individual features as a function of the overall project
- teams as a function of the overall project
- added scope or discovered work (if your project tags it in a way that can be queried through JQL)
- any other custom field that your team defines
Use Case #3 Analyzing Changes
A consolidated change log of every change within your project is shown below the burndown chart. This allows you to quickly identify meaningful changes in the project’s backlog. Select the series in question and quickly sort the data by change size. Click on a row and the corresponding point is highlighted on the burndown.
Alternatively, you can filter the change log table to the data currently visible on the chart (zoom in on what you want to see and filter) or you can directly filter by setting dates.
Transparency is the oxygen that enables high performing teams…
Full Support for Story Point or Time-Based Jira Cloud Projects
Built on JQL
Both the overall project burndown and all additional burndowns are specified through Jira’s Query Language (JQL). This makes it fast and easy to select tasks to be included in projects. Any fields that can be queried using JQL can be included in the filter for these burndowns making it easy to identify meaningful collections of work.
Built for Planning
Whether you’re planning a sprint, a milestone or a long-term project, the Red Line Burndown provides critical features like Budget definition, Resource Modeling, inclusion of discovered work factors and utilization errors.
Built for Analysis
When monitoring progress, the Red Line Burndown shows multiple burndown charts within the same view. This enables rapid access to insights about your team’s performance. You can instantly understand significant changes in the burndown
through our Analyze Burndown Changes feature. With the user-defined resource model, the burndown computes the weekly velocity (story point mode) or utilization (time based mode).
Built for Success
Understanding how your team is performing against the original model that you defined makes it easy to know when project adjustments need to be made. The Red Line Burndown will predict an end date for your project based on user inputs. These features provide the clarity that teams need to unlock their full potential.