| Date | Project | Version |
|---|---|---|
| 19 May | data-platform-ci | v0.2.1 |
| 28 May | data-platform-ci | v0.2.2 |
| 26 Jun | data-platform-ci | v0.2.3 |
| 7 Jul | data-ecosystem-core | 1.0.0 |
Only 2 of Data's 5 active sprints had goals the warehouse could parse. The other 3 (S1, S2 and S3) wrote goals using [] with no space between the brackets, which the parsing regex does not match. Releases shipped in those sprints, so the work happened. Aligning on - [ ] and - [x] syntax would make the hit rate meaningful. Data's other 2026 goals are project deliverables tracked through Jira initiatives rather than warehouse metrics.
data-ecosystem-core 1.0.0 shipped on 7 July after a release-candidate sequence that began on 26 May and ran through eight candidates. Four final releases landed across PI 10, up from three in PI 9 and none in PI 8.
Merged MRs finished at 107 against 35 in PI 8, roughly three times the baseline. Commits reached 1,349 against 614. PI 9's 292 merges were part of an organisation-wide activity peak, so the fall from that figure is a return toward trend rather than a decline.
Velocity vs Capacity finished at 84%. Total resolved work was 92 SP against 109.7 SP of capacity, so the team was productive even though very little of it was planned work.
Creep Ratio finished at 126%, meaning more unplanned work arrived than was ever committed. 127.1 SP of creep against 101 SP of commitment. S1 (44.3 SP creep against 10 SP commitment) and S5 (43 SP creep against zero commitment) account for most of it.
Commitment was set at 92% of capacity, down from 227% in PI 9. Planning came down sharply and unplanned work filled the space. Committed Done vs Capacity of 34% reflects the small plan rather than low output: Velocity vs Capacity was 84%.
S5 was planned with zero commitment. The team resolved 16 SP of unplanned work in it. Web shows the same zero-commitment pattern in its own S5, so this is worth understanding as a planning practice rather than a one-off.
Bug count rose to 22 from 9 in PI 9. S3 accounted for 11 of them.
Sprint goal tracking remains hard to read. Three of five active sprints wrote goals using [] with no space between the brackets, which the warehouse regex does not match, so the 100% figure rests on two data points.