Fusion hit every one of its 19 sprint goals in PI 11 — the second consecutive PI at 100%. xCures 1.0.0 reached a final tag in S5, pmr-hcm shipped 4.5.0 in S4 and 4.6.0 in S6, and the xCures deployment setup, unit-test verification and Ketryx mappings all closed in S4. Completion ratio of 57.3% is the team's highest in three PIs, and creep ratio of 30.3% is among its lowest.
| Goal | Target | PI 11 | Status |
|---|---|---|---|
| Sprint and PI goal achievement shared, all team leads | ≥80% hit rate | 19 of 19 goals ticked · 100% | 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.
19 goals set, 19 ticked. S4 alone closed five: the CHDI-6 deployment setup, CHDI-3 verification, the PSR-EVO2 feature flag, the PSR activity flag across front and back end, and the PSR v2 vital-sign chart pages.
Of 13 release tags, 9 were final versions. xCures went from project creation in S1 to a 1.0.0 final tag in S5 inside a single PI.
Completion ratio reached 57.3% against 62.1% in PI 10 and 48.6% in PI 9, and velocity against capacity came in at 115%.
S6 was the team's strongest sprint of the PI: 25 of 30.5 committed points completed, velocity of 31 against 16.6 of capacity.
Output per team member fell on all three measures against the team's own PI 10 level — points at an index of 79, merge requests at 48, commits at 67. Points per head went 32.4 to 25.5, and merge requests per head 33 to 16.
Totals moved the same way: 74 merge requests against 131 in PI 10, and 726 commits against 920. Velocity was 120 points against 129.5.
The roster changed mid-PI. One engineer left on 10 September 2026 and two joined the same day, taking the team from four to five. S3 and S5 sit either side of that change and are the team's two lightest sprints of the PI — velocity of 7.5 and 14 points respectively.
Fusion has no production or staging environment mapped in dim_environment, only
dev, 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.