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/Sprint or Sprint.

Interpreting Chart

Burndown chart gives an overview of the progress of work overtime 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/Sprint 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, perform the following steps:

  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, ToDo, Card Count).

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 filter the Burndown chart to view it for specific card types. Click the Filter icon on the chart toolbar. The filter will be applied even for export in MS Excel format.

6. Moreover, you can also export the chart into MS Excel by clicking the Export icon on the chart toolbar, and view it offline.

7. Click the Close icon to close the chart.

Sprint Burndown Chart

To view a Sprint Burndown Chart, perform the following steps:

  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.

Viewing PI or Sprint Burndown Chart by Estimate, To-Do(Hours), or Card Count

Let us understand how the chart is plotted when you select Estimate, To-Do(Hours) or Card Count.

Viewing Chart by To-Do Hours

To view the Burndown chart by To-Do(Hours), the To-Do owners should enter the To-Do Estimates, Actual Effort, and Remaining Effort on a daily basis in the cards to track the progress of the PI/Sprint in the Burndown chart.

You can enable the Time-Tracking Plug-in to enter effort on To-Dos. Effectively, you can see some meaningful data generated on the Burndown Charts. See Logging Effort for To-Dos help for details on how team members can log effort for To-Dos.

  • Interpret the Actual, Planned, and Remaining values in hours as team members will be entering daily effort in hours.
  • The PI/Sprint/Sprint Burndown chart plots the sum of all Daily Remaining Effort (that the To-Do owners enter for cards scoped in the PI/Sprint) on the Y-axis against the dates on the X-axis (from the PI/Sprint start date through the PI/Sprint end date). The Burndown slope is the orange line indicating the remaining hours as the PI/Sprint moves through the end date.
  • The PI/Sprint Burnup line (in green) is plotted for the sum of all Daily Actual Effort (that the To-Do owners enter for the cards scoped in the PI/Sprint) on the Y-axis against the dates on the X-axis (from the PI/Sprint start date through the PI/Sprint end date).
  • The chart also shows a blue line indicating the planned slope i.e. how the cards should have ideally been completed through the PI/Sprint ideally. It is the sum of remaining effort for To-Dos of cards on the PI/Sprint start date through the PI/Sprint end date closing at ‘0’.

burndown by todo

Viewing Chart by Estimate

  •  To view the Burndown chart by Estimate, the card owner needs to enter the value in the Estimates Each card in the PI/Sprint will have Estimate points which will form the basis of Actual, Planned, and Remaining values in the Burndown chart.
  • The blue line indicating the slope of how the cards should have ideally been completed through the PI/Sprint. It is the sum of values entered on the Estimates field of the PI/Sprint cards divided by the number of PI/Sprint days. The blue line shows the ideal way of burning the total scoped work from the PI/Sprint start date through the PI/Sprint end date closing at ‘0’.
  • The Remaining or the orange dotted line is calculated based on the total Estimate value of the cards that are still in the Ready or In-progress column.
  • Actuals or the PI/Sprint Burnup line in green color is the total Estimate value of the cards that are either archived or moved to or beyond the Done column.

 Viewing Chart by Card Count

  •  The Burndown chart by Card Count is plotted based on the number of cards tagged to the PI/Sprint that are archived or moved to or beyond the Done column. The aggregated count of such cards form the basis of Actual, Planned, and Remaining values in the Burndown chart.
  • The blue line indicating the slope of how the cards should have ideally been completed through the PI/Sprint. It is the total number of cards tagged to the PI/Sprint cards divided by the number of PI/Sprint days. The blue line shows the ideal way of completing the cards from the PI/Sprint start date through the PI/Sprint end date closing at ‘0’.
  • The Remaining or the orange dotted line is calculated based on the total number of cards that are still in the Ready or In-progress column.
  • Actuals or the PI/Sprint Burnup line in green color is the total number of cards that are either archived or moved to or beyond the Done column.

  • Was this helpful?
  • Yes   No