quick-green · weekly tech-ops
Tech-OPs KPIs29.09.2026 - 05.10.2026 · inclusive
Slack Linear Better Stack
Lines under each KPI show the last eleven reporting weeks - 13.7 · 21.7 · 28.7 · 4.8 · 11.8 · 18.8 · 25.8 · 1.9 · 15.9 · 22.9 · 29.9 - 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 (22.09-28.09)
▲ 700%
16
Ops support
threads · Slack
flow · linear · delta vs prev week
▲ 80%
27
Issues shipped
Ready4Live / Deployed / Done
▲ 64%
23
Estimated points
across the 27 issues
▲ 100%
10 · 37%
Urgent or Bug
of 27 shipped
▲ 61%
6.5d
Avg cycle time
Ready for Dev → target · 18 of 27
Cycle time is 6.5d across 18 issues. Points-per-issue sits at ~0.9. Flow counts Done since 21.7, so it is not fully like-for-like with weeks before then.
Observation
29.09 - 05.10
- Shipped jumped to 27, but it's mostly a release-batch artifact. 14 of the 27 issues entered Ready4Live late Friday and were bulk-deployed Monday morning; without that batch this reads as a normal ~13-issue week. Points-per-issue fell to ~0.85 (from ~1.6 last week), confirming it's volume of small items rather than bigger work.
- Cycle time rose to 6.5d on a thinner, skewed sample. Only 18 of 27 issues have a usable Ready for Dev. transition (8 skipped it entirely, 1 excluded as a bulk status correction); a couple of long-dwelling backlog items (QG-1005, QG-1008, ~18 days each) pull the average up, while most of the Friday batch moved in 1-5 days.
- Ops support rebounded to 16 threads, led by pharmacy onboarding. Five of the week's asks were new-pharmacy or zip-code setup requests as onboarding ramps up; the rest were the usual bug/question mix, including a recurring theme of customers landing on the wrong (DHL) pharmacy in the multi-pharmacy marketplace view.