15 teams, a single 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 single 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.
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, Jeffrey Fredrick and Douglas Squirrel made me realise it was Fear Conversations that helped us to mitigate fear and navigate the difficult conversations we had to have.
If you thought Continuous Delivery was just for the happy few having trendy microservices, think again!
Agile on the Beach is a leading annual conference in Falmouth, Cornwall UK. Since 2011 Agile on the Beach has been a two day agile conference, set on the Cornish coast with a beach party in between. The conference explores agile software, products, teams, business and practices. With over 400 attending, the conference hosts 50 seminars and workshops to provide the ultimate agile learning experience, along with ample opportunities for networking at its three evening events.
Got to agileonthebeach.com for more details