Sprint Tracking Report

Last updated: March 9, 2026

Overview

The Sprint Tracking Report gives engineering teams a comprehensive view of sprint execution and planning predictability. It tracks how work progresses through a sprint cycle — from what was planned to what was completed, rolled over, blocked, or added mid-sprint — helping teams understand and improve their delivery consistency over time.

How to Access

Navigate to Productivity → Velocity → Predictability in the left-hand sidebar.

The report is scoped to the team or group you're currently viewing. You can switch teams using the team selector at the top of the page.

Selecting a Sprint

Use the sprint selector dropdown at the top of the report to choose which sprint to analyze. The report will load all metrics and breakdowns for the selected sprint.

Sprint Breakdown Table

The core of the report is the Sprint Breakdown Table, which shows key sprint metrics as both point-in-time values and trend charts across recent sprints. Each row represents one metric:

Column

Description

Planned Completed (%)

The percentage of completed work that was planned at the start of the sprint. Calculated as: Planned Completed ÷ Total Completed. This is the primary planning accuracy signal.

Total Completed

All issues or story points completed during the sprint, regardless of whether they were originally planned.

Planned Completed

Issues or story points that were both in the original sprint plan and completed by sprint end.

Unplanned Completed

Issues or story points completed during the sprint that were not in the original plan — i.e., work added mid-sprint.

Rollover

Issues that were planned at sprint start but were not completed by sprint end, and carried forward to the next sprint.

Blocked

Issues in a "Blocked" status at the end of the sprint cycle.

In Progress

Issues still actively being worked on at the end of the sprint.

In Review

Issues awaiting review at the end of the sprint.

Investment

FTE-days invested during the sprint (requires investment reporting to be configured).

Issue Cycle Time

Average time from issue creation to completion for issues closed during the sprint.

Planning Accuracy

Planning accuracy is the flagship metric of the Sprint Tracking Report. It measures how predictable your team's sprint planning is.

Two calculation methods are available:

  • Issues Planning Accuracy — Total Planned Issues Completed ÷ Total Planned Issues

  • Estimate Planning Accuracy — Total Planned Story Points Completed ÷ Total Planned Story Points

Both are expressed as a percentage (0–100%). A higher score indicates that the team is completing what it commits to. Lower scores can point to scope creep, underestimation, or external blockers.

Note: You can configure whether "In Progress" and "In Review" issues at sprint end are included in planning accuracy calculations via Display Settings.

Display Settings

Click the Display Settings button to customize your view. Settings are personal and don't affect what others see.

Setting

Description

Issues Unit

Toggle between viewing metrics by issue count or story points.

Include Issues Assigned to Non-Team Members

When enabled, includes issues from the sprint that are assigned to people outside the selected team.

Investment Framework

Select which focus area framework to use for the investment breakdown (if multiple are configured).

Planning Accuracy Calculation

Choose whether to count "In Progress" and "In Review" issues toward planning accuracy.

Investment Breakdown

If your organization has focus areas configured and you have investment reporting permissions, an Investment Breakdown section will appear below the sprint breakdown table. It shows how sprint work was distributed across your strategic investment categories, making it easy to see whether sprint execution aligned with intended allocation.

Exploring Issues

Click on any status category in the breakdown table to open the Issue Drawer — an interactive side panel showing:

  • The full list of issues in that category

  • Direct links to each issue in your issue tracker (e.g., Jira, Linear)

  • A breakdown by assignee

  • Cycle time per issue

  • A link to open the full sprint issues view in a new tab

Required Permissions

Action

Permission Required

View Sprint Tracking Report

Issue Tracking Report access

View Investment Breakdown

Investment Report access

Enable / configure sprint tracking for a team

Team Management access

If you are missing data for certain teams or individuals, a permission alert will appear in the report indicating what access is restricted.

Tips for Getting the Most Out of Sprint Tracking

  • Track trends, not just snapshots. The trend charts next to each metric let you see how your team's planning accuracy and completion rates are improving (or declining) sprint-over-sprint.

  • Investigate blockers early. High "Blocked" or "In Review" counts at sprint end are signals to examine your review and dependency management processes.

  • Use rollover to improve estimation. A consistently high rollover count may indicate over-commitment. Use this data in retrospectives to right-size sprint scope.

  • Compare planned vs. unplanned completion. A high proportion of "Unplanned Completed" work can indicate reactive work patterns or poor backlog management.

  • Correlate with investment. Use the Investment Breakdown alongside sprint metrics to understand whether sprint effort is aligned with strategic priorities.

Related Reports

  • Issue Lifecycle Report — Track individual issues across all time, not scoped to sprint boundaries.

  • Issue Throughput Report — Measure issue completion rates globally, without sprint-based scoping.

  • Allocation Reports — Understand how engineering time is distributed across investment categories over longer time horizons.