| Date | Project | Version |
|---|---|---|
| 19 May | data-platform-ci | v0.2.1 |
| 28 May | data-platform-ci | v0.2.2 |
| 10 Jun | data-ecosystem-core | 1.0.0 |
Data's PI 10 sprint goal checkboxes are all empty (S1-S3 each have an unticked goal). Same pattern as PI 9. Releases were shipped (4 finals, 4 RCs) which would normally tick goals like "Release candidate of data ecosystem in staging" — suggests the boxes are not being updated rather than the work not being done. Data's other 2026 goals are project deliverables tracked through Jira initiatives.
4 final releases and 4 unique RC versions shipped across S1-S3. This is already more release activity than Data had in all of PI 9 (9 finals, 1 unique RC). The release cadence is the highest the team has had since release tracking began.
Delivery against capacity at 83% projected (velocity 103.4 vs capacity 123.9). Below PI 9's 104% but the commitment-vs-capacity calibration is now 73% — a deliberate reduction from PI 9's 186%, which is reflected in the higher projected completion ratio (75% vs PI 9's 51%).
Creep ratio projected at 77%, the highest in the trend window. S1 was the source: 0 SP committed but 35.25 SP of creep work landed. Effectively the sprint was planned with nothing and then filled with unplanned work. S2 and S3 had more typical proportions (0 and 9 creep) but the S1 spike dominates the PI total.
Bug count projected at 27 — more than double PI 9 (10). Most of the spike is in S3 (11 bugs).
Sprint goal checkboxes have not been ticked in S1-S3. Either the practice has lapsed or the goals are written but not maintained. Worth checking with Vlad on the workflow.
Merged MR throughput projects to 90 for PI 10 against 279 in PI 9 (-68%). Release activity is at record highs while MR throughput is at a 3-PI low — both can be true if PI 9 had unusually high MR volume from data ecosystem migration work, or if PI 10 MRs are larger and fewer. Worth noting alongside the strong release picture.