Data hit 6 of the 7 sprint goals it recorded in PI 11 and shipped DES 1.1.0 through to a final tag in S1, and cleared its pre-production release of 1.2.0 in S3 against a ticked goal. Points completed per team member held within 6% of PI 10 at 19.4 — an index of 94 against the team's own prior level — through a PI in which the delivery roster went from six people to four at the S1/S2 boundary.
| Goal | Target | PI 11 | Status |
|---|---|---|---|
| Sprint and PI goal achievement shared, all team leads | ≥80% hit rate | 6 of 7 goals ticked · 86% | Met |
Beyond the shared goal above, no team-level engineering metric goals for 2026 are tracked via the warehouse for this team. Its 2026 goals are project deliverables — tracked as Jira initiatives and quarterly milestones — and are not computable from the metrics dataset. See the engineering goals document.
Of the 7 goals recorded, 6 were ticked. S1 closed both — the DES 1.1.0 release candidate and a temporary production-access solution. S2 closed the 1.1.0 technical work and started the CDS migration spike. S3 closed the 1.2.0 pre-production release and the scheduled-task assets for Web.
Output per team member held close to its PI 10 level even as totals fell sharply: 19.4 points per head against 20.6, an index of 94. The denominator shrank almost as fast as the output.
The team tagged 24 versions across the PI — the 1.1.0 and 1.2.0 lines of data-ecosystem, data-ecosystem-core and data-ecosystem-infrastructure, plus data-platform-ci — of which 5 were final versions.
Creep absorbed 48.25 of 84.25 unplanned points, a creep-done ratio of 57%, the team's highest in the window.
No sprint goals were recorded for S4 or S5. The 7-goal denominator therefore covers four of the six sprints, and the 86% hit rate is not comparable with a PI in which all six sprints logged goals.
Commits fell from 1,994 in PI 10 to 683, and merge requests from 131 to 66. Two engineers left the team on 5 August 2026, between S1 and S2; they accounted for 77% of the team's commits in S1. The replacement hire on 6 August is a Product Owner, so the delivery roster moved from 6 to 4.
Velocity totalled 83.25 points against 117.25 in PI 10. Commitment fell further, from 145 to 113, and completion ratio was 31% for the PI against 35.9% in PI 10.
The one missed goal is S6's “To deploy 1.2.0 on pre-production”. Of the 24 tags in the PI, none of the 1.2.0 line went past a release candidate.
S4 is the lightest sprint in the team's five-PI record: 10 points committed, 1 completed, velocity of 2 against 15.7 of capacity.
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.