Agile 2.0 Prior Sprint Dashboard

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    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 provides essential data visualizations to help Scrum masters and sprint planners analyze the scope, actual burndown, burnup, and forecast trends of previous sprints. This analysis is crucial for planning upcoming sprints effectively. The dashboard can be accessed viaAll > Agile Development > Dashboards.

    Show full answer Show less

    Key Features

    • Data Visualization: Offers insights into sprint burndown and burnup trends, excluding canceled stories.
    • Indicators: Includes metrics such as total story points for current and active stories, generating scope and completed series for reports.
    • Widgets Breakdown: Features metrics like committed points, stories completed, completed work, and missing estimates.
    • Burndown and Burnup Charts: Line charts illustrating scope changes over time, with options to customize visible series.

    Key Outcomes

    By utilizing the Agile 2.0 Prior Sprint Dashboard, users can:

    • Gain visibility into actual changes in scope and forecast trends from previous sprints.
    • Make informed decisions when planning for upcoming sprints based on burndown and burnup trends.
    • Identify if the team is on track or falling behind schedule, allowing for timely adjustments in workload.

    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 All > Agile Development > Dashboards and select Agile 2.0 Prior Sprint Dashboard.

    Figure 1. Agile 2.0 prior sprint dashboard widgets
    Agile 2.0 prior sprint dashboard widgets.
    Figure 2. Agile 2.0 prior sprint dashboard burndown visualization
    Agile 2.0 prior sprint dashboard burndown report.
    Figure 3. Agile 2.0 prior sprint dashboard burnup visualization
    Agile 2.0 prior sprint dashboard burnup report.
    Note:
    Canceled stories are not included in any of this data.

    End user and roles

    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

    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

    The following are the breakdowns used by the indicators.

    • Scrum: Sprint
    • Scrum: Prior Sprint

    Widgets

    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

    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 Sprint Burnup visualization. For more information, see Upgrading the layout of Agile 2.0 dashboards.

    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.
    • 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.

    Analyze the burndown trends and accordingly plan the workload for an upcoming sprint.

    Sprint Burnup

    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.

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