Follow
Using the Scrum Agile Burndown Chart

 

The agile burndown chart is displayed together with the completion status and the story board. These agile components are available in the following situations in Workfront: 

  • On agile iterations
    For more details about using the agile burndown chart, story board, and completion status in a pure agile environment (with backlogs and an iteration), see "Working in an Agile Environment."
  • When viewing a project in an agile view
    NOTE In order for the burndown chart to be displayed in an agile view on a project, the current day must be within the start and end date of the project, and tasks must have Planned Hours assigned to them.
    For information about how you can leverage the agile story board, burndown chart, and completion status within an existing project, see "Managing a Project in an Agile View."

This section discusses the completion status and burndown chart. For information about the agile story board, see "Using the Agile Story Board."
 

Understanding Iteration Completion Status

The completion information described in this section is displayed above the burndown chart.

Completion Percentage on an Iteration

Completion Percentage When Viewing a Project in an Agile View

This information indicates the completion status of the iteration or project for the day that is currently selected in the burndown chart. By default, the completion status is displayed based on the current day's date.

The following information is available:

Percent Complete: Overall progress of the iteration or project. Percent Complete is calculated based on the number of completed points or hours divided by the total number of points or hours associated with the iteration or project.

Percent Complete adjusts based on the percent complete of each story or task within the iteration or project, including stories or tasks that are only partially complete.

The color of the Percent Complete status bar displays as red or green to match the color of the actual burndown rate. It is shown in red when the burndown rate is less than the ideal (more points or hours remaining per day than the ideal burndown calculation), and it is shown in green when the burndown rate is equal to or better than the ideal (equal or fewer points remaining per day than the ideal burndown calculation).

Completed Stories: (Available only in iterations) The number of stories marked Complete. This is shown in relation to the total number of stories in the iteration. For example, "3 of 6" indicates that 3 of the 6 stories in the iteration have been marked Complete.

Project Status: (Available only in projects) The status of the project is displayed.

Completed Points / Hours: (Available only in iterations) The number of points or hours marked Complete. Shown in relation to the total number of points or hours in the iteration. For example, "5 of 11" indicates that 5 of the 11 stories in the iteration have been marked Complete. This number is directly related to the Percent Complete calculation, and is updated at the same time Percent Complete is updated.

Points and hours are associated with stories. When a story is marked Complete, the points or hours associated with that story are marked Complete. 

By default, points are used. You can change this by modifying the settings for your team, as described in "Configuring How Stories Are Estimated (Points or Hours)" in "Creating and Managing Agile Teams."

Planned Hours Complete: (Available only in projects) The number of Planned Hours marked Complete. Shown in relation to the total number of Planned Hours from all tasks in the project.

Points / Hours Per Day: (Available only in iterations) The average number of points or hours marked Complete each day since the beginning of the iteration through the current day.

This is calculated by the total points or hours complete, divided by the total number of days through the current day. (Partial days are recorded as a whole day.)

This information can be useful when planning a future iteration.

Average Hours Per Day: (Available only in projects) The average number of hours marked Complete each day (calculated from the time that the project status was first moved to Current). [! Is this accurate?]

Estimated Completion: The estimated date that the iteration or project will be completed, based on the current rate in the Points / Hours Per Day (for iterations) or Average Hours Per Day (for projects). 

When the Estimated Completion date is later than the end date defined for the iteration or project, the number of working days remaining is displayed as red in parenthesis next to the Estimated Completion date.

When the Estimated Completion date is earlier than the planned end date of the iteration or project, the number of working days remaining is displayed in green. (The end date for the iteration is specified when the iteration is planned, as described in "Creating an Iteration"; the end date for the project is the Planned Completion Date, or it is the current date if the Planned Completion Date is in the past. The Planned Completion Date for the project is calculated based on the duration of tasks in the project.) When planning the iteration, if you set the iteration end date for a non-working day and the iteration is tracking to finish on time, the Estimated Completion date is set for the last working day prior to the iteration end date that you set (because work is not scheduled to be burned down on non-working days).

For example, "(+9 days)" indicates that the Estimated Completion date is 9 working days later than the iteration's planned end date.

For more information, see "Understanding How Days Off Affect the Burndown Chart."

Understanding the Burndown Chart

The burndown chart provides a visual representation of how stories are progressing through the iteration or project. The actual burndown rate is measured against the ideal burndown rate for the iteration or project timeline.

The burndown chart adjusts based on the selected day. The current day is the default. When a previous day is selected, all data in the burndown chart and all values in the completion status section above the burndown chart are recalculated to represent the data as it was at the end of the selected day. (You can select past days or the current day; you cannot select days in the future.)


 

Understanding Visual Indicators

The burndown chart contains the following visual indicators:

Ideal burndown rate based on when the iteration or project began.

 

This line is not displayed if the scope of the iteration or project never changes (hours or points are never added or removed).

 

This line is displayed as flat when work is done on a day off. For more information, see "Understanding How Days Off Affect the Burndown Chart."

Ideal burndown rate based on current stories or tasks.

 

The current ideal burndown rate (solid blue line) differs from the original ideal burndown rate (dotted blue line) when hours or points are added to or removed from the iteration or project after the iteration or project begins.

 

This line is displayed as flat when work is done on a day off.

 

