Continuous Delivery in 4 Months for 15 Teams and their 1 Monolith

W7     Start Time : 11:00     End Time : 11:30

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 costs 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.

When we started out, I thought our Continuous Delivery journey could be an example implementation of Steve Smith’s Measuring Continuous Delivery book. It turned out quite differently. Afterwards, I realised it was Fear Conversations that helped us to mitigate fear and navigate the difficult conversations we had to have.

We will cover:

  • Introduction: the context of the organisation.
  • The plan: what I had in mind when starting this journey – The Improvement Kata, Value Stream Mapping and Theory of Constraints.
  • What actually happened: how the plan turned out differently than expected, i.e. using Fear Conversations to mitigate fear.
  • Tada: achieving Continuous Delivery and what were the outcomes for the organisation, i.e. how it made many problems everyone knew about very visible to the organisation allowing the organisation to act upon it.
  • The learnings: what I learned from this journey.

Key Takeaways:

  1. Be able to use the Improvement Kata to introduce change at scale.
  2. Be able to run a Value Stream Mapping workshop to understand the current situation.
  3. Be able to use the Theory of Constraints to identify which activity should be improved first and which experiment will be most likely to succeed.


Back to Programme

    • Speaker


      Thierry de Pauw - Continuous Delivery consultant, ThinkingLabs, Belgium

      Thierry is Engineering Lead at the fintech startup PaxFamilia.

      On the side, he founded ThinkingLabs where he advises organisations in the adoption of Continuous Integration and Continuous Delivery.

      Thierry is a lean software engineer, CI/CD advocate and jack-of-all-trades with a passion to help teams create meaningful software, having a keen eye for code quality and the software delivery process, from customer interaction to continuous delivery. Instead of balancing quality & delivery, he believes and practices that better quality is actually a way to more and better deliveries.

      In 2019 Thierry organised the CITCON – Continuous Integration and Testing unconference in Ghent, Belgium.

    << previous next >>