Engineering Performance · PI 10 mid-PI brief

Fusion · PI 10 Mid-PI Read-out

PI 10 runs 28 April 2026 to 5 August 2026. As of 11 June 2026, sprints 1-3 are complete and S4 starts shortly. This brief summarises Fusion's progress so far and projects full-PI outcomes at current run-rate.

PI progress

62% active days

Sprints complete

3 of 5 active

Run-rate factor

≈ 1.59×

Today

11 June 2026

Fusion is on track to repeat its PI 9 performance, with planning calibrated to capacity. 10 of 10 sprint goals hit. Creep ratio held under the 20% ceiling. Delivery is running close to capacity (95% projected). Bug count remains low.

Completion vs Commit PROJ

85%

▲ +31pp vs PI 9

Delivery vs Capacity PROJ

95%

▼ -13pp vs PI 9

Sprint Goals Hit

100%

10 of 10 goals · S1-S3

Creep Ratio PROJ

13%

▲ +2pp vs PI 9

Bugs Completed PROJ

▲ +3 vs PI 9

Releases (so far)

4 finals

2× PI 9's full-PI total

Merged MRs PROJ

▼ -46% vs PI 9 (104) · 34 so far

Capacity, Commitment, Velocity, Creep · PI-level

Story points per PI · velocity = commit_done + creep_done · creep shown as absolute SP · PI 10 projected dashed

Capacity Commitment Velocity Creep

Capacity, Commitment, Velocity, Creep · PI 10 by sprint

Sprint 1-3 actual · S4-S5 planned commitment shown · S6 is the IP sprint · creep in amber

Capacity Commitment Velocity Creep

Creep Ratio · PI-level

creep / commitment · 20% ceiling shown · PI 10 projected dashed

Creep ratio 20% ceiling

Bugs Completed · PI-level

Count per PI · PI 10 projected dashed

Bugs

Release activity · PI-level

GitLab release counts on Fusion projects · PI 10 so far + projected total

Final releases PI 10 projected

Merged MRs · PI-level activity

Count of accepted MRs per PI, attributed by team member. Data available from PI 8 onwards. PI 10 projected dashed.

Merged MRs

Final releases this PI

Final releases shipped in PI 10 so far (S1-S3).

Date	Project	Version
30 Apr	pmr-hcm	4.2.1
7 May	pmr-hcm	ctrt-1.0.0
13 May	pmr-hcm	ctrt-1.0.1
15 May	pmr-hcm	4.3.0

Goal progress

Progress against 2026 team-level engineering goals applicable to Fusion · status reflects PI 10 mid-PI position.

Sprint & PI goal achievement

100% · 10 of 10 goals (S1-S3)

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

10 of 10 sprint goals hit across S1-S3. Goals are concrete and deliverable-focused (FSN-244 dev complete, n8n workflows finished, PWU UI tickets shipped). The full PI 9 hit rate of 100% (18/18) is on pace to repeat.

Commitment of 124 SP against 119.1 capacity = 104% — the most balanced commitment-to-capacity Fusion has set in the trend window. Down from PI 9's 182%, which makes the projected completion ratio (85%) genuinely strong rather than driven by under-planning.

4 final releases shipped in S1-S3 already exceeds PI 9's full-PI total (2). The team is releasing more frequently than at any prior point in the trend window.

Where the data is mixed

Bug count of 5 in 3 sprints projects to ~8 for the PI — slightly higher than PI 9 (5) and PI 7 (0). Still low in absolute terms.

Approvals per merged MR averaged 0.09 in PI 10 so far (3 approvals / 34 merges), continuing the low review-depth pattern seen in PI 9 (0.78/merge). Worth understanding whether the review process is being skipped or whether approvals are being tracked elsewhere.

Merged MR throughput projects to 56 for PI 10 against 104 in PI 9 (-46%). Fusion is the smallest dev team and PI 9 included a heavy xCures push, so a step-down was expected — but worth tracking to ensure the slower MR pace isn't masking a delivery issue.