Agile 2.0 Prior Release Dashboard

  • Release version: Xanadu
  • Updated January 30, 2025
  • 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 Release Dashboard

    The Agile 2.0 Prior Release Dashboard in ServiceNow provides visual insights into the scope, actual burnup and burndown, and forecast trends of past releases. This dashboard helps product owners and scrum teams analyze previous release performance to better plan and manage upcoming releases.

    Show full answer Show less

    Users can access the dashboard by navigating to All > Agile Development > Dashboards and selecting Agile 2.0 Prior Release Dashboard. It excludes canceled stories from its data calculations to ensure accurate metrics.

    Key Features

    • Data Visualizations:
      • Release Burnup Report: A line chart showing burnup trends with series such as Scope (planned work) and Completed (work finished) for the previous release. Users can toggle these series on or off.
      • Release Burndown Report: A line chart displaying scope changes, ideal work completion progress, and actual work completed over time. It includes series for Scope, Ideal Burndown, and Remaining work. Comparing actual versus ideal burndown helps assess if the team was ahead or behind schedule.
    • Widgets:
      • Stories Completed: Total number of stories completed in the prior release.
      • Completed: Total story points completed in the prior release.
      • Missing Estimates: Count of stories missing estimates in the prior release.
    • Role-Based Access: Product owners and scrum users with the scrumuser role can view and analyze this data to track scope changes and delivery trends.
    • Customization: The burnup and burndown reports can be customized to fit specific reporting needs, allowing teams to tailor visualizations to their workflows.

    Key Outcomes

    • Gain clear visibility into how scope changed and work progressed in previous releases.
    • Understand if delivery was on schedule by comparing actual versus ideal burndown trends.
    • Identify missing story estimates to improve future planning accuracy.
    • Leverage historical data to forecast and plan upcoming releases more effectively.

    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.