Over a million developers have joined DZone.

5 Things DevOps Is Not

DZone's Guide to

5 Things DevOps Is Not

For those starting out with DevOps, it can be overwhelming with the amount of changes that need to happen to have it run smoothly.

· DevOps Zone ·
Free Resource

Best practices for getting to continuous deployment faster and with dramatic results in reduced outage minutes, development costs, and QA testing cycles. Brought to you by Rainforest QA.

For those starting out with DevOps, it can be overwhelming with the amount of changes that need to happen to have it run smoothly. This list by Shelbee Smith-Eigenbrode from DevOps.com chose to list 5 highlights that DevOps is NOT in order to give us a better understanding on how to approach it.

  1. DevOps does not simply combine the development and operations teams
    It seems like everyone at first thinks that all it takes to create DevOps is to combine those teams, however the truth is that you need to do much more. DevOps combines many processes and practices that need to be implemented throughout the entire delivery pipeline, spanning multiple stakeholders. Continuous integration (CI) and continuous delivery (CD) are two such practices.
  2. DevOps is not its own team
    Having a separate DevOps team can lead to more silos in the end. Likewise, the creation of these teams may also lead to further confusion in a case where the mission is not clearly defined.However, there are some instances where a temporary DevOps team may be necessary to enable the processes and potential tooling that is needed for adoption, but keep it temporary! Matthew Skelton’s blog, What Team Structure is Right for DevOps to Flourish? addresses this issue.
  3. DevOps is not a tool
    While it is great that there are a growing number of tools that enable us to continue maturing DevOps adoptions, DevOps is so much more than that! DevOps is not Chef or Jenkins, it is much more. While adopting automation is a huge part of DevOps, it must be combined with end-to-end practices of increased collaboration with continuous integration/continuous delivery, amplified feedback loops and continuous improvement. DevOps is a journey that requires a strategy.
  4. DevOps is not “one size fits all”
    There are many different business drivers and technologies to take into account when setting up your DevOps adoption strategy and identifying your DevOps tool chain. Therefore, it is important embrace change, gather metrics, understand feedbacks, fail fast, and correct your course quickly. If you find that a tool that you used for a previous project successfully is no longer is effective, ditch it and move on quickly. You need to understand the current strategy and environment and then react accordingly.
  5. DevOps is not automation
    It’s not ONLY automation. Automation is definitely a huge part of DevOps, but there is so much more. Understanding the main DevOps practices is a great precursor to making sure that the true benefits of DevOps are viewed.Thus, if you are starting out, this list of what DevOps is NOT can ensure that you don’t get caught up in mistakes many other people starting out have made. It is so important that every member of the team understands what DevOps is and what it is not.

Discover how to optimize your DevOps workflows with our on-demand QA solution, brought to you in partnership with Rainforest QA.

devops ,security ,database ,dba ,microsoft ,agile adoption ,release management ,culture ,linux ,sql server

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}