Pitfalls in DevOps adoption

“People, not process, are the most common cause of DevOps failures,”

This seems counterintuitive.

Gartner identifies several reasons that explains this grim prediction. First of all, organizations shifting to DevOps are often trying to do too much too quickly. This, coupled with Unrealistic expectations of DevOps, creates frustration and mistrust.
Adopting to change, any change, is difficult, let alone a shift in the way the organization operates. Add to this the need to learn how to use new tools (each with it’s own syntax and workflow) and being asked to do more (you’re DevOps now!) and you can easily understand why newly formed DevOps team struggle. The answer (especially for tech people) seem obvious- use more, better tools. But as Gartner points out- Tools are not the solution to a cultural problem, and can never overcome issues like Lack of collaboration and misalignment between dev, product and sales teams. Moreover, the access amount of tools, proprietary scripts and systems makes it difficult to share information (not to mention lack of proper documentation) between team member and between teams- and these factors hurt trust, ownership and teamwork which are so important for the proper operation of a development organization. In addition, there is not enough experienced manpower that can help organizations transform themselves into DevOps led organizations. So how can such organizations deal with this imminent change with facing certain failure (well, 90% failure rate isn’t certain, but it comes pretty close) ? the answers in our minds is to focus on the actual people who would become the new DevOps. They certainly need guidance and clear leadership to help them transform the organizations. We agree with Gartner that tools are not a “magic” solution for this challenge, but the use of the right tools (ones facilitating automation, collaboration and streamlined processes) will help immensely — especially when considering the alternative (writing scripts all day long). This is also a place where determined leadership might be required- developers like scripts, but this is not a robust, scalable solution so IT leaders should be adamant in persuading their department to ditch these for proper tools.

It is only through the use fusion of people, processes and the right tools that organizations can achieve success in adopting DevOps.

Good luck and have a wonderful new year!

Related posts:

The Yankees finally gained some momentum on the season after a dismal start to the year. It looked like the Yankees were going to drop to 2–5, but Gleyber saved the day on Thursday with two big home…

Presently there is another test to conquer your preferred household item or hardwood floor. An unmistakable imprint on wood stain covered hardwood floor, left another test brought about by a tipping…

Last week it happened: we made a breakthrough in our AI and improved it tremendously for all bet types. These changes were released yesterday. What does this mean in detail? Our AI is now able to…