Engineering Flow
AI-first executive view · Custom scope · last 30d
AI Bottom Line
Over the last 30 days, this scope delivered 3 issues with very long active flow times; the main constraint is work aging in progress rather than intake or blocked WIP, and AI has no measurable owned contribution in this window.
Headline KPIs · last 30d
AI insight
- Where AI helps:One AI-touched item shows much shorter Jira flow lead time at 15.1 hours, but this is based on a single item and is directional only.
- Where AI hurts:The same AI-touched cohort shows slower time to ready at 5.2 hours, but this is also a single-item result and not decision-grade.
- Next focus:Focus the next review on clearing or re-scoping the three longest in-progress incidents before adding more active work.
AI in teams · 1 team
3 completed · 33.3% AI-touched · 1 active agent
Bottom line
IMC improved (50.0%) in throughput. AI cohort too small for cycle comparison (n=0/2); no specific AI bottleneck stands out.
Issues done
3
+50.0% vs prev
AI-owned share
0%
+0.0 pp vs prev
AI-touched
1 (33%)
Lead Time (active)
69.1d
prev 23.4d
Cycle Time (active)
31.7d
TTR p50
0.5h
prev 15.5d
PR Review p50
—
WIP active
3
WIP blocked
0
AI insight
Where AI helps
No AI-owned metric is currently faster than the human cohort.
Where AI hurts
No AI-owned metric is currently slower than the human cohort.
AI cohort too small for direct comparison on this team.
Top AI bottleneck
no AI-owned cohort with stage data
Active agents · top 1
Active bottlenecks · top 5
Top teams · by throughput
| Key | Team | Throughput | Lead Time (active) | Cycle Time (active) | Active WIP | Blocked WIP | AI % |
|---|---|---|---|---|---|---|---|
| IMC | [Engineering]: Incident Management | 3 | 69.1d | 31.7d | 3 | 0 | 0% |