When a company invests in DevOps, it’s investing in speed: speed to market, speed to new ideas, speed to respond, and speed to recover. DevOps is a lot like roller coasters, sports cars, or anything else that goes zoom — if you don’t first build in safety, nobody will be comfortable going fast. The consequences of disregarding this could be disastrous, and it is up to leadership to provide that support and vision to ensure a successful transformation.
We’ve heard the message of DevOps: Automate Everything.
Automate code testing. Automate workflows. Automate infrastructure. Create the no-touch deploy. Empower the application developer to deploy directly into production. Sounds simple enough, right?
As your organization begins its DevOps transformation, you may become preoccupied with automation, forgetting that there are other DevOps concepts to address in your environment. The Scaled Agile Framework® references CALMR (Culture, Automation, Lean Flow, Metrics, Risk & Recovery) to highlight the importance of more than automation in DevOps. In this article, we’ll address the other concepts to keep in mind while on the DevOps journey.
DevOps is a market buzzword, with nearly every enterprise trying to implement DevOps to remain relevant in their industry. When I was first introduced to DevOps, I was skeptical—over 40 deployments in a day and 200x shorter lead times? I was extremely concerned about the security and robustness of these builds being deployed, as the only artifacts to support this were from smaller companies. There was nothing to prove that DevOps worked in large enterprises.
OK, you’re an RTE or an SPC in the IP iteration at the end of your PI. You’re getting ready to run the Scaled Agile Framework® (SAFe®) Inspect and Adapt (I&A) Workshop, and it seems a bit daunting. It’s big. It’s a bit complicated. It’s got lots of people. Maybe you’re wondering if it’s even worth it. Trust me, it is. And I promise that an I&A is easier than it seems.