Planned vs. Actual Burndown Chart

Print this topicEmail this topic

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. Acutal Burndown

Release filter

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.

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.

Chart data

  • 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 chart illustrates the difference between the planned and actual burndown values for each iteration. 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.

Table data

  • 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
  • Planned Burndown is the iteration’s planned burndown value at the start of iteration
  • Actual Burndown is the iteration’s actual burndown value at the start of iteration

The table displays 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.

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.

Additional features

Use the Auto Height setting to automatically adjust the vertical space of the app based on the amount of visible data.

Feedback

Please send us your feedback regarding our help site. For feedback regarding the Rally product, click here to open a support case or click here to submit a new feature request
English
By submitting this form, you accept the Mollom privacy policy.
© 2014 Rally Software Development Corp | Legal