--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-business-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Agile 2.0 Sprint Dashboard # Agile 2.0 Sprint Dashboard {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 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 Sprint Dashboard The Agile 2.0 Sprint Dashboard in ServiceNow provides a comprehensive view of your current sprint's progress, enabling scrum masters and sprint planners to track story completion, scope changes, and forecast sprint outcomes. It helps you monitor key sprint metrics such as percentage of work completed, time elapsed, missing story estimates, and blocked work. This dashboard is accessible viaAll \> Agile Development \> Dashboardsby selecting the Agile 2.0 Sprint Dashboard. Show full answer Show less ## Key Features * **Sprint Details and Progress:** Visual widgets show percentage of work completed, elapsed sprint time, and count of stories missing estimates. * **Scope and Story State Analysis:** Displays committed work versus current scope, and the number of stories in each state (e.g., Ready, In Progress, Testing, Complete). * **Forecasting:** Predicts likelihood of sprint completion on schedule by analyzing burndown and burnup trends based on historical data. * **Visual Reports:** Includes Sprint Burndown, Sprint Burnup, and Cumulative Flow Diagram charts to monitor scope changes, work completion trends, and story state transitions. * **Indicators and Metrics:** Utilizes story points to calculate total scope, completed work, percent completed, time elapsed, and blocked work for actionable insights. * **Customizable Reports:** Dashboards and reports can be tailored to your team's specific needs for enhanced visibility. * **Missing Estimates Handling:** Stories missing estimates can be flagged, and entering default story points enables meaningful dashboard analytics. ## Key Outcomes * Gain clear visibility into sprint progress and scope changes to proactively manage and adjust sprint plans. * Analyze sprint burnup and burndown trends to understand whether your team is ahead, on track, or behind schedule. * Forecast sprint completion dates to better manage expectations and resource allocation. * Identify blocked work and missing estimates to ensure accurate tracking and timely resolution. * Improve sprint planning and execution by monitoring story states and their transitions throughout the sprint lifecycle. Track the progress of your stories in the current sprint and forecast sprint completion using the Sprint Dashboard. Navigate to AllAgile DevelopmentDashboards and select Agile 2.0 Sprint Dashboard. Figure 1. Agile sprint dashboard widgets Figure 2. Agile sprint dashboard burndown report Figure 3. Agile sprint dashboard burnup visualization Figure 4. Agile sprint dashboard cumulative flow diagram The Agile 2.0 Sprint Dashboard provides the following insights: * Displays details of the sprint such as percentage of work that is complete, time elapsed, and total number of stories that are missing estimates. * Displays the number of stories of the sprint in their current state and their progress. * Indicates the scope changes, if any, and trends of those scope changes. * Indicates the way the team needs to progress on stories to achieve the sprint goal. * Forecasts data showing the likelihood of completing the sprint as planned. {#agile-development-sprint-dashboard__ul_dcq_sg4_vgb} ## End user and roles {#agile-development-sprint-dashboard__section_upb_qj4_2fb} {#agile-development-sprint-dashboard__table_ov2_tj4_2fb__entry__3} | End user and goal | Required role | Benefits | |-|-|-| | Scrum master and sprint planner: Need visibility into scope changes, completed and remaining work for a sprint to adjust plans to complete the sprint on time. | scrum_user | * Analyse the sprint burnup and burndown trends * Analyse the scope change for the sprint * View current states and analyse the time in each state for the stories of the sprint * Estimate sprint completion dates {#agile-development-sprint-dashboard__ul_qhl_vbl_rlb} | [ ] {#agile-development-sprint-dashboard__table_ov2_tj4_2fb} ## Indicators {#agile-development-sprint-dashboard__section_nm4_hk4_2fb} Scrum: Sum of story points of all stories in the current sprint : Generates the scope series in the Sprint Burndown and Burnup reports. The scope series indicates the amount of work (in story points) that is the planned for the sprint. Scrum: Sum of story points of active stories in the current sprint : Generates the completed series in the Sprint Burndown and Burnup reports. The completed series indicates the amount of work (in story points) completed in the sprint. Scrum: Time elapsed in sprint : Calculates the time to be displayed in the Time Elapsed widget. Scrum: Count of all stories in the current sprint : Generates the area series in the Sprint Cumulative Flow Diagram report. It indicates the number of stories in the current sprint. Scrum: Percent Completed by Points : Calculates the amount of work (in percentage) completed for the sprint. The value is the result of the following formula: ([[Scrum: Sum of story points of completed stories in current sprint]]/[[Scrum: Sum of story points of all stories in the current sprint]]*100) ## Breakdowns {#agile-development-sprint-dashboard__section_yfw_qk4_2fb} * Scrum: Sprint * Scrum: Current Sprint * Scrum: State {#agile-development-sprint-dashboard__ul_ulw_dl4_2fb} ## Widgets {#agile-development-sprint-dashboard__section_ybr_3my_k3b} Scope : Indicates the amount of work in story points that is planned for the sprint. This widget lets you see at a glance how much work must be completed to achieve the sprint goal. It also lets you drill down to detail on the stories planned into the sprint. Percent Completed : Indicates the percentage of work that has been completed in the sprint using story points. This widget lets you see at a glance how much work has been completed in the sprint. Together with the adjacent Time Elapsed widget, these widgets let you see whether you are completing work at a rate consistent with achieving the sprint goal on schedule. Time Elapsed : Indicates the percentage of time that has elapsed between the start date and planned end date of the sprint. Together with the adjacent Percent Completed widget, these widgets let you see whether you are completing work at a rate consistent with achieving the sprint goal on schedule. Committed Points : Indicates the committed scope (in number of story points) of the sprint. Together with the adjacent Scope widget, these widgets show the difference between the sprint's committed and current scope. Note: This widget is not visible by default. You can add it from Reports to your dashboard. For more information, see [Edit a responsive dashboard](https://www.servicenow.com/docs/access?context=t_EditADashboard&version=australia&pubname=australia-now-intelligence&ft:locale=en-US). Missing Estimates : Indicates the total number of stories in the sprint that are missing estimates. It is required that you use estimates for the other indicators, widgets, and reports on this dashboard to be meaningful. Tip: If you do not estimate stories, enter a "1" in the Story Points field. The other indicators, widgets, and reports will then effectively function by count. Blocked Work : Indicates the amount of work (in story points) in the sprint that is blocked. ## Data visualizations {#agile-development-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, then install this dashboard from Solution Library to upgrade its layout and access the following visualizations: * Sprint Burnup * Sprint Cumulative Flow Diagram {#agile-development-sprint-dashboard__ul_hcl_c4y_qmb}For more information, see [Upgrading the layout of Agile 2.0 dashboards](https://servicenow-prod.fluidtopics.net/91ecTSvepCBYJRx3ezEczw "Upgrade to the latest layout of Agile 2.0 dashboards using Solution Library."). Note: For all reports shown in the Sprint dashboard, the planned end date of the Sprints is used as a filter. Completed Sprints appear in the chart only if their Planned end date is less than or equal to the current date. {#agile-development-sprint-dashboard__table_mbk_ndk_k3b__entry__3} | Title | Type | Description | |-|-|-| | Sprint Burndown | 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. * Scope Forecast: Predicts the possibility of scope change for the future dates, which is based on historical data. * 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 the actual burndown 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 the actual burndown is below the ideal burndown, it implies that there is less work left than originally estimated. The team is running ahead of the schedule of the sprint. * Remaining Forecast: Predicts the burndown for the future dates. It indicates whether you can complete the sprint on time. The prediction is based on historical data. {#agile-development-sprint-dashboard__ul_qjf_qdk_k3b} | | Sprint Burnup | Line chart ![]() | Shows the sprint burnup trend indicating scope changes. Forecasts future changes in scope and the trend of 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. * Scope Forecast: Predicts the possibility of scope change for the future dates, which is based on historical data. * Completed: Indicates the amount of work completed in the sprint. * Completed Forecast: Predicts the burnup for the future dates. It indicates whether you can complete the sprint on time. The prediction is based on historical data. {#agile-development-sprint-dashboard__ul_vp1_ln5_rlb} | | Sprint Cumulative Flow Diagram | Area chart ![]() | Monitor the progress of all the stories of your sprint between its actual start and end dates. View the number of stories in each state by their arrival to a state, time in this state, and its departure from this state. The Sprint Cumulative Flow Diagram report comprises the following areas that can be hidden or displayed based on your preference: * Ready: Indicates the number of stories in the sprint that are ready to start work on. * Work in Progress: Indicates the number of stories in the sprint that are in development. * Ready for Testing: Indicates the number stories in the sprint that are ready to be tested. * Testing: Indicates the number of stories in the sprint that are currently being tested. * Complete: Indicates the number of stories in the sprint that are complete. {#agile-development-sprint-dashboard__ul_gjh_lyk_rlb} Note: Stories in Ready and Cancelled states are not included in this report. | [ ] {#agile-development-sprint-dashboard__table_mbk_ndk_k3b} You can customize the Burnup, Burndown, and Cumulative Flow Diagram reports. For more information, see [Customizing Agile 2.0 dashboard reports](https://servicenow-prod.fluidtopics.net/fgfiHGdMqAwg7pqHoRKH0A "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