Dashboard and reporting: see delivery health at a glance

Burndown charts, sprint metrics, and real-time dashboards give your team and stakeholders visibility into what is happening without manual status reports.

The dashboard

The Dashboard is your personal landing page in Flying Donut. It shows a summary of all active projects, sprints, and your current assignments. At a glance you can see which sprints are in progress, what work is assigned to you, and where your attention is needed.

  • Active sprints from all your projects are listed with days remaining
  • Cards assigned to you are highlighted with their current status
  • Click 'Show All' to see the full list of your assignments
  • Kanban boards with work assigned to you are also visible
  • The dashboard updates in real time — no manual refresh needed

Example — Morning check-in: A developer opens Flying Donut and sees the dashboard. Two sprints are active. One has 3 days left with 2 cards assigned. The other has 8 days left with 1 task in progress. The developer clicks the first sprint to focus on finishing the closest deadline.

Burndown charts

Every active and completed sprint has a burndown chart that visualizes remaining work over time. The chart is a core Scrum reporting tool that helps the team assess whether the sprint is on track.

  • Y-axis: total remaining task hours across all sprint cards
  • X-axis: sprint days from start to end date
  • Ideal line: a straight diagonal from total estimate to zero, showing the expected pace
  • Actual line: real remaining hours, updated in real time as tasks are completed
  • When the actual line is above the ideal, the team is behind; below means ahead of schedule

Access the burndown chart from the sprint board toolbar or the sprint list view.

Reading the burndown chart

The burndown chart tells a story about how the sprint is progressing. Here are common patterns and what they mean:

  • Smooth downward slope following the ideal line — the team is on track with consistent progress
  • Flat line for several days then a steep drop — work is being completed in batches, possibly at the end of the sprint (consider smaller task breakdowns)
  • Actual line rises above initial estimate — scope was added mid-sprint (scope creep) or estimates were too low
  • Actual line drops below ideal early — the team is ahead of schedule or estimates were too generous
  • Stair-step pattern — tasks are being completed in bursts, which may indicate dependencies between tasks

Sprint counters and metrics

Beyond the burndown chart, each sprint shows real-time counters:

  • Total cards in the sprint
  • Cards by status: To Do, In Progress, Done
  • Total tasks and task completion percentage
  • Total estimated hours and hours remaining
  • Days left in the sprint (or overdue indicator)
  • Story points committed vs. completed

These metrics are visible in the sprint list, the sprint board header, and the planning view. They update in real time.

Using data for retrospectives

Sprint data is preserved after completion, making it a valuable input for retrospectives. Review past sprints to identify patterns and improve:

  • Compare planned vs. completed story points across several sprints to establish velocity
  • Look at burndown patterns — consistent scope creep suggests refinement needs improvement
  • Check which cards were not completed — were they too large, poorly defined, or blocked?
  • Use Workmate to generate a sprint summary for retrospective preparation
  • Track velocity trends to improve future sprint planning accuracy

Example: Over four sprints, a team finds they consistently complete 80% of committed story points. In sprint five, they commit to 80% of their maximum capacity and deliver 100% — resulting in a more predictable and less stressful sprint.

Custom reporting with the API

For reporting needs beyond the built-in dashboard and burndown chart, use the REST API to extract project data and build custom reports:

  • Export sprint cards and burndown data for external dashboards
  • Build velocity charts tracking story points across sprints
  • Generate throughput metrics for Kanban boards
  • Create executive summaries with card counts, completion rates, and trends
  • Feed data into BI tools like Google Sheets, Grafana, or custom internal dashboards

Common questions

Can I export burndown data?+
Yes. Use the API endpoint GET /api/projects/{projectId}/iterations/{id}/burndown-chart to get burndown data as JSON, including daily remaining hours and original estimates.
Is there a velocity chart built into the product?+
Flying Donut provides sprint-level metrics. For cross-sprint velocity charts, use the API to aggregate data across sprints.
Do completed sprint metrics remain accessible?+
Yes. Completed sprints and their burndown charts are archived and accessible from the Sprints page.
Can I share the dashboard with stakeholders?+
Stakeholders can be added to the project with a Follower role for read-only access to sprints, boards, and dashboards.

Get visibility into your team's delivery health

Real-time dashboards and burndown charts give your team and stakeholders the data they need — without manual status reports.