Engineering Performance · PI 9 Brief

Cloud · PI 9 Read-out

PI 9 ran 4 February 2026 to 29 April 2026. This brief summarises your team's PI 9 metrics.

PI 9 continued a steady upward direction for Cloud. Completion against commitment rose for the third PI in a row. Sprint goal hit rate was 83%. Merged MR throughput grew 41%. Cloud shipped 5 platform releases — exactly on the 1-per-active-sprint target.

Completion vs Commit

54.1%

▲ +2pp vs PI 8

Delivery vs Capacity

85%

Just below capacity

Sprint Goals Hit

83%

15 of 18 goals

Creep Ratio

25.7%

▼ +4pp vs PI 8

Bugs Completed

▼ +11 vs PI 8

Prod Deploys

▲ +1 vs PI 8 (0.071/d active)

Capacity, Commitment, Velocity, Creep · PI-level

Story points per PI · velocity = commit_done + creep_done · creep shown as absolute SP in amber

Capacity Commitment Velocity Creep

Capacity, Commitment, Velocity, Creep · PI 9 by sprint

Sprint-by-sprint view inside PI 9 · sprint 6 is the IP sprint · creep in amber

Capacity Commitment Velocity Creep

Creep Ratio · PI-level

Unplanned work as % of commitment · 20% ceiling shown

Creep ratio 20% ceiling

Bugs Completed · PI-level

Count of bug-type issues delivered each PI

Bugs

Deployments per PI · by tier

Active-period count (excludes IP sprint)

Production Staging

Deployment frequency · by tier

Deploys per active day · 0.5/d is the DORA target

Production Staging 0.5/d target

Goal progress

Progress against 2026 team-level engineering goals applicable to Cloud.

Sprint & PI goal achievement

83% · 15 of 18 goals

Target: ≥ 80% (shared, all teams)

Pass

Release cadence

5 platform releases · 1.0 / active sprint

Target: avg 1 release per active sprint (Nick) · measured by production deployment date

Pass

Final releases this PI

Final releases shipped in PI 9 across all Cloud projects. cloud-platform-environment rows use production deployment dates (the actual release event); other projects use the GitLab tag date as no deployment data is tracked for them. RC, alpha and beta tags excluded.

Date	Project	Version
5 Feb	flink-maps-stream-inspector	7.5.0
6 Feb	rest-api	1.190.10100
6 Feb	rest-api	1.190.10200
10 Feb	rest-api	1.197.10000
10 Feb	rest-api	1.197.10001
10 Feb	rest-api	1.197.10002
11 Feb	cloud-platform-environment	3.10.11.1
11 Feb	rest-api	1.198.10000
20 Feb	rest-api	1.197.10100
23 Feb	rest-api	1.198.10001
2 Mar	rest-api	1.199.10000
5 Mar	cloud-platform-environment	3.10.12.0
6 Mar	rest-api	1.197.10200
6 Mar	rest-api	1.197.10300
6 Mar	cloud-platform-environment	3.10.12.1
9 Mar	rest-api	1.200.10000
18 Mar	rest-api	1.201.10000
26 Mar	cloud-platform-environment	3.10.13.0
28 Mar	rest-api	1.200.10100
28 Mar	rest-api	1.200.10200
30 Mar	rest-api	1.200.10300
30 Mar	rest-api	1.202.10000
31 Mar	beam-processors	1.26.0
5 Apr	rest-api	1.203.10000
7 Apr	cloud-platform-environment	3.10.14.0
8 Apr	rest-api	1.204.10000
16 Apr	flink-maps-stream-inspector	7.6.0
27 Apr	beam-processors	1.27.0

What stood out

Completion rose from 51.8% to 54.1%, the third PI of incremental gain. Delivery against capacity was 85% (velocity 166.3 against capacity 194.7). Sprint goal hit rate was 83% (15 of 18 goals). Merged MRs grew from 331 to 466 (+41%). Production deploys rose from 4 to 5, hitting the team's "1 release per active sprint" goal exactly.

At the sprint level, the strongest sprint was S4 (velocity 52 against capacity 34.9), with S3 delivering least.

Where the data is mixed

Bug count of 21 is more than double PI 8 and the highest of the PI 5-9 period.

Creep ratio at 25.7% sits above the 20% ceiling and has risen from 21.5% in PI 8.

MR closed-without-merge rate rose from 13% to 20% of opened MRs in PI 9.

Production deploy frequency at 0.071/d (active-period basis) remains well below the 0.5/d DORA target.