From bi-annual to fortnightly releases in 4 months for 15 teams and a single monolith

15 teams, 1 shared monolith, 1 release every 6 months, and product demand for 1 release every 2 weeks. How do you know where to start with Continuous Delivery, when you’re surrounded by technology and organisational challenges?

This is the journey of 15 teams and their 1 shared monolith, at a federal Belgian agency. They increased their throughput from bi-annual releases to fortnightly releases in under 4 months, achieving a state of Continuous Delivery.

The cost and time for testing quality into the software product, stabilising and releasing the product during each bi-annual release were skyrocketing. The demand for Continuous Delivery was there, but the circumstances made it very difficult.

I’ll cover how we used the Improvement Kata, Value Stream Mapping, and the Theory Of Constraints to choose which changes to apply first, and kickstart the organisational changes we needed to improve quality and drive down lead times.

If you thought Continuous Delivery was just for the happy few having trendy microservices, think again!

  • @ EXPANDConf 2019
  • @ XPDays Benelux 2019
  • @ ScanAgile 2020 (video)
  • @ Lean Agile Exchange 2020
  • @ Agile on the Beach 2022 (video)
  • @ FlowCon 2022 (video)
  • @ KanDDDinsky 2022