Prolaio · Product & Engineering Leadership
PI 9 Weekly Report
19 March 2026 Sprint 4 · In Progress
PI 9  ·  4 Feb → 29 Apr 2026 Day 43 of 84  ·  41 days remaining
S1 ✓ S2 ✓ S3 ✓ ▶ S4 S5 S6

This week's discussion points

Critical Web has zero deployments in PI 9 — no staging, no production, across all 3 completed sprints and sprint 4. This is a complete halt vs PI 8's active staging cadence (30+ sprints-worth of activity). Root cause needs an answer today.
Critical Cloud completion is in freefall — 55% → 33% → 27% across S1–S3. That's a 28pp decline over 3 consecutive sprints. At this trajectory the team won't reach 40% PI completion. What changed after PI 8?
Risk Web delivery is regressing — tracking at 62.5% against a PI8 baseline of 88.6%. Combined with the deployment freeze, something structural has changed for this team in PI 9.
Watch Mobile S3 creep spiked to 52.7% — delivery was strong (90%) but unplanned work is returning. Mobile completed 35 bugs in 3 sprints; at this pace PI 9 would land at ~70 bugs, a material improvement on PI 8's 115 but still the highest in the org.
Positive Mobile and Fusion show genuine improvement signals — Mobile is tracking to 76% PI completion (vs 50% in PI 8). Fusion's S3 was 78% with zero creep — their best sprint in 4 PIs. Both worth acknowledging and sustaining.
PI 9 snapshot · sprints 1–3 complete
Cloud
36.4%
143.1 pts committed · 52.1 done
↓ S1→S3 21% creep 10 bugs
Data
47.7%
120.5 pts committed · 57.5 done
↓ S1→S3 9% creep 4 bugs
Fusion
58.9%
95 pts committed · 56 done
↑ S3 surge 19% creep 3 bugs
Mobile
76.4%
163.25 pts committed · 124.75 done
↑ S3 = 90% S3 creep 53% 35 bugs
Web
62.5%
96 pts committed · 60 done
↔ variable 19% creep 0 deploys
Delivery trends & PI forecast Sprint-by-sprint completion ratio · trajectory based on S1–3 rate
Sprint completion ratio — PI 9 (S1–S3)
Cloud Data Fusion Mobile Web
80% target
Creep ratio by sprint — PI 9
Cloud Data Fusion Mobile Web
20% ceiling
PI 9 completion trajectory · if current S1–3 rate holds for S4–S5
Team S1–3 done pts S1–3 rate S4–S5 planned Total planned Projected done Projected % PI 8 actual vs PI 8
Cloud 52.1 36.4% 76.1 219.2 79.8 36.4% 51.8% ▼ 15pp
Data 57.5 47.7% 57.0 177.5 84.7 47.7% 48.9% ≈ flat
Fusion 56.0 58.9% 43.0 138.0 81.3 58.9% 47.6% ▲ 11pp
Mobile 124.75 76.4% 72.25 235.5 179.9 76.4% 50.1% ▲ 26pp
Web 60.0 62.5% 14.0 110.0 68.75 62.5% 88.6% ▼ 26pp

Projection assumes S4–S5 completion equals S1–S3 average rate. Sprint 6 has zero commitment across all teams — not yet planned. S4 is currently in progress. Actual PI 9 outcome will update weekly.

Quality pulse Bug count per sprint · pace vs PI 8
Bugs completed — PI 9 S1–S3 vs PI 8 pace

PI 8 pace = PI 8 total bugs ÷ 6 × sprint number (scaled for 3-sprint comparison)

Cumulative bugs in PI 9 (S1–S3) vs PI 8 full PI
Cloud
S17
S22
S31
Total10
PI8 was10
Data
S11
S23
S30
Total4
PI8 was5
Fusion
S11
S20
S32
Total3
PI8 was12
Mobile
S18
S214
S313
Total35
PI8 was115
Web
S10
S20
S33
Total3
PI8 was8
Deployment health Cloud & Web only · Data, Fusion, Mobile not tracked

Cloud

preproduction
S1–S3 2 2 1
production
S1–S3 1 0 2

3 prod deploys in 3 sprints. Preprod activity declining (2→2→1). Consistent with PI 8 pattern. Still well below 0.5/day target but not a regression.

Web

staging
S1–S3 0 0 0
production
S1–S3 0 0 0
⚠ Zero deployments across all environments in all 3 completed sprints. In PI 8, Web deployed to staging 30 times across S1–S3. This is a complete halt.
Data notes
Sprint 4 is currently in progress — no completion data is included for it. Sprint 6 has zero commitment across all teams and is not yet planned. All agile data sourced from Jira via BigQuery warehouse. Deployment data available for Cloud and Web only (Data, Fusion, Mobile not yet instrumented — action from PI 8 retrospective still outstanding). Activity commit data covers the full PI-to-date window. Projections are linear extrapolations from S1–3 completion rates and should not be treated as forecasts.