From waterfall to Agile, across teams and sectors

The products in these stories were not delivered by accident. Behind each one sat delivery management, Agile coaching and Scrum Master work, on teams that ranged from a handful of people to more than ten, in sectors from HR and finance to supply chain and security, and across product, quality, Oracle and AI disciplines. Several of those teams started in waterfall.

How delivery was run

Waterfall to Agile

Teams moved from long waterfall phases to iterative delivery: backlogs in place of specifications, working increments in place of milestone documents, and reviews that changed what was built next.

Different teams, different shapes

Delivery was adapted to the team rather than the other way round: a small product team, a ten-person mobile team across platform migrations, and Oracle and AI teams with their own release rhythms.

Across verticals and horizontals

The same delivery discipline applied across business areas (HR and finance, supply chain, security) and across engineering disciplines (product, quality engineering, Oracle, AI).

What changed

Work became visible and predictable: stakeholders could see progress and risks as they happened, decisions were made at the right time, and releases stopped being events to brace for.