It’s all about labels these days – AI, Containers, DevSecOps. Many people claim to ‘do it’, very few *actually* do. And unfortunately, organisations suffer about this label-driven development.

Take DevSecOps for example: on face value it’s about adding Security practices to DevOps. But how do you measure the value derived from it? And also – how do you make sure you are not disrupting your team in the process? And if you already have an established DevOps practice, what's going to change?

In this session we will see why you don’t need a label to add these practices, and how to introduce sustainable solutions to implement in your build and release pipelines in order to achieve a higher security standard across your projects without hampering your teams.