Overview
How the team is doing and where AI is showing up.
Period
Scope
Filters
Right now · Last 30d
Issues done
105
▼ 53.7%
AI participation
0.0%
▼ 6.2%
Lead Time (active)
4.7d
▼ 33.7%
Cycle Time (active)
1.6d
▼ 71.1%
Time to Ready p50
2.8d
▲ 181.2%
WIP active
252
▲ 6.8%
WIP blocked
65
▲ 1.6%
Deploys / week
4.9
▼ 38.0%
Bug rate / week
3.3
▼ 82.1%
Trend · last 8 weeks
Throughput
AI %
Cycle Time (active, h)
AI impact
MetricAI medianHuman medianΔ%
Cycle Time (active)AI: —n=0Human: 1.6dn=104⚠ n<20
Lead Time (active)AI: —n=0Human: 4.7dn=105⚠ n<20
Time to Ready p50AI: —n=0Human: 2.8dn=105⚠ n<20
PRs mergedAI: 0Human: 30—
PR review p50AI: —n=0Human: 3.1hn=7⚠ n<20
Before vs After AI
| Metric | Before AI | After AI | Δ |
|---|---|---|---|
| Lead time p50 (raw, days) | 19.2dn=2405 | 8.4dn=994 | ▼ 56.3% |
| Throughput / week | 12.5n=2405 | 14.6n=994 | ▲ 17.3% |
| AI participation (%) | 0n=2405 | 12.6n=994 | — |
| Deploys / week | 0.2n=9 | 2.1n=122 | ⚠ |
| Change failure rate (%) | 18.2n=11 | 33n=182 | ⚠ |
Per-project breakdown (2 projects)
mode: compare
Before AI55 weeks · n=193
- Lead Time (raw)
- 23d
- Throughput / wk
- 3.5
- AI %
- 0%
- Deploys / wk
- 0.2
- Change fail rate
- 18.2%
- Deployments
- 11
After AI59 weeks · n=481
- Lead Time (raw)
- 5.8d
- Throughput / wk
- 8.1
- AI %
- 4.6%
- Deploys / wk
- 2.1
- Change fail rate
- 33%
- Deployments
- 182
mode: compare
Before AI103 weeks · n=2212
- Lead Time (raw)
- 15.3d
- Throughput / wk
- 21.4
- AI %
- 0%
- Deploys / wk
- —
- Change fail rate
- —
- Deployments
- 0
After AI24 weeks · n=513
- Lead Time (raw)
- 11d
- Throughput / wk
- 21.1
- AI %
- 20.5%
- Deploys / wk
- —
- Change fail rate
- —
- Deployments
- 0
Tip: switch any project to Before only / After only in its config to focus on one era — useful when one side has insufficient data or contaminated history.
Top teams · by throughput
AI activity · how agents are being used
| Agent | Assigned | Authored PRs | Reported | Transitions | Comments |
|---|---|---|---|---|---|
| Oliver | 0 | 2 | 0 | 19 | 42 |
| Nikolaos | 0 | 0 | 0 | 0 | 36 |
| Amelia | 0 | 0 | 0 | 0 | 0 |
| Anastasia | 0 | 0 | 0 | 0 | 0 |
| Sakura | 0 | 0 | 0 | 0 | 0 |
| Veronica (ADOMCPAutomation) | 0 | 0 | 0 | 0 | 0 |
| Robocop | 0 | 0 | 0 | 0 | 0 |
| Total | 0 | 2 | 0 | 19 | 78 |
Data Quality
| Check | Status | Current value | What it means |
|---|---|---|---|
| Sync freshness | ⚠ | 6/6 projects · 6 stale > 24h · oldest PU 890.5h | How recently we pulled JIRA data. Stale > 24h means the numbers in this scope may be lagging real-world state. |
| Latest sync status | ✓ | 6/6 projects last sync OK | Whether each project's most recentsync succeeded. This is the current-health signal: if green, every project's data is fresh from a successful pull, even if older runs in the 24h window failed. |
| Historical errors (last 24h) | ✓ | 0 | Count of failed sync attempts in the last 24h. Transient noise unless Latest sync status above is also red — then a project is currently broken, not just blipped. |
| Metric configs | ✓ | all projects fully configured | Each project has 11 metric definitions (start/end statuses, ready statuses, etc.). All projects fully configured means cycle/lead/WIP/throughput/etc. use the project-specific status lists, not fallback defaults. |
| AI Period coverage | ✓ | 2/6 projects configured | Number of projects where someone clicked 'Compare' on the project's config page and set an AI introduction date. Drives the 'Before vs After AI' section below. Most projects can stay unconfigured — only opt in for projects where you actually want a before/after split. |
| Stage config coverage | ⚠ | 1 status missing from 1 project' configs · 0 wip configs missing pauseStatuses | Configs must list every status the team actually uses. Otherwise Where Work Waits and Blocked WIP silently drop transitions. Audit17 P0-3. |
| PR ↔ JIRA linkage (last 30d) | ✓ | ADS 76.7% (23/30) | Share of completed PRs whose branch name or title contains a JIRA issue key (e.g. ADS-1234). Below 60% means the PR/JIRA join is unreliable for that project — for those, quote PR-only metrics (PR Throughput, Review Duration) instead of metrics that join PRs back to JIRA tickets. |
Where work waits
Bottleneck: tickets spend the most time in Waiting for Client (78d median). This is the top of Active Flow Bottlenecks, not the intake card.
Active Flow Bottlenecks
Workflow stageRelative wait timeMedian time
Waiting for Client
78dp50
Ready For Staging
4.5dp50
PM/Client Review
2.7dp50
Failed On Testing
1.8dp50
On Hold
1.8dp50
Ready For Canary
1.4dp50
Backlog / Intake Aging
Workflow stageRelative wait timeMedian time
New
97.7dp50
Approved for Sprint
81.8dp50
Approved
36.7dp50
Open
34.4dp50
To Do
12.8dp50
Triaged
5.3dp50
Longest stuck right now
| Key | Summary | Status | Age |
|---|---|---|---|
| PU-169 | 8 Ball Pool Together - launch stand-alone 8 ball Pool Together | In Progress | 788.2d |
| PU-126 | Premier Sunday Crossword - Solve source of puzzle feeds | Ready For Live | 788.2d |
| PU-177 | Crosswords - high priority maintenance and improvements | In Progress | 788.2d |
| PU-81 | AARP all games - adaptive sampling | Ready For Review | 788.2d |
| PU-95 | Let's Block Champ - Release Request 15 | Failed On Testing | 788.2d |
| PU-151 | Outspell - Core Gameplay | Ready To Test | 788.2d |
| PU-161 | Outspell - Sounds | Ready To Test | 788.2d |
| PU-170 | Outspell - UI Preloader Screen | Ready To Test | 788.2d |
19 tickets excluded — managed centrally.
133 tickets excluded — managed centrally.