Agile Software Development

4 Signs Your DevOps Initiative Is Off the Rails

The danger of a DevOps pilot team is that, if it does not properly transfer its knowledge to cross-functional teams, it can become a new organizational silo of its own. That defeats the purpose of DevOps, but it happens. In an article for AgileConnection, Jeffery Payne discusses four signs that DevOps may not be working as it should be in your business:

  • Focusing solely on speed
  • Forgetting to onboard teams
  • Focusing on tooling instead of systems thinking
  • Thinking of DevOps as a process

Zooming toward Calamity

DevOps enables continuous delivery, but businesses that interpret that only to mean “DevOps makes things go vroom vroom fast,” are wrong. Continuous delivery happens as a combination of increased speed (through improved processes) and earlier testing that removes defects sooner. Incorporating quality assurance sooner is critical to healthy DevOps, and a speed-only imperative forgets that.

Next, about forgetting to onboard teams, Payne writes this:

It is common when moving to a DevOps delivery model for some pretty radical changes to be made across the delivery process that impact how software developers, testers, release managers, and operational personnel do their jobs. For example, seeking to move toward a continuous delivery process in which all code changes are promoted into production will often dictate changes to how code is branched and merged during software development and check-in. If an appropriate branch/merge strategy is not followed, your teams are going to struggle to accelerate delivery.

Those responsible for enabling DevOps within your organization must take the time to teach, mentor, define processes, and set up enabling technologies for those who must wield new DevOps capabilities.

Another thing DevOps teams must do is consider systems thinking ahead of tinkering with tool optimization. After all, optimizing the wrong things does not yield a lot of value. It is better to take time to understand bottlenecks and constraints in the value stream before getting into optimization and automation discussions.

Lastly, remember that DevOps, like agile, is basically a philosophy for work. It is not just a process to be run through, with an easy prize at the end. Rather, DevOps should be an ongoing labor of love.

For additional thoughts, you can view the original article here:

Show More

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.