For more information, see "Understanding How Days Off Affect the Burndown Chart."

 

Actual burndown rate is shown in red when the burndown rate is less than the ideal (more points or hours remaining per day than the ideal burndown calculation).

 

The following formula is used to calculate the actual burndown rate:

 

[SUM(Point or Hour Value of In-Progress Work * Percent Complete) + Point or Hour Value of Completed Work]

Actual burndown rate is shown in green when the burndown rate is equal to or better than the ideal (equal or fewer points remaining per day than the ideal burndown calculation).

 

The following formula is used to calculate the actual burndown rate:

 

[SUM(Point or Hour Value of In-Progress Work * Percent Complete) + Point or Hour Value of Completed Work]

Change in scope (hours or points are added or removed from the iteration or project).

 

Scope changes are always shown as a vertical line in the middle of the day. In addition, a blue dot is displayed in the middle of any day where a scope change has occurred.

 

The vertical axis of the burndown chart shows the story points or hours.

Change in date range (iteration or project duration is either increased or decreased).

 

A blue dot is displayed in the middle of any day where the iteration or project duration was changed.

A green or red dot is displayed on the actual burndown rate any time work is burned down. (When the actual burndown rate on that day is red, the dot is red; when the actual burndown rate on that day is green, the dot is green.)

 

Work is burned down when any of the following occur:

  • The Percent Complete is increased on the story.
    Percent Complete is increased when:
    • Manually changed

    • The number of points or hours are updated on the story

  • The status of the story is changed to Complete

Understanding How Days Off Affect the Burndown Chart 

The default schedule defined in Workfront affects the burndown chart by excluding days off (weekends and holidays) from the burndown. The burndown chart uses the default schedule to define working days (as described in "Workfront Schedules").

Agile teams can incorporate team-specific non-working days by defining an alternate schedule (as described in "Defining an Alternate Team Schedule for Burndown Charts" in "Creating and Managing Agile Teams"). This alternate schedule is then reflected in the burndown chart of any iteration assigned to the team. The alternate schedule affects only the burndown chart.​ You cannot define an alternate schedule for an agile view on a project.

Days off are reflected in the burndown chart only if:

  • Work was previously logged on a day off.  (The day when work was logged is displayed.)

    When work is logged on a day off:

    • Any work logged is not included when calculating the ideal burndown because the team is not scheduled to do any work.

    • The ideal burndown lines (the solid blue line and dashed blue line) are displayed as flat in the burndown chart for any day when work was done or on the day you are viewing the burndown chart (if you are viewing on a day off). 

    • Work logged is included when calculating other burndown statistics such as the estimated completion and the average points or hours per day. 

  • You are viewing the burndown chart on a day off. (The day that you are viewing is shown on the burndown chart.)

  • You complete the total remaining work for the iteration or project on a day off. 

    When a user completes the total remaining work for the iteration or project on a day off, the Estimated Completion field displays the date the iteration or project was completed.

    When planning the iteration, if you set the iteration end date for a non-working day and the iteration is tracking to finish on time, the Estimated Completion date is set for the last working day prior to the iteration end date that you set (because work is not scheduled to be burned down on non-working days). 

    The end date for the iteration is specified when the iteration is planned, as described in "Creating an Iteration." The end date for the project is calculated based on ...

Using an Alternate Team Schedule for Burndown Charts

NOTE Alternate team schedules are used only on iterations; alternate team schedules are not used when viewing a project in an agile view. 

Schedules that are defined in Workfront affect the burndown chart by excluding days off (weekends and holidays) from the burndown chart.

By default, the burndown chart uses the default schedule to define working days (as described in "Workfront Schedules"). However, your team can choose to use an alternate schedule in order to incorporate team-specific non-working days. This alternate schedule is then reflected in the burndown chart of any iteration assigned to the team. The alternate schedule affects only the burndown chart.

For information about how to select an alternate team schedule to be used in the burndown chart, see "Using an Alternate Team Schedule for Burndown Charts" in "Creating and Managing Agile Teams."

Resizing and Collapsing the Burndown Chart

You can resize or collapse the burndown chart to adjust how much room it occupies on the story board.

Any changes you make to the size or visibility of the burndown chart are visible only to you, and are reset when you clear your browser cache.

Resizing the Burndown Chart

  1. Navigate to the iteration or project that contains the burndown chart you want to resize.
  2. Hover over the bottom line of the burndown chart, then drag the chart to the desired size.

Collapsing the Burndown Chart

  1. Navigate to the iteration or project that contains the burndown chart you want to collapse.
  2. Click the arrow icon in the left of the Percent Complete status bar.

Troubleshooting: Manually Synchronizing Data in the Burndown Chart

The burndown chart is synchronized automatically with data in your project or iteration. If the burndown chart ever becomes out of sync with data in the project or iteration, you can manually synchronize it.

To manually synchronize the burndown chart with data in your project or iteration:

  1. Navigate to the project or iteration where you want to manually synchronize the burndown chart.
  2. (Conditional) On a project, ensure that you are viewing the project in an agile view, as described in "Managing a Project in an Agile View." 
  3. On a project, click Project Actions.
    Or
    On an iteration, click Iteration Actions.
  4. Click Synchronize Burndown Data.