Cloud closed PI 11 with 17 of 19 sprint goals hit and the release record to match: 3.13.0 tagged in S1, the 3.14.0 final tag in S4, 3.14.0 deployed to production and the 3.16.0 final tag in S6. The team merged 458 merge requests and made 4,983 commits, both its highest in the five PIs measured, on an unchanged six-person roster. Velocity reached 199.6 points, the team's highest since PI 8, and median lead time to production fell by about 38% from PI 10.
| Goal | Target | PI 11 | Status |
|---|---|---|---|
| Sprint and PI goal achievement shared, all team leads | ≥80% hit rate | 17 of 19 goals ticked · 89% | Met |
| Platform release cadence | ≈1 per active sprint (≈5 per PI) | 2 in S1–S5 · 4 across the PI | Missed |
Measured from deployments on cloud-platform-environment, tier production, status success — not from GitLab tags, which can lag a production deploy by weeks. The two inside S1–S5 were 3.12.2 and 3.13.0; 3.14.0 and 3.16.0 reached production during the IP sprint. PI 9 hit this goal at 5; PI 10 was also 2.
Goal achievement of 89% is the team's second-highest in the window and the goals are corroborated by independent release evidence rather than resting on self-report. Every ticked release goal has a matching tag or production deployment inside the same sprint window.
Velocity rose while capacity fell. Capacity came in at 178.8 points across the PI against 222.8 in PI 10, and velocity still went from 164.3 to 199.6 — 112% of capacity, the team's highest ratio in the five-PI window.
Activity rose on every measure: 458 MRs merged against 386 in PI 10, and 4,983 commits against 4,216. Per team member that is an index of 119 on merge requests and 118 on commits, where 100 is the team's own PI 10 level; points per head came in at 121.
S5 is the clearest single sprint. A 19-point commitment met 59.1 points of unplanned work, and the team completed 56 points against 36.6 of capacity.
Total scope surfaced ran at 227% of capacity across S1–S5 — 269 points of commitment plus 133.6 of creep against 178.8 of capacity. Completion ratio sat at 44.3% for the PI, within a point of PI 10's 45.8% and PI 9's 43.1%; the figure has not moved in three PIs.
Platform release cadence came in at two production releases during S1–S5 against a goal of roughly one per active sprint. Two more platform versions, 3.14.0 and 3.16.0, reached production during the IP sprint, so four landed across the PI as a whole.
Median lead time from commit to production was 24 days on cloud-platform-environment and 25 on rest-api, against a 7-day target. That is an improvement on PI 10's 39–40 days and remains well above PI 9's 6 and 15 days.
The two missed goals were both ZBeats: the PDP first approval in S1, which was ticked in S2, and QE runbooks in S6.
Source. prolaio-engineering-metrics.metrics in BigQuery,
pulled 16 October 2026. Ratios are point-weighted across the PI
(SUM(x)/SUM(y)), not averages of per-sprint ratios, and cover all six sprints.
Rate-based goals exclude S6, the IP sprint, and say so where they appear.
Committed Done is work committed at sprint start and completed, at its end-of-sprint estimate. Velocity is committed done plus creep done. Completion ratio and creep ratio share a denominator the team sets at planning and are reported here without a pass/fail judgement.
Sprint goals are parsed from the markdown checkboxes in
sprints.sprint_goal, as the team wrote them. Teams edit these after a sprint closes,
so these figures are as of 16 October 2026.
Per-team-member figures use the delivery roster — engineers, QE and interns, excluding Product Owners and PMO — averaged over the PI's sprints.