Sprint Burndown

Overview

Sprint Burndown shows how much work remains in the current sprint vs. how much time is left. It answers the most common sprint question: are we on track?

Koalr computes burndown from your connected issue tracker (Jira or Linear) and updates in real time as issues are completed, added, or rescoped.

Data sources

• Jira — Sprint board, story points, issue status transitions, sprint start/end dates
• Linear — Cycle (Linear's equivalent to sprints), issue estimates, completion events

Koalr reads sprint data via integration APIs on every sync cycle (every 15 minutes during business hours).

How burndown is computed

Ideal burndown line

Remaining work at day D = total sprint points × (sprint_end − D) / sprint_duration

This is the "ideal" slope — if the team burns down work perfectly linearly, remaining points should follow this line.

Actual burndown line

Koalr tracks actual remaining points at the end of each business day:

Remaining at day D = total sprint points − completed points as of end of day D

Scope changes

When issues are added or removed from a sprint mid-sprint, Koalr annotates the burndown chart with a scope change event. This is critical — a burndown that looks "behind" may actually be on track if scope was added.

Dashboard sections

Sprint summary header

• Sprint name and date range
• Total story points planned
• Completed points and percentage
• Remaining points
• Days left in sprint
• On-track indicator — whether the actual burndown is above or below the ideal line

Burndown chart

Line chart showing:

• Ideal burndown (dashed line) — expected remaining points if work flows linearly
• Actual burndown (solid line) — actual remaining points per day
• Scope change annotations — vertical markers when issues are added or removed

Reading the chart:

• Actual line above ideal → behind schedule
• Actual line below ideal → ahead of schedule
• Flat actual line → no completions; potential blocker

Issue breakdown table

All sprint issues with:

• Issue key, title, assignee
• Story points
• Status (To Do / In Progress / Done)
• Days in current status (surfacing stalled items)
• Link to Jira/Linear issue

Sprint history

Previous 5 completed sprints with:

• Completion rate (% of planned points completed)
• Scope change size
• Velocity (points completed per sprint)

Multi-team sprints

If you track multiple teams, use the team filter at the top of the page to switch between team sprint views. Each team runs independent sprints in Koalr.

Forecasting sprint completion

Koalr provides a simple completion forecast:

Projected completion = remaining points / (completed points / elapsed sprint days)

If the team's burn rate is consistent, this forecast shows whether remaining work will complete before sprint end. Displayed as a projected end date relative to the planned sprint end.

Relationship to other metrics

• Sprint Volatility — measures how stable sprint scope is across sprints (Sprint Volatility)
• PR Velocity — PR throughput rate correlates with sprint completion rate (PR Velocity)
• WIP Limits — high WIP mid-sprint is a leading indicator of missed sprint goals (WIP Limits)
• Forecasting — longer-range delivery forecasting built on sprint velocity data (Forecasting)