---
sourceDocument: Yokohama Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-business-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Agile 2.0 Prior Sprint Dashboard

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

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Agile 2.0 Prior Sprint Dashboard

The Agile 2.0 Prior Sprint Dashboard in ServiceNow provides comprehensive data visualizations for analyzing the scope, actual burndown and burnup, and forecast trends of previous sprints.
This enables Scrum masters and sprint planners to gain visibility into past sprint performance and make informed decisions for planning upcoming sprints.
The dashboard excludes canceled stories from its data.
Show full answer Show less  
Access the dashboard by navigating to **All \> Agile Development \> Dashboards** and selecting **Agile 2.0 Prior Sprint Dashboard**.

## Key Features

* **Indicators:** Utilizes story points data from current and prior sprints to generate scope and completion metrics for burndown and burnup reports.
* **Breakdowns:** Data segmented by current and prior sprints to provide relevant sprint-specific insights.
* **Widgets:**
  * **Committed Points:** Displays the committed scope in story points for the sprint.
  * **Stories Completed:** Shows the total number of completed stories in the previous sprint.
  * **Completed:** Indicates the total story points completed in the previous sprint.
  * **Missing Estimates:** Highlights the number of stories without estimates in the prior sprint.
* **Data Visualizations:**
  * **Sprint Burndown Chart:** A line chart showing scope changes, ideal pace, remaining work, and completion trends. It includes series for scope, ideal burndown, and remaining work, allowing users to track if the team is ahead or behind schedule.
  * **Sprint Burnup Chart:** A line chart depicting the completed work and scope changes over the sprint to analyze team progress and scope adjustments.
* **Customization:** Both burndown and burnup reports can be customized to fit specific reporting needs.

## Key Outcomes

* **Enhanced Sprint Planning:** By analyzing prior sprint scope changes and actual completion trends, Scrum masters and sprint planners can better forecast and allocate work for upcoming sprints.
* **Improved Visibility:** The dashboard provides clear indicators and visualizations that highlight scope commitment, story completion, and estimation gaps, enabling proactive management of sprint performance.
* **Upgrade Consideration:** Customers upgrading from older versions of the Performance Analytics Content Pack for Agile 2.0 should install the updated dashboard from the Solution Library to benefit from improved layout and Sprint Burnup visualizations.  
Prior Sprint Dashboard provides data visualization on scope, actual burndown and burnup, and forecast trends of previous sprints. Analyze the data and plan the work for upcoming sprints.

Navigate to AllAgile DevelopmentDashboards and select Agile 2.0 Prior Sprint Dashboard.
Figure 1. Agile 2.0 prior sprint dashboard widgets Figure 2. Agile 2.0 prior sprint dashboard burndown visualization Figure 3. Agile 2.0 prior sprint dashboard burnup visualization  
Note:  
Canceled stories are not included in any of this data.

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

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

| End user and goal | Required role | Benefits |
|-|-|-|
| Scrum master and sprint planner: Need visibility into actual changes in scope and forecast trends of the previous sprints. | scrum_user | * Analyze sprint burndown and burnup trends * Use the data to plan for upcoming sprints {#agile-development-prior-sprint-dashboard__ul_xjv_q5m_rlb} |
[ ]

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

## Indicators

The following are the indicators which are used to generate the data for the reports of this dashboard.  

Scrum: Sum of story points of all stories in the current sprint

:   Generates the scope series in the Sprint Burndown and Sprint Burnup reports.

Scrum: Sum of story points of active stories in the current sprint

:   Generates the completed series in the Sprint Burndown and Sprint Burnup reports.

## Breakdowns {#agile-development-prior-sprint-dashboard__section_yfw_qk4_2fb}

The following are the breakdowns used by the indicators.

* Scrum: Sprint
* Scrum: Prior Sprint
{#agile-development-prior-sprint-dashboard__ul_ulw_dl4_2fb}

## Widgets {#agile-development-prior-sprint-dashboard__section_ybr_3my_k3b}

Committed points

:   Indicates the committed scope (in number of story points) of the sprint.

Stories Completed

:   Indicates the total number of stories that were completed in the previous sprint.

Completed

:   Indicates the amount of work (in story points) that was completed in the previous sprint.

Missing Estimates

:   Indicates the total number of stories in the previous sprint that were missing estimates.

## Data visualizations {#agile-development-prior-sprint-dashboard__section_t5q_fl4_2fb}

If you are upgrading from version 1.0.2 or earlier of Performance Analytics Content Pack for Agile 2.0. Install this dashboard from Solution Library to upgrade its layout and access the Sprint Burnup visualization. For more
information, see [Upgrading the layout of Agile 2.0 dashboards](https://www.servicenow.com/docs/LKv2THEg513vN8Zp7RlnBA "Upgrade to the latest layout of Agile 2.0 dashboards using Solution Library.").  
{#agile-development-prior-sprint-dashboard__table_mbk_ndk_k3b__entry__3}

| Title | Type | Description |
|-|-|-|
| Sprint Burndown | Line chart![Line chart]() | Indicates the scope changes, if any, and trends of those scope changes. Indicates the ideal pace of work, how much work is remaining, and if the scope is likely to be completed before the end of the sprint. The Sprint Burndown report comprises the following series that can be hidden or displayed based on your preference: * Scope: Indicates the amount of work that is planned for the sprint. * Ideal Burndown: Indicates how the team needs to progress on stories to complete the sprint on time. * Remaining: Indicates the amount of work left for completion in the sprint. If Remaining is above the Ideal Burndown, it implies that there is more work left than originally estimated. The team is running behind the schedule of the sprint. If Remaining is below Ideal Burndown, it implies that there is less work left than originally estimated. The team is running ahead of the schedule of the sprint. {#agile-development-prior-sprint-dashboard__ul_qjf_qdk_k3b} Analyze the burndown trends and accordingly plan the workload for an upcoming sprint. |
| Sprint Burnup | Line chart![Line chart]() | Shows the previous sprint burnup trend indicating scope changes. Analyze future changes the trend of team's work completion. The Sprint Burnup report comprises the following series that can be hidden or displayed based on your preference: * Scope: Indicates the amount of work that is planned for the sprint. * Completed: Indicates the amount of work completed in the sprint. {#agile-development-prior-sprint-dashboard__ul_vp1_ln5_rlb} |
[ ]

{#agile-development-prior-sprint-dashboard__table_mbk_ndk_k3b}

You can customize the Burnup and Burndown reports. For more information, see [Customizing Agile 2.0 dashboard reports](https://www.servicenow.com/docs/HN4ALUk8PGBSTq23oKmVsw "Customize the Burnup, Burndown, and Cumulative Flow Diagram reports of your Agile 2.0 dashboards according to the custom states of your scrum stories.").

*[\>]: and then


