DevOps Anti-patterns and How to Correct Them

  1. Systems thinking
  2. Amplify feedback loops
  3. Culture of continual experimentation and learning

DevOps Anti-pattern #1 — Treating DevOps as a set of tools

Most technology and knowledge workers would likely agree with the claim that tools make things better, more efficient or easier in some shape or form, when applied appropriately. In the DevOps world, many teams that I have worked with treat “DevOps” and tools are one in the same, which is a tremendous mistake that undervalues the power of DevOps and the core outcomes it aspires to achieve.

DevOps Anti-pattern #2 — Treating DevOps as a team

Many organizations establish a “DevOps team” which is typically a team of software engineers that have expertise in specific tools that enable various processes and practices including (but not limited to) Continuous Integration, Continuous Testing and/or Continuous Deployment, just to name a few examples. This team specializes in automation of processes using a set of tools, which is important, but should not be considered to be the desired end-state in a DevOps transformation.

DevOps Anti-pattern #3 — If you automate, then you are doing DevOps

As mentioned previously, automation is a significant piece of the overall DevOps puzzle. However, if implemented in isolation without considering the overall workflow and organizational value stream, the value that automation delivers will likely not fulfill its full potential.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


An Alten Company, Cprime is a global consulting firm helping transforming businesses get in sync.