Mastodawn

How and When to Use AI to Diagnose & Avoid Common Agility Problems, Part 3
https://www.jrothman.com/mpd/2026/06/how-and-when-to-use-ai-to-diagnose-avoid-common-agility-problems-part-3/
#CycleTime #LLM

How and When to Use AI to Diagnose & Avoid Common Agility Problems, Part 3 - Johanna Rothman

I started this series discussing where AI use might create bottlenecks. The more people work solo on anything, the more likely they become bottlenecks for the team. When each person works solo with AI, they reinforce resource efficiency, where everyone is busy, but the team can't seem to finish anything when anyone wants it. Instead, […]

Johanna Rothman

Johanna Rothman Jun 16

How to Diagnose the Bottlenecks In Your Team to Reduce Cycle Time, Part 2
https://www.jrothman.com/mpd/agile/2026/06/how-to-diagnose-the-bottlenecks-in-your-team-to-reduce-cycle-time-part-2/
#CycleTime

How to Diagnose the Bottlenecks In Your Team to Reduce Cycle Time, Part 2 - Johanna Rothman

In How to Use Value Stream Maps to See Where AI Creates Bottlenecks Part 1, I described three teams that used LLMs. However, those teams only used LLMs as individuals, reinforcing resource-efficiency thinking instead of flow-efficiency thinking. (Resource efficiency makes everything take longer because of the focus on the individual. Flow efficiency allows the work […]

Johanna Rothman

Johanna Rothman Jun 10

How to Use Value Stream Maps to See Where AI Creates Bottlenecks, Part 1
https://www.jrothman.com/mpd/2026/06/how-to-use-value-stream-maps-to-see-where-ai-creates-bottlenecks-part-1/
#AI #CycleTime

How to Use Value Stream Maps to See Where AI Creates Bottlenecks, Part 1 - Johanna Rothman

So many people (and some teams) work under mandates to “use AI.” While I am a fan of these two functions for the current LLMs: The ability to create fast prototypes for human assessment and judgment. And the ability to gain new insights into you, your team's, or your organization's data. (This often requires a […]

Johanna Rothman

Thomas ◉ no agile theater May 6

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.

#agile #cycletime #velocity

Thomas ◉ no agile theater Apr 21

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!

#agile #app #cycletime #leadTime #kanban

Cylenivo Apr 21

Cylenivo just launched on Product Hunt!

Free cycle time & lead time analytics for Jira. No cloud, no account. Your data stays local.

https://www.producthunt.com/products/cylenivo

#flowmetrics #cycletime #kanban #opensource

Cylenivo: Free cycle time & lead time analytics for Jira. No cloud. | Product Hunt

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.

Product Hunt

Cylenivo Apr 20

Tomorrow #Cylenivo launches on Product Hunt. Free cycle time & lead time analytics for #Jira, #Trello and #OpenProject. Local, free, open source, no cloud.

https://www.producthunt.com/products/cylenivo

#flowmetrics #cycletime #leadtime #kanban #opensource

Cylenivo: Free cycle time & lead time analytics for Jira. No cloud. | Product Hunt

Product Hunt

Cylenivo Apr 20

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

#flowmetrics #cycletime #kanban #opensource

Lead Time vs Cycle Time: What Every Team Lead Should Know

Both measure how long work takes. But they answer different questions and confusing them leads to...

DEV Community

Cylenivo Apr 20

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

Flow Metrics Explained: Cycle Time, Lead Time, Throughput, WIP — Cylenivo

What are flow metrics and why do they matter? A practical guide to cycle time, lead time, throughput, WIP, and flow efficiency for software teams.

Cylenivo Apr 19

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.

https://cylenivo.org/cycle-time-jira/

#cycletime #jira #flowmetrics #kanban

How to Measure Cycle Time in Jira (Free Tool) — Cylenivo

Learn what cycle time means in Jira, how to measure it from status transitions, and why Jira's built-in reports fall short. Free desktop tool included.