In my two decades of experience leading DevOps, Digital, and Agile transformations, I’ve observed that the path to modernisation is rarely a straight line. Organisations, particularly those in data-sensitive sectors, like banking, government, and healthcare, often find themselves at a crossroads. They need to innovate faster while maintaining rigorous security and reliability. This tension between speed and safety has traditionally forced companies to choose one over the other. But it doesn’t have to be this way.
How do you make sure your organization is not overloaded with too many projects, too many ideas, and too little focus? And how do you ensure you are building the right thing? This is exactly what epics are for. In this video, I walk through the concept of epics, show you a concrete example, and explain why epics are far more effective than traditional projects.
Collaborate & Research is the second step in the SAFe DevOps Health Radar. In this video, I explain how teams collaborate internally and conduct market research to define a minimal feature set that validates the hypothesis from the previous step.
The second way to introduce DevOps is to build a strong flow of feedback going in the opposite direction of the value flow — from customers and production back into the business and into development. This is the Second Way in Gene Kim’s Three Ways framework, and it is what stops the First Way from optimising in the dark.
