Projects dashboard template

Sprint Agile Delivery Dashboard Template

Sprint is a single-file HTML dashboard for a software team mid-sprint: kanban board, burndown, pull request review, CI quality, velocity, and retro actions.

Sprint is a software delivery dashboard template delivered as one self-contained HTML file. It shows a fictional team, Team Kestrel, on day 7 of 10 in Sprint 34, with the sprint goal pinned in the header: ship the billing-migration cutover. Five tabs organize the page, Board, Burndown, Code Review, Quality, and Velocity & Retro, covering the full loop from committed work to retro commitments.

The Board tab is a kanban where tickets carry feature, bug, and chore labels, and clicking a ticket opens a detail pane with owner, estimate, age in column, and the standup note. The Burndown tab plots points remaining against the ideal line, next to a scope ledger that records every change after commitment with day, points, and forecast impact. The Code Review tab holds a sortable table of open pull requests and a review latency chart for the last 20 PRs, where the median is 3.1 hours against a target under 4. The Quality tab lists failing and flaky tests from CI on the main branch over the trailing 7 days, plus a deploy log for the sprint with rollbacks marked. The Velocity tab charts committed vs completed points across the last 8 sprints and closes with the carried retro actions from Sprint 33.

What is inside Sprint

Sprint header with team name, sprint number, day 7 of 10, the sprint goal, and standup notes timestamp
Kanban board with feature, bug, and chore labels and a click-through ticket detail pane (owner, estimate, age in column, standup note)
Burndown chart of points remaining vs the ideal line for day 7 of 10
Scope ledger table logging changes after commitment with day, points, and forecast impact
Sortable open pull request table with title, author, lines changed, age in hours, and state
Review latency chart for the last 20 PRs, median 3.1 hours vs a target under 4, with the worst offender flagged red
Nudge panel for PRs past the 24-hour courtesy line, with an action to post review reminders
Failing and flaky tests table from CI on main, trailing 7 days, with fail rate, owner, and status
Deploy log for the sprint with production deploys and rollbacks marked
Velocity chart of committed vs completed points across the last 8 sprints, plus the Sprint 33 retro action table

Specifications

Format	Single self-contained HTML file; zero dependencies, no build step
Theme	Whiteboard Marker
Mood	Light
Category	Projects
Price	$6.99, one-time

Who Sprint is for

Sprint serves scrum masters and agile coaches, who use the burndown and scope ledger to separate a slow sprint from a growing one.

Engineering managers use review latency and the flaky test table to clear the two things that stall delivery: unreviewed PRs and unreliable CI.

Tech leads work the open PR table, sorted by age, and use the nudge reminder for PRs past the 24-hour courtesy line.

Product owners read the board by label to see how much of the sprint is features versus bugs and chores.

The whole team uses the velocity chart and retro action list during the retrospective, since both are already on the same page.

When to reach for it

Sprint fits teams whose standup opens three tools to answer one question. The template puts the board, the burndown, and the PR queue in one file, so the daily meeting reads one screen.

It replaces the sprint-review slide deck: velocity over 8 sprints and the carried retro actions are already charted, so the review meeting starts from the page.

It suits teams of roughly 5 to 12 people running two-week sprints who want a delivery dashboard without a Jira dashboard config or a BI layer.

Frequently asked questions

Does Sprint sync with Jira or GitHub?

No, Sprint does not sync with Jira or GitHub. Sprint is a static single-file HTML template with realistic sample data for one team. Tickets, PRs, tests, and velocity points are arrays in the file that you edit by hand or generate from your own tooling before publishing the page.

What does the scope ledger track?

The scope ledger tracks every change made after sprint commitment: the day it happened, what changed, the points involved, and the forecast impact. The ledger sits beside the burndown so a flat line caused by added scope reads differently from a stall.

Which agile metrics are charted?

Sprint charts points remaining vs ideal, review latency with a 3.1-hour median, flaky test fail rates over 7 days, deploy results for the sprint, and committed vs completed velocity across 8 sprints. Retro actions get a table, not a chart.

Can I use it for Kanban instead of sprints?

Partly yes, you can use Sprint for Kanban instead of sprints. The board, PR review, and quality tabs work for continuous flow. The burndown, scope ledger, and velocity tabs assume timeboxed sprints, so a Kanban team would hide or repurpose those sections, which is a small edit to the tab markup.