DevOps - the integrated part of SAFe
Many companies and government agencies today are basically IT enterprises with “something on top”. This means that each enterprise is subject to being DISRUPTED by a startup using the newest technology, organizational forms and work methods.
Just finished reading The DevOps Handbook - how to create world/class agility, reliabilty & security in technology organizations by Gene Kim, Jez Humble, Patrick Debois and John Willis.
Continuous Delivery Pipeline
Totally amazing book. Full of case studies from IT based companies testing and developing creative process and structural ideas into solid approached to the other half of the well known SAFe framework: Continuous Exploration, Integration and Deployment with in the Continuous Delivery Pipeline (https://www.scaledagileframework.com/)
The need to be fast to market and to be able to release on demand is supported by two areas with in SAFe. Program Increment and DevOps. Both methods hold the potential and support the technology company achieve the ability to release on demand.
Reduction of software systems
One area of interest I had before reading the book was how to reduce the vast number of software systems (that usually is the reality) to support continuous delivery and release on demand. This is what this short post is about.
I found part of the answer in part V of the book, in the section named ENSURE TECHNOLOGY CHOICES HELP ACHIEVE ORGANIZATIONAL GOALS.
A case from Google from the book describes: “...we had one official compiled language, one official scripting language, and one official UI language. Yes, other languages were supported in some way or another, but sticking with the big three meant support libraries, tools, and an easier way to find collaborators. These standards were also reinforced by the code review process, as well as what languages were supported by their internal platforms”.
The point on how to reach an end goal as described is revealed. The management creates buoys rather than hard boundaries that all employees must stay within. The buoys being areas where you are safe and supported. And where you can go past as long as you follow the organizational principles.
The Phoenix Project
The DevOps Handbook is full of cases and practical advice on how to streamline, change og adjust your organization, architecture and methods to be able to establish a Continuous Delivery Pipeline as part of your implementation of SAFe in your organization.
My path to The DevOps Handbook went through the classic The Phoenix Project - a novel about IT, DevOps and helping your business win by Gene Kim, Kevin Behr and George Spafford.
Wether you are a CEO or a software developer, you should read this book (before taking on or ordering someone in your company to take on The DevOps Handbook 😊).
As you read this book you will undoubtedly relive the many various troubles that all technology based enterprises experience. And you will meet ways to counter these problems. That’s when you take on The DevOps Handbook. Happy reading.
