Engineering Performance · PI 10 brief

PI 10 · Fusion

PI 10 ran 28 April to 5 August 2026. This brief summarises Fusion's PI 10 results across the five active sprints. The IP sprint (S6) is excluded from headline metrics per the standard convention.
PI window
28 Apr to 5 Aug
Active sprints
5 (S1-S5)
IP sprint
S6 excluded
Status
Complete
Fusion closed PI 10 with the strongest all-round numbers of the trend window. 17 of 17 sprint goals hit, a second consecutive perfect goal PI. Completion Ratio reached 64%, the team's highest. Nine final releases shipped against one in PI 9. Merged MR throughput finished more than three times the PI 8 level, and commits rose in every PI of the window.
Completion Ratio
64%
▲ +12pp vs PI 9 (51.5%)
Committed Done vs Capacity
94%
▲ +7pp vs PI 9 (86.5%)
Velocity vs Capacity
110%
▲ +5pp vs PI 9 (104.8%)
Sprint Goals Hit
100%
17 of 17 goals
Creep Ratio
26%
▲ -1pp vs PI 9 (27.4%)
Bugs Completed
10
▼ +5 vs PI 9 (5)
Merged MRs
99
▲ +241% vs PI 8 · 1.4/day
Capacity, Commitment, Velocity, Creep · PI-level
Story points per PI · velocity = commit_done + creep_done · creep shown as absolute SP
Capacity Commitment Velocity Creep
Capacity, Commitment, Velocity, Creep · PI 10 by sprint
All six sprints actual. S6 is the IP sprint and is excluded from the headline metrics above.
Capacity Commitment Velocity Creep
Creep Ratio · PI-level
creep / commitment · 20% ceiling shown
Creep ratio 20% ceiling
Bugs Completed · PI-level
Count per PI
Bugs
Release activity · PI-level
GitLab final release counts on Fusion repositories. Data available from PI 8 onwards.
Final releases
Merged MRs and commits · PI-level activity
Accepted merge requests and commits per PI, attributed by team member, active sprints only. PI 9 was a broad-based activity peak across the whole organisation.
Merged MRs Commits (right axis)

Final releases this PI

Final releases shipped in PI 10 (28 April to 5 August 2026).
DateRepositoryVersion
30 Aprpmr-hcm4.2.1
7 Maypmr-hcmctrt-1.0.0
13 Maypmr-hcmctrt-1.0.1
15 Maypmr-hcm4.3.0
10 Junpmr-hcm4.3.1
10 Junpmr-hcmctrt-2.0.0
24 Junpmr-hcmctrt-2.0.1
24 Junpmr-hcmctrt-2.0.2
6 Julpmr-hcmctrt-2.0.3

Goal progress

Progress against 2026 team-level engineering goals applicable to Fusion · status reflects final PI 10 results.
Sprint & PI goal achievement
100% · 17 of 17 goals across S1-S5
Target: ≥ 80% (shared, all teams)
Pass

Fusion's other 2026 goals are project deliverables (xCures, CTRT-OCORO, n8n integrations) tracked through Jira initiatives rather than warehouse metrics.

What stood out

17 of 17 sprint goals hit across the five active sprints, following 16 of 16 in PI 9. Fusion has now closed two consecutive PIs without missing a goal. The goals themselves are concrete and deliverable-shaped: named tickets, named workflows, named release tags.

Completion Ratio finished at 64%, up from 52% in PI 9 and the highest Fusion has recorded. Committed Done vs Capacity reached 94%, meaning the team completed committed work worth almost exactly its measured capacity.

Nine final releases shipped versus one in PI 9 and none in PI 8. The CTRT v2 line accounted for four of them (ctrt-2.0.0 through ctrt-2.0.3), alongside pmr-hcm 4.2.1, 4.3.0 and 4.3.1.

Creep Ratio held at 26%, essentially flat against PI 9's 27% and well down from 39% in PI 8. Fusion held creep essentially flat while three of the other four teams saw it rise. Mobile's creep fell further in absolute terms, from 40% to 25%, but from a much higher base.

Merged MRs finished at 99 against 29 in PI 8, more than triple the baseline. Commits rose in every PI of the window: 314, then 497, then 668. Fusion and Web are the only two teams whose commit volume did not peak in PI 9.

Where the data is mixed

Bug count rose to 10 from 5 in PI 9, though it remains below PI 8's 12 and low in absolute terms.

Commitment is still set well above capacity at 148%, down from 168% in PI 9 but the gap persists. The high Completion Ratio comes despite this rather than because the plan was conservative.

Creep Ratio at 26% remains above the 20% ceiling, the sixth consecutive PI above it.

Approvals per merged MR finished at 1.4, up from 0.9 in PI 9. Review depth is now the highest in the window, though absolute approval volume of 142 remains near the bottom of the org, ahead of only Web, which is consistent with Fusion being the smallest team.