The reality is that DevOps teams are often complicated to manage. The teams work towards a common goal, but both have vastly different approaches, KPIs and requirements. Developers think that ops are slow and obstructive, the giant brakes stopping the fabulous 4x4 ride into app and solution development success. IT Ops, on the other hand, is the team up at 3am fixing the problems in the code that the developers threw over the wall the day before, the team that has to ensure the implementation is solid and stable. It’s easy to see why the two can clash.
Do you feel as though developers don’t understand IT Ops’ key mandate—to keep the IT environment stable, compliant, secure and always on? Do developers get that everything else comes after that? While this may stem from their need for speed, it is also true that developers face pressures and challenges of their own. Some of them can be solved with the help of Operations in ways that also help you deliver on your goals more reliably.
Some days it may feel like the role of developers is to make stuff that destroys your stuff – the bedrock of servers, websites and databases that you administer. Whilst developers create some of these things, there is little point if the environment that you administer can’t integrate them and keep them secure and functioning.