A Tension Worth Taking Seriously
The relationship between ITSM and DevOps has been characterised, somewhat unfairly, as a conflict between control and speed. ITSM wants governance, documentation, approval gates and change management. DevOps wants continuous delivery, automation, small frequent releases and minimal process overhead. The two communities have spent years talking past each other.
The reality is more nuanced. Both disciplines share the same ultimate goal: reliable, high-quality service delivery. The tension is real but it is a tension between different approaches to the same objective — and it is resolvable.
Where They Actually Conflict
The sharpest point of genuine conflict is change management. Traditional ITSM change management — with CAB approval, change freeze periods and heavyweight documentation — is genuinely incompatible with the deployment frequencies that effective DevOps teams work at. A team deploying to production multiple times a day cannot wait for a weekly CAB.
The solution is not to abandon change management — it is to redesign it for the DevOps context. This means investing heavily in automated change risk assessment, pre-approved change models for automated pipeline deployments, and post-deployment monitoring that can identify issues faster than traditional testing and approval gates.
Where They Complement Each Other
The complementarity is at least as significant as the conflict. ITSM's emphasis on service orientation — understanding what business outcomes IT services are delivering, and measuring performance against those outcomes — is a valuable counterbalance to DevOps teams that can become focused on delivery velocity at the expense of service quality.
Problem Management is the other area of strong complementarity. DevOps teams generate rich telemetry data and have strong capabilities in root cause analysis. ITSM's structured problem management practices provide a framework for ensuring that learning from production issues is captured, shared and acted upon systematically — not just within the team that experienced the issue.
"ITSM and DevOps don't have a values conflict. They have a process design challenge. The organisations that solve it are building the most resilient service delivery capabilities we see."
Making It Work in Practice
The organisations that have successfully integrated ITSM and DevOps tend to start from a position of mutual respect rather than territorial protection. ITSM practitioners who engage with DevOps teams on their terms — understanding the technical constraints and the delivery pressures — are far more likely to find workable compromises than those who insist on traditional ITSM practices without adaptation.
The practical starting points are usually change management (redesigning it for continuous delivery) and incident management (ensuring that production issues in DevOps environments are handled with the same rigour as incidents in traditionally managed environments). From those foundations, broader integration tends to follow.
Is your ITSM as good as it should be?
Our independent benchmarking assessment gives IT leaders a clear, evidence-based picture of where their service management stands — and exactly what to do about it.
Book a Free Strategy Session →