Sprint Analytics

Sprint Analytics provides visual charts and metrics that reveal how work progresses through your iteration. Burndown charts, burnup charts, and distribution breakdowns transform raw task data into actionable insights.

The Problem This Solves

Looking at a task board tells you current state, but not trajectory. You cannot see whether you are ahead of schedule, falling behind, or experiencing scope creep. Without analytics, sprint reviews become guesswork: "I think we did okay" instead of "Here's exactly what happened."

Sprint Analytics converts your task history into charts that show patterns, problems, and progress. Make data-informed decisions during the sprint and conduct meaningful retrospectives after.

What You Are Looking At

The Analytics tab displays a dashboard of sprint metrics. At the top, a KPI bar shows key numbers at a glance. Below that, charts visualize task completion patterns. Distribution breakdowns reveal how work divides across types, members, and effort levels.

Note: Sprint Analytics is a Pro feature. A badge indicates when subscription upgrade is required.

KPI Stats Bar

The top row displays six key metrics:

Total Tasks: Complete count of tasks assigned to this sprint, regardless of status.

Completed: Number of tasks in "done" workflow states. Compare to total for completion ratio.

Progress: Percentage of tasks completed. Calculated as (completed / total) × 100.

Story Points: Sum of effort points assigned to sprint tasks. Only populated if your project uses point estimation.

Worked Hours: Total time logged against tasks in this sprint. Requires time tracking to be active.

Duration: Number of days in the sprint based on start and end dates.

These metrics update in real-time as tasks change status or time is logged.

Burndown Chart

The burndown chart shows remaining work over time. The Y-axis represents tasks (or points) remaining. The X-axis represents time from sprint start to end.

Ideal line: A diagonal line from total work at sprint start to zero at sprint end. This represents perfectly linear progress.

Actual line: Your real remaining work over time. Shows how progress compares to ideal.

Reading the chart:

Line above ideal: Behind schedule. More work remains than expected.
Line below ideal: Ahead of schedule. Work is completing faster than planned.
Line matches ideal: On track for planned completion.
Flat sections: No tasks completed during that period.
Upward spikes: Scope added mid-sprint (tasks added or reopened).

Burnup Chart

The burnup chart complements burndown by showing completed work accumulating over time.

Scope line: Total sprint scope (all tasks assigned). A flat line means stable scope. Rising line means tasks are being added.

Completed line: Cumulative tasks finished over time. Should rise steadily toward the scope line.

Reading the chart:

Completed approaching scope: Sprint will complete on time.
Completed flat while scope rises: Scope creep outpacing delivery.
Completed rising faster than scope: Team is ahead, or scope is reducing.
Gap at sprint end: Work that did not get done (the remaining tasks).

Burnup is particularly useful when scope changes frequently, as it shows both completion progress and scope expansion simultaneously.

Task Type Distribution

This breakdown shows how sprint work divides across task types (Bug, Feature, Improvement, etc.).

For each type:

Color indicator: Matches the type's configured color
Type name: The task type label
Count: Number of tasks of this type
Percentage: Share of total sprint tasks
Progress bar: Visual representation of percentage

Use cases:

Identify bug-heavy sprints that may indicate quality issues
Track feature versus maintenance ratios
Ensure balanced work distribution

Team Member Distribution

This breakdown shows how tasks distribute across team members.

For each member:

Avatar: Team member's profile image
Name: Team member's name
Count: Tasks assigned to this member
Percentage: Share of total assigned tasks
Progress bar: Visual representation of percentage

Use cases:

Identify unbalanced workloads
Find over-allocated or under-utilized team members
Ensure equitable distribution during planning

Note: Tasks can have multiple assignees, so total assignments may exceed total tasks.

Effort Distribution

If your project uses effort or priority levels, this breakdown shows sprint work by effort category.

For each effort level:

Color indicator: Effort level's configured color
Level name: The effort category label
Count: Tasks at this effort level
Percentage: Share of total sprint tasks

Use cases:

Verify appropriate mix of complex and simple work
Ensure sprint does not contain only difficult tasks
Track effort estimation patterns

Daily Activity Timeline

A timeline view may show task completions per day throughout the sprint:

Bars or markers: Indicate tasks completed each day
Patterns: Reveal work rhythm (steady versus end-loaded)
Gaps: Days with no completions worth investigating

Use cases:

Identify problematic patterns (all work completing last day)
See how weekends or holidays affect progress
Correlate with external events affecting productivity

Velocity Comparison

If available, velocity charts compare this sprint's throughput to historical sprints:

Current sprint: Tasks or points completed
Average velocity: Historical mean
Trend line: Direction of velocity over recent sprints

Use cases:

Understand capacity for future planning
Identify improving or declining team performance
Set realistic expectations for upcoming sprints

Refreshing Data

Click the refresh button in the sub-header to reload all analytics data. Use this when:

Tasks have recently changed status
You want the latest numbers during a meeting
Charts seem stale or outdated

A loading indicator appears while data refreshes.

Using Analytics for Retrospectives

Analytics provide objective data for sprint retrospectives:

Review burndown shape: Was progress steady or end-loaded?
Check for scope creep: Did burnup show expanding scope?
Examine distributions: Was workload balanced? Were types as expected?
Compare velocity: How does this sprint compare to recent history?

Ground discussions in data rather than impressions. "We felt busy" becomes "We completed 23 tasks, 5 above average, but 8 were added mid-sprint."

Pro Tips

Daily check-ins: Review burndown briefly each day to catch problems early
Screenshot for documentation: Capture charts at sprint end for historical records
Combine with qualitative data: Charts show what happened; team discussions explain why
Watch for patterns: Consistent end-loading may indicate estimation or planning issues

How to Report a Problem or Request a Feature

Your feedback matters. Here is how to share it:

If charts display incorrectly, data seems wrong, or you want additional metrics, we want to hear about it.

In the Sidebar, click on Support Tickets and open a ticket for the problem. Everything is interactive and fast through the GitScrum Studio platform.