Prior Release Dashboard provides data visualization on scope, actual burnup and burndown, and forecast trends of previous releases. Analyze the data and plan the work for upcoming releases.

Navigate to All > Agile Development > Dashboards and select Agile 2.0 Prior Release Dashboard.

Figure 1. Agile 2.0 prior release burndown report
Agile 2.0 prior release burndown report.
Figure 2. Agile 2.0 prior release burnup report
Agile 2.0 prior release burnup report.
Note: Canceled stories are not included in any of this data.

End user and roles

Table 1. End user goal with required role and benefits
End user and goal Required role Benefits

Product owner: Needs visibility into actual changes in scope and forecast trends of the previous releases.

scrum_user
Analyze trends for the following:
  • Scope changes
  • Previous releases

Indicators

Scrum: Sum of story points of completed stories in the active releases
Generates the actual burndown series in the Release Burndown report, and the completed series in the Release Burnup report.
Scrum: Sum of story points of all stories in active releases
Generates the scope series in the Release Burndown and Release Burnup reports.

Breakdowns

  • Scrum: Release
  • Scrum: Prior release

Widgets

Stories Completed
Indicates the total number of stories that were completed in the previous release.
Completed
Indicates the amount of work (in story points) that was completed in the previous release.
Missing Estimates
Indicates the total number of stories in the release that are missing estimates.

Data visualizations

Table 2. Prior release Summary
Title Type Description
Release Burnup Line chartLine chart

Analyze the burnup trends of a previous release.

The prior release burnup report comprises the following series that can be hidden or displayed based on your preference:

  • Scope: Indicates the amount of work that was planned for the release.
  • Completed: Indicates the amount of release work that is complete for this release.
Release Burndown Line chartLine chart

Shows the scope and rate of scope change, the ideal rate for work completion, and the actual rate of work completion. Analyze the burndown trends and accordingly plan the workload for an upcoming release.

The prior release burnup report comprises the following series that can be hidden or displayed based on your preference:
  • Scope: Indicates the amount of work that was planned for the release.
  • Ideal Burndown: Indicates how the team had to progress on stories to deliver the release on time.
  • Remaining: Indicates the amount of work that is completed.

    If the actual burndown (Remaining) is above the ideal burndown, it implies that the team was running behind the schedule of the release. If the actual burndown (Remaining) is below the ideal burndown, it implies that the team was running ahead of the schedule of the release.

You can customize the Burnup and Burndown reports. For more information, see Customizing Agile 2.0 dashboard reports.