Engineering Flow
AI-first executive view · Custom scope · last 30d
AI Bottom Line
AI-narratedcached· 2026-07-21 00:30 UTC
Delivery slowed this period: completed work fell to 8 issues, median Jira flow lead time was 105.8 hours, active WIP remained high at 61 items, and the dominant flow constraint is work sitting On Hold and Ready For Review.
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
8▼ 33.3%
Last 8w
AI participation
0.0%—
Last 8w
Lead Time (active)
4.4d▲ 26.3%
no trend
Cycle Time (active)
4.9d▲ 262.5%
Last 8w
AI insight
- Where AI helps:No AI-owned work was completed, so there is no observed area of AI benefit in this period.
- Where AI hurts:No direct delivery downside from AI is visible because AI participation was 0% and no agent activity is recorded.
- Next focus:Run a focused aging-WIP review on On Hold and Ready For Review items, starting with the longest-stuck tickets, and either unblock, ship, or remove them from active flow.
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
On Hold
637.8dp50
Ready For Review
344.6dp50
Ready To Test
35.6dp50
Ready For Live
32.3dp50
In Testing
8.4dp50
Top teams · by throughput
| Key | Team | Throughput | Lead Time (active) | Cycle Time (active) | Active WIP | Blocked WIP | AI % |
|---|---|---|---|---|---|---|---|
| TECH | Tech Services | 9 | 5d | 4.9d | 61 | 11 | 0% |
Data quality⚠ amber
⚠ Sync freshness1/1 synced
✓ Latest sync1/1 OK
✓ Config coverageall configured
✓ PR linkageno PR data