Engineering Flow
AI-first executive view · Custom scope · last 30d
AI Bottom Line
AI-narratedcached· 2026-07-21 09:39 UTC
Flow is effectively stalled this period: no issues were completed or deployed, while active and blocked work remain high.
AI ROI: data insufficient for the last 30d. 1 project in scope, none with stable AI vs Human cohort (n≥10 both sides) on Lead Time.
Investigate per project →Headline KPIs · last 30d
Issues done
0▼ 100.0%
no trend
AI participation
0.0%▼ 100.0%
no trend
Lead Time (active)
——
no trend
Cycle Time (active)
——
no trend
AI insight
- Where AI helps:None observable in this period: AI participation is 0% and there are no AI-owned completed samples.
- Where AI hurts:AI is not affecting outcomes here because there is no recorded AI activity or ownership in scope.
- Next focus:Triage and close or reclassify long-stuck In Progress items, then review the blocked queue as a separate recovery action.
AI in teams · 0 teams
No teams in scope have AI involvement in this window. As soon as an AI agent assignment, comment, transition, or reporter shows up, this section populates.
Active bottlenecks · top 5
Workflow stageRelative wait timeMedian time
In Progress
718.8dp50
On Hold
71dp50
In Testing
57.6dp50
Top teams · by throughput
| Key | Team | Throughput | Lead Time (active) | Cycle Time (active) | Active WIP | Blocked WIP | AI % |
|---|---|---|---|---|---|---|---|
| No teams in scope. | |||||||
Data quality⚠ amber
⚠ Sync freshness1/1 synced
✓ Latest sync1/1 OK
✓ Config coverageall configured
✓ PR linkageno PR data
155 tickets excluded — managed centrally.