Skip to content
FlowMetrics

Free during beta

See how work really flows through your team

FlowMetrics turns your Jira history into the flow metrics that matter: throughput, cycle time, work in progress, aging work and service levels. Spot bottlenecks early and make commitments you can keep.

Sign in with your Atlassian account · Read-only access · No credit card

FlowMetricsSample data

Throughput

11.7/ week

+2.1
vs prior 26 weeks

Median cycle time

4.6d

−1.3d
vs prior 26 weeks

Work in progress

9items

−3
since 5 Jan

SLE compliance

86%

+7 pts
Target: 85% within 10d
Preview of the FlowMetrics overview with sample numbers: throughput, median cycle time, work in progress and SLE compliance, plus weekly throughput and cycle time charts.

Why flow metrics

Your board shows what's in progress. Not how work is flowing.

FlowMetrics looks at what actually happened to every work item, straight from Jira's status history, so the conversation moves from opinions to evidence.

Velocity isn't a forecast

Story points and burndowns describe effort, not when work actually finishes. Stakeholders want dates you can stand behind.

Bottlenecks hide in plain sight

Work quietly piles up in Review or Testing long before a sprint goal slips, and nobody sees it in the board.

Old work gets forgotten

Items age in progress for weeks until they turn into the release blocker everyone is suddenly talking about.

Features

Everything a Scrum Master needs to understand delivery

Built on proven flow metrics, presented so you can read them in a stand-up and defend them in a steering meeting.

Throughput

Completed items per week, with the trend against the previous period and a sparkline at a glance.

Cycle time percentiles

Median, 85th and 95th percentile: how long work really takes, outliers included. Never averages.

Bottleneck detection

See which workflow stage absorbs most of the active time, and how many items are waiting there right now.

Aging work in progress

Every open item plotted by status and age, so you can act on work that's at risk before it breaches.

Service level expectations

Set an SLE like “85% within 10 days” and track how often your team actually meets it.

Flow Analysis drill-down

Cycle time scatterplot, WIP and lead time trends, and a searchable issue table that links straight to Jira.

Coming next

Monte Carlo forecasting: “How many items can we deliver by the end of the quarter?”, answered with probabilities instead of guesses.

How it works

From sign-in to insight in about two minutes

  1. Sign in with Atlassian

    Approve read-only access. You only see the projects your own Jira account can already see.

  2. Pick a project, map your workflow

    FlowMetrics suggests a mapping from Jira's status categories. Review it, set your SLE and save.

  3. Sync and see your flow

    Status history imports in seconds. Re-sync whenever you want fresh numbers.

Security & privacy

Your Jira data stays yours

FlowMetrics is built to be safe to try on a real project.

Read-only by design

FlowMetrics asks only for read scopes. It can't create, edit or delete anything in Jira.

Your permissions, your data

Everyone signs in with their own account and sees only their own teams and metrics.

Encrypted and deletable

Access tokens are encrypted on the server. Delete everything FlowMetrics stores about you in one click.

Transparent metrics

Every definition is documented. Percentiles are real observed values, not interpolations.

Free while we build it with you

FlowMetrics is in beta and free to use. We'd rather learn what actually helps your team than send you an invoice. Try it on a real project and tell us what's missing. Your feedback decides what we build next.

FAQ

Questions, answered

Is FlowMetrics really free?

Yes. Every feature is free during the beta, and you don't need a credit card.

Does it change anything in Jira?

No. FlowMetrics only requests read access. It reads issues, statuses and their history, and never writes back.

Which Jira does it work with?

Jira Cloud. Jira Server and Data Center are not supported.

Do I need to be a Jira admin?

No. Any user who can browse a project can analyse it. Some organisations require an admin to approve third-party apps before anyone can sign in.

Who can see my metrics?

Only you. Teams, settings and imported data belong to the account that signed in. They aren't shared with other users.

What data is stored, and can I delete it?

Your Atlassian name and email, your team settings, the issue keys, titles, types and status history needed to compute metrics, and encrypted access tokens. Settings → Delete my data removes all of it.

How are the metrics calculated?

From each issue's status history and your workflow mapping. Cycle time runs from the first Active status to Done, measured in calendar days over complete weeks. Percentiles use the nearest-rank method.

Ready to see your team's flow?

Free during beta. Read-only. Set up in minutes.