The practice of Chaos Engineering has established the importance of running resiliency experiments in cloud-native application ecosystems. As the field of Chaos/Resilience Engineering has matured and attained widespread adoption, a need has emerged for engineering organizations to quantify the costs of running such a program. Additionally, sustained investment in any long-running program will require metrics (KPIs) to show effectiveness to Executive Leadership.

In this talk, we will discuss the setup, running and maintenance stages of a high performing Chaos/Resilience engineering program irrespective of the size of the organization. We will analyze the key metrics that should be tracked along with the optimum cadence of chaos exercises. Also, with the rapid advancement of CI/CD tools and cloud deployment technologies, we look at enhancing the impact of chaos engineering by deep integration into the continuous deployment pipeline.

As a leader, I'm always looking for new ways to improve the way I lead, the way our projects are run, and the way I can optimise our business. When agile was introduced into a more mainstream business audience, I was one of them - I saw the potential for the values and principles to work for all types of businesses, not just software development.

Since then many years have passed and after being exposed to and in the bowels of all forms of agile mindsets converted into approaches (e.g. Scrum, SAFE, etc.), I've learnt a few things - some good and some bad. I've distilled it to 10 lessons I've learnt about agile, all coming from a non-agile practitioner.

Microservices sound appealing, but what can we do with those ten-million-line code bases? Shared domain objects, horizontal coupling, and years of boundary erosion have left us with enormous complexity and spiderwebs of coupling. Michael will share techniques at various levels of abstraction, from implementation details to API design and responsibility allocation. There’s no silver bullet that will make it easy to decompose a monolith, but you’ll learn some techniques that have helped and some pitfalls to avoid, all based on Michael's experience with both successful and failed transformations.