Engineering Performance · PI 10 mid-PI brief

Cloud · PI 10 Mid-PI Read-out

PI 10 runs 28 April 2026 to 5 August 2026. As of 11 June 2026, sprints 1-3 are complete and S4 starts shortly. This brief summarises Cloud's progress so far and projects full-PI outcomes at current run-rate.
PI progress
62% active days
Sprints complete
3 of 5 active
Run-rate factor
≈ 1.63×
Today
11 June 2026
Cloud has a strong sprint-level execution rhythm three sprints in. 9 of 9 sprint goals hit. Commitment is closer to capacity than in PI 9. However, platform release deployments are running behind — 1 platform release shipped to production so far (3.10.15.0 on 7 May), with 3.10.16.0 tagged but pending deployment.
Completion vs Commit PROJ
76%
▲ +22pp vs PI 9
Delivery vs Capacity PROJ
93%
▲ +8pp vs PI 9
Sprint Goals Hit
100%
9 of 9 goals · S1-S3
Creep Ratio PROJ
51%
▼ +25pp vs PI 9
Bugs Completed PROJ
23
flat vs PI 9 (21)
Platform Releases (so far)
1
deployed to production · cloud-platform-environment
Merged MRs PROJ
93
▼ -80% vs PI 9 (474) · 57 so far
Capacity, Commitment, Velocity, Creep · PI-level
Story points per PI · velocity = commit_done + creep_done · creep shown as absolute SP · PI 10 projected dashed
Capacity Commitment Velocity Creep
Capacity, Commitment, Velocity, Creep · PI 10 by sprint
Sprint 1-3 actual · S4-S5 planned commitment shown · S6 is the IP sprint · creep in amber
Capacity Commitment Velocity Creep
Creep Ratio · PI-level
creep / commitment · 20% ceiling shown · PI 10 projected dashed
Creep ratio 20% ceiling
Bugs Completed · PI-level
Count per PI · PI 10 projected dashed
Bugs
Platform releases deployed · PI-level
cloud-platform-environment production deployments per PI (the actual release event) · PI 10 includes a projected fill based on current pace
Platform deployments PI 10 projected
Merged MRs · PI-level activity
Count of accepted MRs per PI, attributed by team member. Data available from PI 8 onwards. PI 10 projected dashed.
Merged MRs
Deployments per PI · by tier
Active-period count (excludes IP sprint) · PI 10 so far + projected total
Production Staging
Deployment frequency · by tier
Deploys per active day · 0.5/d is the DORA target
Production Staging 0.5/d target

Final releases this PI

Final releases shipped in PI 10 so far (S1-S3) across all Cloud projects. cloud-platform-environment rows use production deployment dates (the actual release event). Other projects use GitLab tag dates (no deployment tracking). 3.10.14.0 was actually deployed 7 Apr (PI 9) despite the May 7 tag date, so it appears in the PI 9 brief. 3.10.16.0 is tagged but not yet deployed to production.
DateProjectVersion
29 Aprrest-api1.205.10000
6 Mayrest-api1.206.10000
7 Maybeam-processors1.28.0
7 Maycloud-platform-environment3.10.15.0
7 Mayrest-api1.207.10000
8 Mayrest-api1.208.10000
12 Maybeam-processors1.28.1
14 Mayrest-api1.209.10000
22 Mayrest-api1.210.10000
22 Mayrest-api1.211.10000
22 Mayrest-api1.211.10001
22 Mayrest-api1.211.10002
22 Maybeam-processors1.29.0
22 Mayrest-api1.211.10003
22 Mayrest-api1.211.10004
22 Mayrest-api1.211.10005
25 Mayrest-api1.211.10006
25 Mayrest-api1.211.10007
25 Mayrest-api1.211.10008
25 Mayrest-api1.211.10009
25 Mayrest-api1.211.10010
26 Mayrest-api1.211.10011
26 Mayrest-api1.211.10012
26 Mayrest-api1.212.10000
27 Maybeam-processors1.30.0
27 Maybeam-processors1.30.1
28 Maybeam-processors1.30.2
28 Maybeam-processors1.31.0
2 Junbeam-processors1.31.1
8 Junbeam-processors1.32.0
9 Junflink-maps-stream-inspector7.7.0
9 Junflink-maps-stream-inspector7.7.1

Goal progress

Progress against 2026 team-level engineering goals applicable to Cloud · status reflects PI 10 mid-PI position.
Sprint & PI goal achievement
100% · 9 of 9 goals (S1-S3)
Target: ≥ 80% (shared, all teams)
Pass
Release cadence
1 platform release in 3 sprints · 0.33/sprint
Target: avg 1 release per active sprint (Nick) · measured by production deployment date
Behind pace

What stood out

Every sprint goal hit so far (9 of 9 across S1-S3). Completion projected at 76% (up from PI 9's 54%). Delivery against capacity projected at 93%, the closest to capacity the team has been since PI 7. Mid-PI commitment of 151.4 SP is 83% of measured capacity (183.3 SP), a noticeable shift from PI 9 (127%).

Where the data is mixed

Platform releases are running behind cadence. Only 1 production deployment so far (3.10.15.0 on 7 May) against the target of 1 per active sprint (~5 per PI). 3.10.16.0 has been tagged in GitLab since 3 Jun but has not yet shipped to production. PI 9 deployed 5 platform releases, hitting the goal exactly.

Creep ratio projected at 51% — up sharply from PI 9 (26%). Real demand is exceeding the plan: 47.1 SP of creep in 3 sprints against a commitment of 151.4 SP for the whole PI.

Bug count of 14 in 3 sprints projects to ~23 — flat with PI 9 (21) but higher than the PI 5-8 range (9-19).

MR throughput is the clearest negative signal in the brief: 57 merged MRs in 44 active days projects to 93 for the full PI, against 474 in PI 9 (a -80% drop). The hygiene side of the same story: closed-without-merge rate is 19% of opened MRs (12 of 63), continuing the PI 9 upward trend (20% in PI 9, 13% in PI 8). Whatever is showing up as "completed" in Jira is not showing up as MRs flowing through GitLab at PI 9 pace.

prolaio · PI 10 mid-PI brief generated 11 June 2026 Source · BigQuery prolaio-engineering-metrics