quick-green · weekly tech-ops
Tech-OPs KPIs06.10.2026 - 12.10.2026 · inclusive
Slack Linear Better Stack
Lines under each KPI show the last eleven reporting weeks - 21.7 · 28.7 · 4.8 · 11.8 · 18.8 · 25.8 · 1.9 · 15.9 · 22.9 · 29.9 · 6.10 - current week marked; hover a point for its value. 8-14.9 was not reported. Windows vary, the flow definition changed on 21.7.
ops & reliability · delta vs prev week (29.09-05.10)
▼ 38%
10
Ops support
threads · Slack
flow · linear · delta vs prev week
▼ 30%
19
Issues shipped
Ready4Live / Deployed / Done
▼ 4%
22
Estimated points
across the 19 issues
▼ 40%
6 · 32%
Urgent or Bug
of 19 shipped
▼ 20%
5.2d
Avg cycle time
Ready for Dev → target · 15 of 19
Cycle time is 5.2d across 15 issues. Points-per-issue sits at ~1.2. Flow counts Done since 21.7, so it is not fully like-for-like with weeks before then.
Observation
06.10 - 12.10
- Flow normalised after last week's release-batch spike. 19 shipped / 22 points is back to a typical week, following the 27-issue Friday-deploy anomaly. Points-per-issue sits at ~1.16, in line with recent weeks.
- Cycle time (5.25d, n=15) sits mid-pack, but two long-queued doctors-app tickets pull it up. QG-1020 and QG-1021 both sat in Ready for Dev. since 21.09 (~17 days) before moving this week; the rest of the batch cleared in under 10 days, several same-day. 4 of 19 shipped issues have no Ready for Dev. transition in history and are excluded from the average.
- Ops support returned to a normal mix after last week's onboarding wave. Pharmacy onboarding continued (Hinrichsen Apotheke's two-phase go-live, iPunkt Augsburg, Adler Wiesbaden going live), but the bigger story is a root-caused Grüne Blüte bug: products missing a flowzz ID create duplicates instead of merging, and ops is manually backfilling hundreds of IDs.