Engineering Performance · PI 10 mid-PI
PI 10 · Mid-PI read-out and projections
An in-flight view of PI 10 with run-rate projections compared against PI 5 to PI 9 actuals. PI 10 runs 28 April 2026 to 5 August 2026. As of 29 May 2026 the teams are 41% through the PI calendar, with 2 sprints complete, sprint 3 in progress, and 3 sprints remaining (including the IP sprint).
PI dates
28 Apr → 5 Aug
99 calendar days
PI progress
41%
31 of 71 active days elapsed
Sprints
2 done · 1 active
S4, S5 future · S6 = IP
Run-rate factor
≈ 1.71 ×
5 active sprints / ~2.9 elapsed
▼ Planning swing
Commitments dropped sharply across most teams
After PI 9 missed the 80% completion target, four of five teams committed well under their measured capacity in PI 10. Cloud cut commitment in half (247 → 123 SP). Web cut to 44% of capacity. Mobile is the only team committing above capacity again.
▲ Creep explosion
Creep is exploding where commitments dropped
Projected creep ratios: Data 99%, Cloud 61%, Web 54%. Real work is showing up off-plan because the plan got too small. Only Fusion (16%) is on track to stay under the 20% ceiling. Mobile (33%) and the rest are well above.
▲ Target signal
3 of 5 teams projected to hit 80% completion
For the first time in the trend window, Cloud (85%), Data (84%), and Web (87%) are projected to clear the 80% commitment-completion target. Fusion projects 91%. The caveat: this is partly because they committed less in the first place.
Team status dashboard
Projected PI 10 values per team. Status reflects projected outcome vs target (Completion ≥ 80%, Creep ≤ 20%, Deploy ≥ 0.5/d) and direction vs PI 9. Arrows show change vs PI 9 actual.
| Team |
Commitment |
Completion (proj) |
Delivery vs Cap (proj) |
Creep (proj) |
Bugs (proj) |
MRs merged (proj) |
Prod deploys (proj) |
| Cloud |
123▼ -50% vs PI 9 |
85%▲ +31pp |
86%▲ +1pp |
61%▼ +35pp |
21flat vs PI 9 |
119▼ -74% |
2.3▼ -54% |
| Data |
76▼ -62% vs PI 9 |
84%▲ +34pp |
80%▼ -24pp |
99%▼ +90pp |
24▼ +14 |
101▼ -64% |
—no data |
| Fusion |
111▼ -45% vs PI 9 |
91%▲ +37pp |
92%▼ -16pp |
16%▲ +5pp |
9▼ +4 |
71▼ -32% |
—no data |
| Mobile |
196▼ -24% vs PI 9 |
66%flat |
100%▼ -29pp |
33%flat |
40▲ -50 |
135▼ -79% |
—no data |
| Web |
73▼ -57% vs PI 9 |
87%▲ +27pp |
51%▼ -16pp |
54%▼ +27pp |
7▼ +3 |
11▼ -92% |
2.3▼ -23% |
Read this carefully. Almost every team shows green on Completion projected and red on Creep projected. That isn't an unambiguous win. Lower commitment makes completion easier to hit, but if the actual demand exceeded the plan, the work shows up as creep instead. The PI 10 story is, so far, less about delivery and more about how teams calibrated planning after PI 9.
Projected PI 10 in trend context
PI 5 to PI 9 values are actuals. PI 10 is run-rate projected, shown as a dashed final segment on each line.
Completion ratio · PI 5 to PI 9 actual + PI 10 projected
commit_done / commitment · target ≥ 80% (dashed amber)
Creep ratio · PI 5 to PI 9 actual + PI 10 projected
creep / commitment · 20% ceiling (dashed amber)
Bugs completed · PI 5 to PI 9 actual + PI 10 projected
Count of bug + anomaly issues delivered
The planning swing: commitment vs capacity
Each team's commitment as a percentage of their measured capacity. PI 9 over-committed; PI 10 under-committed in most cases.
Commitment as % of capacity · PI 5 to PI 10
100% line shown · above = stretching capacity, below = planning under capacity
▼ Cloud, Data, Web
Sharp shift to under-committing
Cloud went from 127% of capacity in PI 9 to 67% in PI 10. Data from 186% to 61%. Web from 95% to 44%. The intent looks like a planning reset after PI 9, but the creep ratios show real demand is still arriving at PI-9 levels.
→ Fusion
Closest to balanced planning
Fusion committed 110.5 SP against 119.1 capacity = 93% of capacity. Creep projected at 16%, under the ceiling. The only team currently projecting to land on both the completion target and the creep ceiling.
▲ Mobile
Still committing above capacity
Mobile committed 196 SP against 164 capacity = 120% of capacity. Still over-committing, although less than PI 9 (145%). Projected creep at 33% and completion at 66% mirror PI 9's pattern. The behaviour around capacity hasn't shifted yet.
▲ Mobile quality
Bug throughput trending down significantly
Mobile bugs projected at 40 vs PI 9's 90. That extrapolation is conservative — Mobile only completed 23 bugs in the first 2.86 active sprints vs 116 in all of PI 8. The bug pressure on Mobile has eased substantially.
Per-team PI 9 vs PI 10 projected
PI 9 actual numbers alongside PI 10 projections. Status indicators on PI 10 columns reflect projected outcome vs target.
| Team |
Commit PI 9 |
Commit PI 10 |
Done PI 9 |
Done PI 10 (proj) |
Velocity PI 9 |
Velocity PI 10 (proj) |
Completion PI 9 |
Completion PI 10 (proj) |
Creep% PI 9 |
Creep% PI 10 (proj) |
Bugs PI 9 |
Bugs PI 10 (proj) |
| Cloud |
247.4 | 123.2 |
133.8 | 104 |
166.3 | 157 |
54.1% | 84.7% |
25.7% | 61.2% |
21 | 21 |
| Data |
201.5 | 76.0 |
101.8 | 64 |
113.0 | 99 |
50.5% | 84.2% |
9.1% | 99.3% |
10 | 24 |
| Fusion |
200.0 | 110.5 |
108.0 | 101 |
119.0 | 109 |
54.0% | 91.2% |
11.5% | 16.2% |
5 | 9 |
| Mobile |
257.75 | 196.25 |
170.6 | 129 |
230.1 | 165 |
66.2% | 65.5% |
32.0% | 32.6% |
90 | 40 |
| Web |
167.0 | 72.5 |
100.0 | 63 |
118.0 | 84 |
59.9% | 86.9% |
26.9% | 54.3% |
4 | 7 |
PI 10 values projected from the first 2.86–2.93 of 5 active sprints, multiplied by ~1.71× to estimate the full PI active period. PI 9 columns dimmed to make the comparison easy to read. Mobile is the only team where the projected pattern closely mirrors PI 9.
Specific signals worth surfacing
⚠ Data sprint 1
Data PI 10 S1 had zero commitment, 35.25 SP of creep
An entire sprint planned with 0 committed story points, but 35.25 SP of creep work came in. This isn't a typical creep pattern — it's a sprint that wasn't planned at all. Worth understanding whether this was a transition sprint or a planning lapse.
⚠ Web MR throughput
Web has merged 5 MRs in the first 31 days of PI 10
PI 9 saw 137 MRs merged across 84 days (1.63/day). PI 10 so far is 0.16/day — a 10× drop. Team size is unchanged at 6 contributors. Either real slowdown (large WIP not yet merged, blocked work, big rewrites in long-lived branches) or a data attribution issue. Worth a direct check with Jeff.
⚠ Sprint goals so far
Data and Web sprint goals show 0 of 3-5 ticked
Both teams have written sprint goals for S1-S3 but every checkbox is empty. This could mean goals are tracked but not updated, OR goals genuinely haven't been completed. The other three teams have ~78-90% hit rates on goals so far (Cloud 78%, Fusion 90%, Mobile 38%). Worth pinging Vlad and Jeff on whether the goal status is being kept current.
▲ Mobile quality direction
Mobile bug pressure has materially eased
After PI 8 (116 bugs) and PI 9 (90 bugs), Mobile has completed 23 bugs in the first ~3 active sprints of PI 10. Projected full PI: 40 bugs. If sustained, this would be the lowest bug throughput for Mobile since PI 7.
Method and caveats
Run-rate extrapolation takes "so far" values for each team (commit_done, creep, creep_done, bugs) and multiplies by 5 / active_sprints_elapsed, where active sprints exclude the IP sprint (sprint 6). Commitment and capacity are taken from the full PI plan since both are already loaded.
MRs and deployments use a days-based extrapolation: total active days (71) divided by elapsed active days (31) gives a factor of ~2.29×. Active days exclude the IP sprint period.
What this report cannot tell you. Extrapolation assumes the second half of the PI will run at the same rate as the first half. In practice teams often accelerate or decelerate based on dependencies, release crunches, or holidays. Treat projected numbers as directional, not as forecasts. The Mobile projection is most likely to be accurate (similar PI 9 pattern); the Cloud, Data and Web projections are most uncertain because the planning shape changed.
Why creep can look extreme. When commitment is small (Data 76 SP, Web 72.5 SP), even a moderate amount of unplanned work produces a very high creep ratio. The ratio is most informative when looked at alongside absolute creep volume, not in isolation.