Planned vs. Actual Burndown Chart

The Planned vs. Actual Burndown app captures a release ’s burndown progress. It is a chart overview with a table to view the data. Use this app to help you determine if:

  • The release is progressing as expected.
  • The work is logically divided between the iterations.
  • There should be a reallocation of the user stories to other iterations.

Planned vs. Actual Burndown

Source code is available: Planned vs. Actual Burndown Chart app source code

Viewing Burndown Data

To use the information displayed in the app:
  1. Use the release drop-down to select the data to burn down in the chart. When a release is selected, any iterations that are active after the release start date or before the release end date will be added to the chart. Work items in the iterations, including those not directly assigned to the release, are included.
  2. View the chart to see the difference between the planned and actual burndown values for each iteration.
    • The planned burndown line displays the trend of the planned velocity burndown
    • The actual burndown line displays the trend of the actual velocity burndown

    The actual burndown line is dashed when the value was predicted by using the planned velocity values instead of the actual velocity values for future iterations.
  3. View the table data to see the burndown related data broken down by iteration. The “Release Plan Estimate ” value located above the table is the sum of all plan estimates for the selected release. It is used to help calculate the planned and actual burndown values for the beginning of each iteration by subtracting the appropriate value. The release row shows the burndown values at the end of the last iteration.
    • Iteration Name displays the iterations’ names for the selected release.
    • Start Date is the iteration’s start date.
    • End Date is the iteration’s end date.
    • Plan Estimate is the total plan estimates for the iteration’s user stories, defects, and defect suites.
    • Actual Velocity is the total plan estimates for the iteration’s accepted user stories, defects, and defect suites.
    • Planned Velocity is the iteration’s planned velocity value.
    • Actual Burndown is the iteration’s actual burndown value at the start of iteration.
    • Planned Burndown is the iteration’s planned burndown value at the start of iteration.

    Actual burndown values occurring in the past are blue, actual burndown values occurring in the future are light grey, and planned burndown values are dark grey.
Note: This data collection works differently than some other apps, such as Release Scope Change, which use the release name field to filter and collect work items. You may see different totals when comparing figures in each app.

Feedback

Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.