Engineering Reports

Engineering performance · reports index

Weekly sprint reviews, PI briefs, cross-team analyses, and related reports. Click any card to open. Updated as each sprint and PI closes out. PI 11 closed 14 October 2026.

PI 12 (in progress)

Current
PI 12 runs 14 October 2026 to 27 January 2027. Data Engineering moved to the AI & Technology department from PI 12, so these reports cover Cloud, Fusion, Mobile and Web, with all baselines recomputed on that four-team basis.
Sprint Review · PI 12 · Sprint 1 →
Sprint closed 28 October. Rebuilt around the five leadership KPIs, with the note’s interim readings where a KPI cannot yet be measured. All four teams hit every goal they set — 8 of 8, the first clean sweep on record. Investment allocation is now reported on the capitalization report’s work-type mapping: new capability took 74% of completed work, with testing and verification doubling its share. Defect intake was matched almost one for one at 0.94x, and Fusion’s production releases are now measured, taking throughput coverage to three of the four teams.

PI 11 (closed out)

Retrospective
PI 11 ran 22 July to 14 October 2026 across six sprints. Start with the cross-team report; the trend analysis puts PI 11 next to PI 9 and PI 10.
Capacity restated 3 November 2026. PI 11 capacity was reloaded in the warehouse alongside PI 12’s, moving S1–S5 capacity from 617.8 to 583.1 points. Demand ÷ capacity for PI 11 is now 204%, not 192%, and velocity ÷ capacity 98%, not 92%. The reports below still carry the original figures; everything not derived from capacity is unaffected.
PI 11 · Cross-Team Summary — one slide →
The single slide for the P&E leadership meeting. Four org numbers, goal achievement against velocity across three PIs, and a five-team strip. 16:9, prints to PDF. Deliberately excludes releases, deployments and lead time — DORA covers only Cloud and Web, so those figures would be partial in front of the full group.
PI 11 · Cross-Team Report →
The full-PI read-out for the P&E leadership meeting. First PI on record to clear the 80% sprint-goal target at 83.6% — while capacity, velocity and production deploys all fell again. Sprint goals, releases, bugs, demand vs capacity, team scorecard, output per engineer, per-team read and delivery flow.
Agile at Prolaio · PI 11 Snapshot →
A snapshot of agile practice across the five product teams: how they plan and deliver, what we measure (agile and DORA), and seven themes from PI 9 to PI 11 data, each with the open questions it raises.
PI 9 to PI 11 Trend Analysis →
Three complete PIs, February to October 2026. The org getting smaller and more reliable at the same time: output per engineer down ~10% per PI, goal achievement up 7 points, and demand stuck between 192% and 205% of capacity for three PIs running. Successor to the PI 8–10 analysis.
PI 11 · Cloud →
17 of 19 goals, highest MR and commit totals on record, lead time halved. Platform release cadence missed at 2 in S1–S5.
PI 11 · Data →
6 of 7 goals and output per head up, through a PI that halved the delivery roster. No goals logged in S4 or S5.
PI 11 · Fusion →
19 of 19 goals, second PI running at 100%, and the highest final-tag ratio recorded. Output per head down on all three measures.
PI 11 · Mobile →
Highest commit and MR totals of its record and the RC-cadence goal cleared, against 12 of 21 sprint goals and a third PI of falling points per head.
PI 11 · Web →
7 of 7 goals and a plan at 116% of capacity — the closest to a realistic plan in the window. Activity down on every measure.

PI 11 weekly sprint reviews

