Getting management on board: “You need to get management as well to make sure that the tools you need are going to be available, that the training you need is going to be available,” Labourey said. “It is going to be a pretty drastic change for many teams in the way they do things, so you can’t expect just to snap and see things happen. It has to be a top-down initiative to improve the flow within IT.”
Getting help from the outside: Having someone from the outside looking in can help stop an organization from making a mistake, or it can bring in a different perspective that an organization might have missed. “Have change agents that can make sure you are not going to fall back into the good ol’ ways of doing things, but you are pushing change,” Labourey said.
Remembering that there is not one DevOps tool: “Everyone can claim a point of view and say [theirs] is a DevOps tool, but it is probably only solving one particular pain point and problem for customers,” said Ravichandran. “So when choosing a tool, look at what the tool solves and if it can work in your current ecosystem.”
It is important that tools interoperate with third-party and open-source tools because customers aren’t going to buy all their DevOps tools from one vendor, she continued.
Labeling tools as “DevOps tools” is a big problem in the industry that buyers should be aware of, according to Dynatrace’s Grabner.
“I want to point fingers at our own industry,” he said. “As much as I love that we have something like DevOps as a term, I think it has been misused…because people think just by adding DevOps on every single blog post or paper, it makes them look credible.
“I think DevOps is great, but the initial idea had nothing to do with tooling. DevOps was really the culture change about automating the process of software engineering and also sharing results.”
Planning ahead: “Have a good plan and procedure for the case when things go wrong, implement good error recovery and reporting, regularly check the scenarios in near-live circumstances,” suggested JetBrains’ Yarko.
Ravichandran added that teams should always make sure they have a previous version they can roll back to in case there is an outage or a complication.