Engineering Performance · PI 10 mid-PI brief

Mobile · 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 Mobile'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
Mobile is on a strong release cadence three sprints in. 3 unique release candidates shipped (target for the full PI was ~3). Bug throughput is trending materially lower than PI 8 and PI 9. Delivery is running above measured capacity.
Completion vs Commit PROJ
56.5%
▼ -10pp vs PI 9
Delivery vs Capacity PROJ
109%
Above capacity
Sprint Goals Hit
75%
6 of 8 goals · S1-S3
Creep Ratio PROJ
26%
▲ -6pp vs PI 9
Bugs Completed PROJ
52
▲ -38 vs PI 9
Releases (so far)
3 RC · 8 final
Unique RC versions · final tags
Merged MRs PROJ
101
▼ -84% vs PI 9 (648) · 62 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 · 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
Release activity · PI-level
Counts from GitLab releases · finals (no suffix) and unique RC versions · PI 10 so far + projected total
Final releases Unique RC versions 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

Final releases this PI

Final releases shipped in PI 10 so far (S1-S3). RC, alpha and beta tags excluded.
DateProjectVersion
28 Aprclinical-mobile-app6.3.22.0
1 Mayhealth-devices-ble-library2.17.0
13 Mayclinical-mobile-app6.3.24.0
1 Junclinical-mobile-app6.3.25.0
8 Junprolaio-monitor1.0.1
9 Junprolaio-monitor1.0.2
9 Junprolaio-monitor1.0.3
10 Junprolaio-monitor1.0.4

Goal progress

Progress against 2026 team-level engineering goals applicable to Mobile · status reflects PI 10 mid-PI position.
Sprint & PI goal achievement
75% · 6 of 8 goals (S1-S3)
Target: ≥ 80% (shared, all teams)
At Risk
Release candidate cadence
3 unique RCs · 6 RC tags · 8 finals
Target: ~3 RCs per PI (Kartik) · already hit
Pass

What stood out

Mobile has already hit the full-PI RC cadence target (3 unique RC versions) at the mid-PI mark, with two more active sprints to run. Counting all release tags, the team has shipped 3 RCs, 6 RC iterations, and 8 final releases across PI 10's first three sprints.

Bug throughput is trending sharply lower. 32 bugs completed in S1-S3 projects to 52 across the full PI, vs PI 8 (116) and PI 9 (90). If the trend holds, this would be Mobile's lowest bug count since PI 7.

Delivery against capacity at 109% (projected) is above target. Velocity (commit_done + creep_done) is running ahead of the team's measured sprint capacity.

Where the data is mixed

Commitment of 243.5 SP is 149% of measured capacity (163.8 SP). Mobile is committing well above capacity again, similar to PI 9 (145%). The completion projection (56.5%) reflects that gap rather than under-delivery.

Sprint goal hit rate is 75% (6 of 8) after three sprints. Two unmet goals in S2: "Updating Corsano wear state calculation" and "BYOD - start internal testing". S3 picked both up and ticked them.

Creep ratio projected at 26%, above the 20% ceiling. Better than PI 9 (32%) but the trend across PI 7-10 still shows creep consistently over ceiling.

Merged MR throughput projects to 101 for PI 10 against 648 in PI 9 (-84%). PI 9 was an exceptional MR PI for Mobile (clinical-mobile-app activity peak), so a step-down was expected. PI 10 pace is still a meaningful drop and worth flagging — Mobile is releasing on cadence but merging far fewer MRs per day.