Weekly
The reports taken to the weekly P&E leadership meeting as each sprint closed. Sprint-goal figures in these were accurate at publication; teams tick goal checkboxes after a sprint closes, so the PI 11 cross-team report supersedes them.
Sprint Review · PI 11 · Sprint 3 →
Sprint closed 2 September. Best completion of the PI at 49.9% and velocity at 98% of capacity, with zero production deployments. Published at 8 of 12 sprint goals; since restated to 11 of 12 as teams ticked boxes after close.
Sprint Review · PI 11 · Sprint 2 →
Sprint closed 19 August. The plan came back to capacity and delivery followed — 11 of 12 sprint goals hit, velocity at 99% of capacity, three production releases including Mobile 6.4.0.0 and Data 1.1.0.
Sprint Review · PI 11 · Sprint 1 →
Sprint closed 5 August. Activity rose while the board fell — 229 MRs merged, up 21%, against a completion ratio of 37.8%. Sprint goals, releases, bugs, demand vs capacity, per-engineer output and DORA.

Team sprint reports · PI 11 S3

Weekly
Per-team read-outs of the last closed sprint, written for the team and its lead. Each report reads the team against its own recent history and ends with three questions to open the sprint conversation.
PI 11 S3 · Cloud →
All three goals hit and the highest velocity of the PI, against a plan now 2.3× capacity. 3.14.0 stopped at rc.2 in preproduction.
PI 11 S3 · Data →
Both sprint goals missed in the sprint with the PI's best completion. 1.2.0-rc.1 tagged in all three repos, pre-prod not reached.
PI 11 S3 · Fusion →
Every goal hit, at the lowest volume of the last nine sprints. Capacity setting is the open question.
PI 11 S3 · Mobile →
97 merge requests merged, the busiest sprint of the PI. Ten tags for one version, and the release goal still marked missed.
PI 11 S3 · Web →
Plan, capacity and outcome aligned for the first time in nine sprints. Fourteen staging deployments, none promoted.

Cross-PI analysis

Analysis
Multi-PI trend work. Start here for the organisation-wide picture.
Engineering Metrics · Diagnosis and Proposal →
Why Completion Ratio cannot work as a target, what unplanned work actually consists of, and a proposed replacement metric set with per-team ad hoc reserve sizing. For the P&E leadership discussion.

PI 10 (closed out)

Retrospective
PI 10 ran 28 April to 5 August 2026. Team briefs cover the five active sprints; the IP sprint is excluded from headline metrics.
PI 8 to PI 10 Trend Analysis →
Cross-team analysis closing out PI 10, with PI 8 and PI 9 as the trend baseline. Six patterns, the commitment-creep relationship, activity and review, team trajectories, measurement health, and questions for the P&E conversation. Superseded for current trend work by the PI 9–11 analysis.
PI 10 · Cloud →
Final read-out for the Cloud team. Capacity, commitment, velocity, creep, releases, deployments, goal progress.
PI 10 · Data →
Final read-out for the Data team.
PI 10 · Fusion →
Final read-out for the Fusion team.
PI 10 · Mobile →
Final read-out for the Mobile team.
PI 10 · Web →
Final read-out for the Web team.

PI 9 (closed out)

Retrospective
PI 9 ran 4 February to 29 April 2026.
PI 9 Engineering Analysis →
Cross-team analysis of PI 9. Status dashboard, sprint goals, agile execution, deployments, activity, MR throughput, and team profiles.
PI 9 · Cloud →
PI 9 read-out for the Cloud team.
PI 9 · Data →
PI 9 read-out for the Data team.
PI 9 · Fusion →
PI 9 read-out for the Fusion team.
PI 9 · Mobile →
PI 9 read-out for the Mobile team.
PI 9 · Web →
PI 9 read-out for the Web team.

Other reports

Reference
Engineering Performance · PI 5-8 →
The original cross-team analysis spanning PI 5 through PI 8 (Feb 2025 to Feb 2026). Source of PI 9-onwards report style.
P&E Weekly · PI 9 · 19 Mar 2026 →
Product and Engineering weekly read-out from mid-PI 9.
AI Adoption Pulse · PI 9 Baseline →
First-run results from the AI Adoption Pulse survey, with DORA 2025 benchmark comparison.
prolaio · Engineering reports index Source · BigQuery prolaio-engineering-metrics