Implementing DevOps - Top 6 Mistakes
Everyone talks about implementing DevOps, but it's easier said than done. Just use this guide to avoid some of the common pitfalls and you'll be fine.
Join the DZone community and get the full member experience.Join For Free
everyone loves to talk about devops, but when it comes to real life enterprise implementation, things start to get a little shaky. having gone through the process with hundreds of organizations, the xebialabs sale engineering team relayed to me the 6 most common mistakes they see when enterprises implement devops for the first time. change is never easy, but if you can dodge these top 6 mistakes, your transition to devops can be relatively painless.
not getting buy-in early in the implementation
go to the person that “owns the box” on the production (aka “ops”) side. talk about your initiative, and help him/her understand how this will benefit the operational teams. (goal: one-button deployments in prod) be willing to partner closely with this person, providing updates (demos, training) for the operations teams.
not having a transition plan
once you have some of your releases automated in this new “devops” way, operations is forced to have two different deployment processes: the new modern “automated” way, and the 17-page deployment spreadsheet. as you start to have success in production, it’s important to talk and plan how to bridge your dev teams delivery models.
automate 2-3 apps from dev to prod
this will help you discover all of the… “nuances” of your application delivery process. which people are involved, what requirements do you have, etc. you may already know this, but automation forces companies to think about how these things will change for the better.
only automating in the lower environments
most development organizations can implement automation in their dev and integration environments. but getting to environments like qa, stage, pre-prod and prod require a lot more thought about the implications of automation. if a devops team is not empowered to make changes along the entire delivery path, then you will find your devops initiative fizzle out in this “half-auto” mode.
creation of a devops team outside the existing ops and dev teams
one trap people fall into is introducing yet another silo. the intention is good, a “painless” migration for certain projects, but in practice it becomes too easy to circumvent this team or worse use some fast route through this team to avoid good practice that exists in the other teams. i have seen teams avoid this trap by embedding “ops” into the development scrums. this is often resisted (“too busy cutting trees to sharpen my axe”), but those that manage it learn a lot and start to see the progression to a working devops organization.
focusing on the wrong thing
the main difference between doing devops right and otherwise is how the people interact with each other. shared knowledge, common goals, desire to succeed are all traits of organizations wanting to do it right. this is harder the more people and business structure there is involved, lots of things have to change in a large organization to make this work, and some of those changes will disrupt other areas of the business, possibly for the worse!
Published at DZone with permission of Necco Ceresani, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.