What changed across the last two sprints
Sprint 1 was a broad foundation sprint: the team delivered the core Drupal, migration, auth, and localization scaffolding needed to get the platform into shape.
Sprint 2 shifted toward product-facing capabilities and hardening: richer editorial controls, migration of content types and pages, DAM discovery and setup, JSON API work, and CI/test coverage all moved forward. Velocity stayed steady in throughput terms, with the mix moving from platform setup toward feature completion and validation.
The main slip risk is concentrated in content moderation workflow work and the remaining Crowdin follow-up. Compared with Sprint 1, the work looks more targeted and more integrated, which is a good sign; the tradeoff is that a few items are still waiting on UAT or clarification before they can close cleanly.
Across the last two sprints, PADI has moved from laying the technical foundation to delivering user-facing and operational capabilities. The first sprint focused on core architecture, migration setup, authentication, multilingual support, and workflow foundations; the second sprint built on that base with editor experience improvements, content migration, DAM discovery, API consumption, and automated testing.
Overall throughput remained healthy, but the nature of the work became more implementation-heavy and product-shaping in Sprint 2. That means the team is no longer just setting up the platform — it is now proving the editorial and migration flows end to end.
What slipped was mainly workflow-related: the content moderation states/transitions item is still blocked by UAT feedback, and the remaining Crowdin follow-up still needs input. What improved is the breadth of working software around editing, preview, migration, and test automation, which should reduce risk as the build matures.