DevOps software development practices continue to take hold as a preferred approach to develop products more effectively. Gartner estimates that half of all enterprises use DevOps. According to research firm Technavio, the global DevOps platform market will achieve 19 percent compound annual growth between now and 2020. But the popularity of DevOps practices has also given rise to some misconceptions about them, according to a recently conducted Moonshot survey published in our new report, A Guide for Successful DevOps Adoption. Those misconceptions can seriously hamper enterprises from fully realizing the potential of DevOps.

Moonshot, working with an outside research firm, recently surveyed U.S. senior IT professionals involved in DevOps adoption, augmented by detailed discussions with senior professionals. We uncovered eight persistent myths hampering their adoption of DevOps. It’s important to understand them to overcome them:

  • Myth 1: DevOps initiatives require a separate department or group to be successful. Reality: temporary DevOps teams need to facilitate the integration of the development and operations team.
  • Myth 2: DevOps is a bottom-up or grassroots approach. Reality: although the push to adopt DevOps may come from ground-level teams, top-level executives need to own DevOps and ensure that DevOps support a structured business strategy.
  • Myth 3: adopting DevOps processes can provide immediate quantifiable gains to enterprises. Reality: adoption of new tools and breaking down departmental silos require time to take effect. It generally takes at least a year for businesses to realize significant benefits.
  • Myth 4: DevOps replaces the need for system administrators by using automation. Reality: effective DevOps can automate the redundant manual tasks and optimize performance through predictive analytics. But the role of operators becomes more sophisticated and evolved with DevOps.
  • Myth 5: development and operations teams must be co-located for successful collaboration. Reality: in the initial phase, DevOps does indeed benefit from co-located teams – but co-location is not mandatory. Geographically distributed teams can help by providing 24/7 support and optimize resource allocation.
  • Myth 6: DevOps is a skill, and hiring new DevOps talent can result in successful DevOps adoption. Reality: successful DevOps adoption requires the right culture. DevOps adoption results from a culture of communication and collaboration between the development and operations teams. Hiring the right talent is not enough.
  • Myth 7: DevOps tools are more important that investing in people and process changes. Reality: automation tools are at the center of DevOps. But DevOps is not just about automation. DevOps is about continuous integration and building a culture of collaboration.
  • Myth 8: DevOps requires the replacement of an enterprise’s technology stack. Reality: DevOps does require the introduction of new tools, but if done the right way, they will integrate with the existing tools and processes – not replace them.

These misconceptions about implementing DevOps properly create roadblocks centered around people, processes and technologies. For instance, the creation of permanent, separate DevOps departments hampers the interdepartmental integration needed for development and operations teams to collaborate effectively.

Our research indicates that enterprises need a structured approach to undertake DevOps successfully. We recommend a five-step approach that tackles issues such as aligning organizational strategy and assessing a business’s DevOps maturity. Moonshot articulate our approach, along with more detailed survey findings, A Guide for Successful DevOps Adoption. This report is a procedural guide for enterprises that are adopting or plan to adopt DevOps. The report is a tool to help you succeed with DevOps. Please contact us for your copy.

Bitnami