It’s always interesting to talk with others about what you can measure in agile teams and what actually makes sense! For example, I’m a fan of cycle time and opposed to velocity (especially when it’s used across team boundaries).
Cycle time is a nice, simple empirical metric. Velocity is based on gut feeling.
RE: https://mastodon.social/@cylenivo/116441442009420848
If you like the idea of a free open source analytics app for #Jira, #OpenProject and #Trello I would be happy to get a thumbs up on Product Hunt. App available for Windows, Linux and Mac. Thanks!
Cylenivo just launched on Product Hunt!
Free cycle time & lead time analytics for Jira. No cloud, no account. Your data stays local.
Free desktop app to measure cycle time, lead time and throughput from Jira, Trello or OpenProject. Monte Carlo forecasts, flow efficiency, rework detection. No cloud, no account (your data stays local) Built because Jira's built-in reports don't show how long work actually takes. Cylenivo reads every status transition and computes percentiles, trends, and delivery forecasts from your real data. No story points, no velocity - just what actually happened. Free, open source. MIT + Commons Clause.
Tomorrow #Cylenivo launches on Product Hunt. Free cycle time & lead time analytics for #Jira, #Trello and #OpenProject. Local, free, open source, no cloud.
Free desktop app to measure cycle time, lead time and throughput from Jira, Trello or OpenProject. Monte Carlo forecasts, flow efficiency, rework detection. No cloud, no account (your data stays local) Built because Jira's built-in reports don't show how long work actually takes. Cylenivo reads every status transition and computes percentiles, trends, and delivery forecasts from your real data. No story points, no velocity - just what actually happened. Free, open source. MIT + Commons Clause.
Lead time and cycle time are not the same metric. One is the team's number, the other is the stakeholder's number. Most teams only track one and have the wrong conversations because of it.
I wrote about the difference and what to do about it.
https://dev.to/nobsagile/lead-time-vs-cycle-time-what-every-team-lead-should-know-odm
Your team's average cycle time is 8 days. Your P85 is 21.
That's not noise but a process signal. The average hides the tickets that get stuck, blocked, or forgotten.
If you only report the average, you're lying to your stakeholders. With good intentions, but still.
https://cylenivo.org/flow-metrics/
#Cylenivo #Agile #flowmetrics #cycletime #kanban #opensource
Jira tracks every status change. But it doesn't show you how long work actually takes.
I wrote a guide on what cycle time means in Jira, why the built-in reports don't cut it, and how to measure it properly.
Working a bit on AI Insights with local model (gemma4) with some good results!
#Cylenivo #Agile #CycleTime #LeadTime #FOSS #App #Scrum #Kanban
Is #Cylenivo a tool for you to consider? I blogged about it.
https://no-bullshit-agile.com/cylenivo-a-tool-not-a-cockpit.html
Thomas
Cylenivo
