---
sourceDocument: Australia Strategic Portfolio Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/it-business-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Agile 2.0 Prior Release Dashboard

# Agile 2.0 Prior Release Dashboard {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

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 AllAgile DevelopmentDashboards and select Agile 2.0 Prior Release Dashboard.
Figura 1. Agile 2.0 prior release burndown report Figura 2. Agile 2.0 prior release burnup report  
Nota:  
Canceled stories are not included in any of this data.

## End user and roles {#agile-development-prior-release-dashboard__section_upb_qj4_2fb}

{#agile-development-prior-release-dashboard__table_ov2_tj4_2fb__entry__3}

| 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 {#agile-development-prior-release-dashboard__ul_mn1_dy5_rlb} |
[Tabela 1. End user goal with required role and benefits]

{#agile-development-prior-release-dashboard__table_ov2_tj4_2fb}

## Indicators {#agile-development-prior-release-dashboard__section_nm4_hk4_2fb}

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 {#agile-development-prior-release-dashboard__section_yfw_qk4_2fb}

* Scrum: Release
* Scrum: Prior release
{#agile-development-prior-release-dashboard__ul_ulw_dl4_2fb}

## Widgets {#agile-development-prior-release-dashboard__section_f5y_ply_k3b}

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 {#agile-development-prior-release-dashboard__section_t5q_fl4_2fb}

{#agile-development-prior-release-dashboard__table_enf_b2k_k3b__entry__3}

| Title | Type | Description |
|-|-|-|
| Release Burnup | Line chart![Line 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. {#agile-development-prior-release-dashboard__ul_mtd_5sb_4mb} |
| Release Burndown | Line chart![Line 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. {#agile-development-prior-release-dashboard__ul_fwm_s2s_4mb} |
[Tabela 2. Prior release Summary]

{#agile-development-prior-release-dashboard__table_enf_b2k_k3b}

You can customize the Burnup and Burndown reports. For more
information, see [Customizing Agile 2.0 dashboard reports](https://servicenow-prod.fluidtopics.net/7K~8t3FoQZBqL4Knd0203g "Customize the Burnup, Burndown, and Cumulative Flow Diagram reports of your Agile 2.0 dashboards according to the custom states of your scrum stories.").