Retrospectives on real flow metrics from Jira
Sprintlens turns your Jira issue history into clear metrics — Lead Time, Flow Efficiency, bottlenecks — and runs the team retro in real time: a board on everyone's screen, voting and warm-ups. Decisions on facts, not feelings.
Three steps to a data-driven retro
Connect Jira
A secure connection to your Jira instance. Tokens stay on the server, read-only access.
Collect metrics
Pick a team and a sprint — Sprintlens builds flow metrics from the issue history in seconds.
Run the retro
Discuss the data, collect cards and action items. Decisions on facts, not feelings.
Works with your Jira — cloud and corporate
Two ways to connect. Both are read-only: tokens are encrypted and stay on the server.
Corporate Jira Data Center / Server
On-premSign in with a Personal Access Token, with Sprintlens deployed inside your company's network.
- Sign-in: Personal Access Token (Bearer)
- Self-hosted REST API v2
- Sprintlens on-prem — data never leaves your perimeter
Jira Cloud
CloudConnect with your Atlassian account email and an API token.
- Sign-in: email + API token
- Atlassian REST API v3
- Metrics from your Jira cloud in seconds
In both modes access is strictly read-only: Sprintlens never writes to your Jira. Tokens are encrypted (AES-256) and kept on the server only.
Real screens, real metrics
Live from the demo — you'll see the same data for your team after connecting Jira.
Flow analysis
The Cumulative Flow Diagram and time-in-status reveal the bottleneck — here it's Code Review.
Epic analysis
Each epic's contribution to flow: Lead/Cycle Time, progress, time per status and blockers.
Retro board
Columns, voting and action items. Cards with metrics are pulled in automatically.
Your data stays in control
Security by default: per-organization isolation, read-only Jira and encrypted secrets.
Read-only Jira
Sprintlens only reads issue history and never writes to your Jira.
Token encryption
Jira secrets (API token / PAT) are encrypted with AES-256 and kept on the server only.
SSRF guard
The Jira address is checked before every request — loopback, private and metadata addresses are blocked.
Per-organization isolation (RLS)
Each organization's data is isolated at the Postgres database level (Row-Level Security).
Realtime isolation
Live retro, presence and activities are visible only within your organization.
Sessions and SSO
Sign-in via an HttpOnly session, with optional SSO — Google, Atlassian, GitHub.
The same retro — minus the busywork and the guesswork
Hours on exports, Excel and Miro, and the decisions still come down to gut feel. Sprintlens removes the prep, puts facts at the center — and brings the team back into the conversation.
Everything to make retro change team behavior
From raw Jira data to concrete decisions. Metrics, bottlenecks and trends in one tool.
Flow metrics from real Jira
Lead Time, Cycle Time, time in each status and throughput — computed from the issue transition history (changelog), not guessed.
Bottlenecks at a glance
The Cumulative Flow Diagram and a per-status breakdown show where work gets stuck — Code Review, QA or waiting.
Flow Efficiency and health
A flow-health index and the share of active vs waiting time — one look at the team's state.
Trends across sprints
Lead Time dynamics (median, p85, p95) and throughput over closed sprints — see whether the team is improving.
Epic breakdown
Each epic's contribution to flow: Lead/Cycle Time, progress, time per status and blockers — instantly see which big piece of work is slowing the sprint.
Auto-observations → retro cards
The system highlights anomalies and adds them to the retro as cards in one click. Nothing gets lost.
The whole team in one retro — in real time
A board on everyone's own screen, votes and cards in sync, and warm-ups that turn a call into a real meeting.
A retro on everyone's screen
A live board over WebSocket: cards, columns and any change appear for every participant instantly. No more one person "driving" a single screen.
Together and at once
As you type a card others see "who's typing", votes are counted per participant, drag-and-drop columns and a "who's online" list.
The "Spy" game
A detective warm-up: the server deals roles privately to each player, a shared timer, and a discussion and reveal at the end. Everyone plays from their own device.
Mood check-in
Everyone marks their mood at the same time — you get the team mood and a breakdown. A quick warm-up without "pass the laptop".
Wheel of fortune
A random participant picker — who speaks next or who gets the task. The facilitator spins, the result is the same for everyone.
The facilitator runs the session
With one button the facilitator starts the retro and launches activities — they open for the whole team in sync, in one rhythm.
Cloud or on your own servers
Start in our cloud or deploy Sprintlens inside your company under a license.
Pro
For growing product teams and several boards.
- Multiple teams and boards
- Trends across sprints
- Auto-observations and export
- Priority support
Enterprise · On-prem
Deployment on your own servers under a license.
- Installation in your environment
- License key and SLA
- Full setup guide