The transition to DevOps can be long and hard because is going to involve disruption. That can mean periods of reduced productivity and increased costs, but it can be worth it. Here are 8 steps to get you started in a positive direction.
DevOps is big right now. Of course, it's tough to get the same definition of precisely what DevOps is from any two people, but in general folks agree that it uses automated deployment tools to enable continuous development, deployment, and improvement of enterprise software.
As DevOps tool vendor New Relic writes on its website, "...the DevOps movement emphasizes communication, collaboration and integration between software developers and IT operations. Rather than seeing these two groups as silos who pass things along but don't really work together, DevOps recognizes the interdependence of software development and IT operations and helps an organization produce software and IT services more rapidly, with frequent iterations."
That's nice, but how, precisely, do you get from whatever it is you're doing now to DevOps? The answer will vary from organization to organization, but in general there are some steps you can take to take you along the path. These steps were developed by exhaustively combing the Internet, looking at the stories told by those who have survived, talking to IT pros, and using employing a modicum of common sense and experience. The result is eight steps that aren't enough to handle every detail, but are sufficient to use as a framework on which other, highly detailed, steps can be hung.
I'm curious about your experience with DevOps. Is it the system your company uses now? Are you considering it? Have you been through a DevOps transition? I'd love to know and I'm sure the community would love to benefit from your experience. Meet me in the comments section and we'll start a conversation on DevOps, step by step.