Engineering Performance · PI 10 mid-PI brief

Web · 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 Web'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
Web has shipped work in every sprint of PI 10 so far and bug throughput remains low. S3 closed all sprint goals after a slower S1-S2 (likely a goal-tracking gap rather than execution). Staging deployment activity is the highest of any team.
Completion vs Commit PROJ
58%
▼ -2pp vs PI 9
Delivery vs Capacity PROJ
48%
▼ -19pp vs PI 9
Sprint Goals Hit
40%
2 of 5 ticked · S3 caught up
Creep Ratio PROJ
36%
▼ +9pp vs PI 9
Bugs Completed PROJ
8
flat vs PI 9 (4)
Prod Deploys PROJ
3
PI 10 so far: 2 (0.045/d)
Merged MRs PROJ
11
▼ -92% vs PI 9 (137) · 7 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
Release activity · PI-level
GitLab release counts on Web projects · PI 10 so far + projected total
Final releases 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). RC and non-version tags (e.g. "v1.1.0-test-ci") excluded.
DateProjectVersion
20 Mayprolaio-ui0.8.1
4 Junprolaio-ui0.9.0

Goal progress

Progress against 2026 team-level engineering goals applicable to Web · status reflects PI 10 mid-PI position.
Sprint & PI goal achievement
40% · 2 of 5 ticked (S3 all hit)
Target: ≥ 80% (shared, all teams)
At Risk
Value delivered every sprint
3 of 3 sprints delivered work
Target: No sprint with zero delivery (Jeff)
Pass

S1 and S2 sprint goal checkboxes were not ticked (same pattern as PI 9 S1-S2). S3 had all checkboxes ticked. The S1-S2 misses may be tracking-hygiene rather than missed work.

What stood out

Every sprint delivered work (S1: 19 SP, S2: 10 SP, S3: 7.5 SP) — the "value every sprint" goal is on track. S3 caught up on sprint goal tracking after a slower S1-S2: both adherence workbench validation and production token integration goals ticked.

Bug count of 5 across S1-S3 projects to ~8 — staying in the low single-digit range that has characterised Web's quality posture across the trend window.

Staging deploys at 27 in S1-S3 project to ~44 for the PI, a notable uptick from PI 9's 33 and back toward the PI 8 cadence (49). Most active staging environment of any team.

Where the data is mixed

Completion projected at 58% with delivery against capacity at 48%. Web is the only team where both projections are red. The picture is similar to PI 9 but velocity is running below capacity for a second consecutive PI.

Creep projected at 36%, above the 20% ceiling and worse than PI 9's 27%. Two sprints back over ceiling.

MR merged count is 7 across S1-S3, projecting to ~11 for the PI. PI 9 was 137. The team has the same number of contributors (6). Worth understanding whether work is sitting in long-lived branches, has shifted to non-MR workflows, or whether something else is going on.

Production deploys at 2 so far, projecting to ~3 (vs PI 9's 3). Production cadence has not recovered.