Reports & Summary

When it's time to tell the story of a sprint — to stakeholders, in a wiki, or at a retro — the Summary and Reports views turn your captured data into clean narrative.

Summary

The Summary view assembles a comprehensive write-up of the sprint (Scrum) or flow window (Kanban): Overview, Key Metrics, Completed Work, Blockers Encountered, Decisions Made, and Risks Identified — pulled straight from your tickets and notes.

• Scope toggle — produce the summary for the current sprint/iteration, the whole PI, or (for scaled teams) the ART.
• Customize — toggle individual sections on or off to control what appears.
• Export — copy to clipboard or export as Markdown for emails, wikis, or docs.

Sprint report

The Sprint report turns an increment into a polished, shareable document assembled from reusable building blocks — delivery KPIs, charts, and narrative — with the metrics and story pulled together into one page.

• Templates — save a layout once and regenerate it each sprint, so the format stays consistent from one increment to the next.
• Scope — build it for a sprint, a whole PI, or (for scaled teams) the ART.
• Share — publish it to a live, read-only page at its own link, or export it as a PDF or PowerPoint bundle for emails and decks.

For an executive audience, the same increment can be reframed as a stakeholder bundle — the delivery story at a higher altitude:

Impact Summary

The Impact Summary is a personal report a Scrum Master generates about their own contribution over a stretch of time — the kind of write-up you’d bring to a one-on-one, a performance review, or a promotion case. Where the sprint report tells the story of the team’s increment, the Impact Summary tells the story of your impact, shown through the improvement it produced.

• You choose the window and the teams. Generate it across a single PI or Quarter, a range of PIs, or the past year, spanning every team you run — the summary draws on all of them at once.
• First-person and contribution-focused. It reads as a narrative you’d write yourself: what you did — surfaced a risk early, kept a migration coherent, helped a team commit to what it could actually deliver — and the difference it made.
• Anchored in real trends. The story is built on program-level movement across PIs — predictability, cycle time, and epics completed — so improvement is measured where it actually shows, not in one sprint’s wobble.
• Yours to edit. Review the generated themes, swap or drop the supporting examples, and leave feedback to tune future drafts before you finalize.
• Private by design. The Impact Summary is delivered to you as a downloadable PDF — it is never published to a public link and never appears on a shared dashboard. It’s your document, to share as you see fit.

Public dashboard

You can publish a live, read-only dashboard for stakeholders at a shareable URL — no login required. It’s served straight from your team’s current data and refreshes as the data does, so there’s nothing to keep up to date by hand. Access can be left open to anyone with the link or restricted to verified email domains.

The page you’re reading right now is built the same way — a static, shareable site generated from the app’s own content. The public dashboard does the live-data equivalent for a single team.