Obstacles to DevOps Adoption

  • June 3, 2018

    DevOps only recently entered the common lexicon of business. However, its strategic advantage to combine software development with IT operations validates its meteoric rise.

    With all the benefits implementing DevOps can bring to an organization, many still face difficulty adopting the practice.

    A recent lecture video posted on JAXenter explains the top ten reasons companies face barriers with DevOps and how to overcome them.

    Executive Support: Making changes requires presenting tangible benefits to stakeholders which can make executive buy-in difficult. DevOps is a relatively nascent concept and may require internal selling upfront to launch or adopt a DevOps program.

    Tool Fragmentation: Tool fragmentation can create internal silos or overlap capabilities that lead to unnecessary complexities. DevOps can leverage current environments to integrate existing toolchains.

    Budget: Like any project, budget is typically the tightest constraint. Think like a project manager and scope it out so that you understand the true cost of the tools and what value they bring.

    Skillset: Implementing a true DevOps program requires five pillar roles that can take up internal resources and time. These five roles include the developer, quality assurance, operations, security and architect.

    App Complexity: Applications need to deliver consistent, seamless, secure experiences. Complex architecture can deter the streamlining of app development.

    Planning: Some projects fail by shooting first and then aiming. Incorporating project management planning principles into DevOps is paramount for success.

    Managing Environments: The applications can exist in a multitude of hosting environments from on- premise to cloud to virtual containers. Understanding where data sits and how it functions can help mitigate these challenges.

    Legacy Integration: How can you integrate what you have today to get where you want to go? Transitioning towards DevOps leveraging existing legacy systems can be a painful transformation but if done strategically can save time and resources on implementing or migrating to new systems.

    Comments(0)

    Leave a comment

    Required fields are marked *