I have really enjoyed finding excerpts from Gene’s podcast to post in here — they just keep getting better and better. Here’s the first of several patterns for DevOps Gene discusses. These are from his up-coming certain-to-be-a-bestselling book, The DevOps Cookbook.
Tom: So let’s move on to this DevOps cookbook. I’m anxious to hear more about that. Talk more about why we need it. And what was your inspiration for it, too. I’d like to know that also.
Gene: I think there are a variety of inspirations. One of the things that I’m really proud of is the book I did called the VisibleOps Handbook, which was really our attempt to capture and codify what high performing IT operations organizations were doing. It came out of the work we did on benchmarking.
One is modification of the Agile sprint process. The goal is to have at the end of each sprint interval – typically two weeks, four weeks, whatever – is to have minimal, viable, shippable code.
The problem is that, in software projects, the developers often use up all of the time in the schedule leaving none, no time for people at the end, security and IT operations. So all of the things about building the environment to deploy to, just falls off the schedule. But you still need to get it done.
So one of our modifications to the Agile sprint process is that instead of having at the end of each sprint just shippable viable code, you also have to have the environment that it deploys into — at the earliest sprint, so we’re talking sprint 0 and sprint 1.
So at the end of sprint 0, you actually have a one step build process where you can actually build the Dev environment. And then after a successful sprint, you can actually build an identical or nearly identical QA-test environment and a production environment.
So never again are we in a position where developers use up all the time and we don’t have any time to actually build stable, maintainable, secure production user environment.
I thought that was sort of a fantastic for creating a very clear goal of what development folks and production folks need to do together.
In our next excerpt from Gene Kim on DevOps – Gene discusses another example from the DevOps Cookbook called Pattern #2: Dev to Ops.
- What is Infrastructure as Code? IaC Explained
- 9 Steps for Building Pipelines for Continuous Delivery and Deployment
- What is “Shift Left”? Shift Left Testing Explained
- How to Measure the Value of Your DevOps Organization
- DevOps Best Practices for Enterprise Architecture
Forrester Study: Accelerate software delivery
When developers build business automation workflows at the same time as other application components, software delivery speed and efficiency increase while errors drop. Read this study to learn what Jobs-as-Code can mean for your business.