Mobile produced 7,142 commits and 421 merge requests in PI 11, the highest totals of its five-PI record and up 19% and 26% respectively on PI 10. It tagged 40 releases including five distinct release-candidate lines, clearing its RC-cadence goal of roughly three per PI for the third PI running. The 6.4.0.0 release shipped in S2 and 6.4.2.0 in S3, both against ticked goals, and 65 bugs were resolved.
| Goal | Target | PI 11 | Status |
|---|---|---|---|
| Sprint and PI goal achievement shared, all team leads | ≥80% hit rate | 12 of 21 goals ticked · 57% | Missed |
| Release Candidate cadence | ≈1 RC every 2 sprints (≈3 per PI) | 5 unique RC versions · 18 RC tags | Met |
Counted as distinct version bases carrying any -rc.* tag: 6.4.0.0, 6.4.2.0, 6.4.2.1, 6.4.4.0 and 6.4.6.0. PI 9 reached 9 and PI 10 reached 4, so the ≈3 target has been cleared in every PI measured.
Activity per team member rose: merge requests at an index of 117 and commits at 111 against the team's own PI 10 level, on a roster that grew from nine to ten in September.
S3 was the team's best goal sprint of the PI — 3 of 4, closing the 6.4.2.0 release, its release candidate and the ePRO branching logic.
The RC-cadence goal was met with room: 5 unique release-candidate versions against a target of roughly 3, from 18 RC tags and 9 final tags.
Bug resolution reached 65, up from 53 in PI 10. The team runs the largest quality function on the roster at three QE alongside six engineers.
12 of 21 sprint goals were hit, a rate of 57%, against a target of 80%. The team has not reached that target in any of the three most recent PIs.
Six of the nine misses are two items restated. “Kick off BYOD beta testing” was set and missed in S4, S5 and S6. The 6.4.x release train was missed in S1 (6.4.0.0, recorded as “features got delayed”), S2 (the 6.4.2.0 RC) and S6 (6.4.6.0).
Points completed per team member fell for the third consecutive PI — 25.6 in PI 9, 20.1 in PI 10, 15.2 in PI 11. Velocity totalled 147.55 points against 180.5 in PI 10, while commitment stayed close to its PI 10 level at 319.6 against 344.75. Completion ratio was 35.3% for the PI.
Total scope surfaced ran at 227% of capacity across S1–S5.
Of 40 release tags, 31 were alpha, beta or release-candidate builds and 9 were final. The 6.4.0.0 line alone carried seven release candidates before its final tag, and 6.4.2.0 carried five.
Mobile has no production or staging environment mapped in dim_environment — only
app-store testing channels — so deployment frequency and lead time cannot be computed for the team.
Source. prolaio-engineering-metrics.metrics in BigQuery,
pulled 16 October 2026. Ratios are point-weighted across the PI
(SUM(x)/SUM(y)), not averages of per-sprint ratios, and cover all six sprints.
Rate-based goals exclude S6, the IP sprint, and say so where they appear.
Committed Done is work committed at sprint start and completed, at its end-of-sprint estimate. Velocity is committed done plus creep done. Completion ratio and creep ratio share a denominator the team sets at planning and are reported here without a pass/fail judgement.
Sprint goals are parsed from the markdown checkboxes in
sprints.sprint_goal, as the team wrote them. Teams edit these after a sprint closes,
so these figures are as of 16 October 2026.
Per-team-member figures use the delivery roster — engineers, QE and interns, excluding Product Owners and PMO — averaged over the PI's sprints.