SwiftEaSe provides the Burndown chart for the team to track its progress against a Program Increment(PI)a sprint plan in their daily scrum meetings. Burndown charts that can be tracked for any board containing tasks with estimates and actual effort, is a graphical representation of outstanding work (or backlog) against time. It is useful for predicting when all the work scope will be completed.

Note: You can plot the Burndown chart for the current Board and its child Boards at the lower level . For example, if you are plotting the Burndown chart via Lean Analytics from a Program level workboard, then the chart fetches data from that Program Work Board and also from its child Team Work Boards .

You can further use the filter in the refine the scope of the chart based on card type. For example, if you want to view only the Team level Burndown chart, then you can select card types like User Story, Technical Story, Issue and Defect.

You can use the Burndown chart at two levels: PI and Sprint.

The Burndown chart can be plotted on the following parameters:

  • Estimate(Story Points) or any other Unit of Measurement
  • To-Do Hours

 The Estimate (Story Points) is plotted based on the cards that are either archived or move to or beyond the Done column during the PI or Sprint.

The Hours plotted based on the hours logged in the Actual field of the To-Dos of the cards that are either archived or move to or beyond the Done column during the PI or Sprint.

Interpreting Chart

Burndown chart gives an overview of the progress of work over time while completing a project. As work is completed, the graph “burns down” to zero.

For each project or Board, Y-axis displays the estimate statistics (like Story Points or To-Do Hours) and the X-axis displays the duration.

The Planned Burndown (blue dotted line) depicts the planned rate at which the work needs to be completed in the ‘ideal’ scenario. It is a straight line that intercepts the Y-axis at the highest point showing the maximum work to be done. It gradually decreases to zero over the sprint/PI and intercepts the x-axis.

The Remaining Burndown (orange dotted line) reflects the rate at which the work is left remaining.  The line is built up by adjoining all the data points that represent the amount of work remaining on each day of the Sprint or PI.

The Actual Burndown (in To-Do hours or any other Unit of Measurement) line represents the rate at which the work is getting completed in a PI or Sprint.

Hovering over any of the data points, a vertical line intersecting all three will be displayed along with their values.

Program Increment(PI)Burndown Chart

To view a PI Burndown Chart:
  1. Select Lean Analytics from the Selected Board breadcrumb menu, and then navigate to PI Burn Down chart.
  2. Select your respective PI from the drop-down menu.
  3. Select your UOM for Estimate (StoryPoint or ToDo).
  4. The Burndown chart is displayed below showing how remaining effort comes to ‘0’, which also is a burn-up chart if you track the progress of Actual Effort.

Note: The data in the chart is fetched from the current Work Board and also from its lower level child Work Boards.

5. You can even filter the chart by Card Type in that board or even export it to Microsoft® Excel(.xlsx) format.

Sprint Burndown Chart

To view a Sprint Burndown Chart:
  1. Select Lean Analytics from the Selected Board breadcrumb menu, and then navigate to Sprint Burn Down chart.
  2. Select your respective Sprint from the drop-down menu.
  3. Select your UOM for Estimate (StoryPoint or ToDo)
  4. The Burndown chart is displayed below showing how remaining effort comes to ‘0’, which also is a burn-up chart if you track the progress of Actual Effort.

Note: The data in the chart is fetched from the current Work Board and also from its lower level child Work Boards.

5. You can even filter the chart by Card Type in that board or even export it in Microsoft Excel(.xlsx) format.

  • Was this helpful?
  • Yes   No