15 teams, 1 monolith, 4 months to achieve Continuous Delivery


This is the story of 15 teams and one monolithic application going from bi-annual releases to fortnightly releases in 4 months time achieving a state of Continuous Delivery.

The reason for that move: the cost and time for testing quality into the software product, stabilising and releasing the product during each bi-annual release were skyrocketing.

Continuous Delivery involves a long list of technology and organisational changes that you have to apply to the unique circumstances of your organisation. Where do you start?

This is where The Improvement Kata, Value Stream Mapping and Theory of Constraints will help in identifying which change to apply first. However, because of the short time frame, it soon became an example of fear conversations.

After this session, you’ll understand how The Improvement Kata, Value Stream Mapping and Theory of Constraints can kick-start a Continuous Delivery program and mitigate fear.

Folks who should attend are anyone involved near and far in designing, creating, testing, deploying and releasing a software product.


  • @ EXPANDConf 2019