Article · 5 October 2026 · 4 min read

The sprint page that needs no Jira seats

The people who most wanted to see the sprint were exactly the people who could not: no Jira licence, no dashboard access, and a Confluence page that rendered empty because the macro checks the viewer's permissions, not the author's. The fix was not another subscription. It was one HTML file.

Read-only curiosity, priced per seat

Every path to showing sprint progress outside the engineering team had a toll booth. Subscriptions and dashboards require a login. The Confluence macro renders against whoever is looking, so unlicensed viewers see nothing. Marketplace plugins price by user tier, which means paying engineering-tool money for people who will only ever read. The need was legitimate and simple: leadership wanting to follow the work. The market's answer was seats.

One file, everything in it

So we built the boring alternative: a small tool that pulls the board's current sprint, next sprint, and unplanned backlog, and renders one self-contained HTML file. No login, no network calls, no external assets. Anyone with the link sees live sprint state, and clicking a ticket opens its full detail: description, subtasks, links, optionally the comments.

Enough analytics to be honest

A static file does not have to be a dumb file. The page carries a burn-up chart, status pills that filter the board, scope and throughput summaries with point totals for the current selection, real names instead of mail handles, and an archive of the year's sprints for comparisons. One deliberate touch: the page flags itself when it is stale, because a snapshot pretending to be live is worse than no page at all.

Where it landed

Hosting is a few lines of Terraform, access is a link, and the audience became exactly who it should have been all along: the whole company. The CEO, the CTO, and the engineering director follow the team through it. Nobody bought a seat to read.