Getting DevOps Wrong: Top 5 Mistakes Organizations Make

Time spent working on DevOps projects has opened a window into some common mistakes that organizations make when trying to deliver a true DevOps initiative.

Bill Kleyman

November 5, 2018

2 Min Read
Network Computing logo

I’ve been swimming in a sea of DevOps conversations and projects. And, to be honest, they’re all a lot of fun. I’m seeing organizations embrace their digital journey by looking much more closely at how they support users, the business, and the resources they’re delivering. A major part of this revolves around applications, code, and key services supporting the business.

Over the years, the way we’ve delivered these applications, services, and pieces of code were pretty unilateral and oftentimes manual. Today, we have a lot of fascinating development concepts specifically designed to make life easier. We have scrum, which is a great framework within which people can address complex adaptive problems. All while still productively and creatively delivering products of the highest possible value. We have agile development where requirements and solutions evolve through the collaborative effort of self-organizing and cross-functional teams, bridging customers, organizations, and the end users.

(Image: Shutterstock)

And, of course, we have DevOps. Which, if you’ve seen my DevOps 101 article, you’ll now that it’s not just two words combined together. DevOps is all of the following:

  • cultural shift in how processes, code, and technology are delivered.

  • philosophy around continuous development and integration with users, business, and even market dynamics.

  • practice that continuously evolves.

  • tool to help deliver services and applications and market-ready speeds.

  • process to help companies innovate at a much faster pace than what traditional (or legacy) software tools and infrastructure could offer.

On that note, I’ve worked with some folks that have said they have “DevOps teams,” but once you open up the development hood, it’s pretty clear that their definition of ‘DevOps’ is a bit off. Maybe they’ve got parts and pieces of a good DevOps process, but they’re definitely missing some pieces. And when you have a DevOps engine firing on half its cylinders, you’re just fooling yourself (and your organization) into thinking your doing a good job. That’s when business, end-users, and your applications begin to suffer.

Read the rest of this article here.

About the Author(s)

Bill Kleyman

Bill Kleyman, Executive Vice President of Digital Solutions, Switch; Writer/Speaker

Stay informed! Sign up to get expert advice and insight delivered direct to your inbox

You May Also Like

More Insights