This article draws on survey data and commentary originally reported by ZDNet (January 2018), based on a DBMaestro survey of 244 IT professionals.
Where DevOps Adoption Stands
DevOps is no longer an emerging practice limited to forward-thinking startups. According to a DBMaestro survey of 244 IT professionals, a majority (55%) were already using DevOps in at least 20% of their projects at the time of publication, while one-third (33%) had extended DevOps practices to more than half of their active projects. That level of penetration signals a clear inflection point: the early-adopter phase is over, and the question is no longer whether to pursue DevOps but how far and how fast to take it.
Continuous Delivery Progress — and the Gaps That Remain
Continuous delivery of application code has become a realistic target for many teams: 54% of respondents in the survey reported they had fully achieved it. However, two adjacent domains lag considerably behind:
- Database continuous delivery: only 36% of respondents had fully achieved this.
- Infrastructure continuous delivery: only 31% had reached that milestone.
These gaps matter. An application pipeline that is fully automated but still depends on manual database change scripts or hand-crafted infrastructure provisioning introduces exactly the kind of toil, risk, and delay that DevOps is designed to eliminate. Closing those gaps is where many organisations need to focus their next phase of investment.
Deployment Frequency and Lead Times
One-third of survey respondents were already deploying more than once a week — a cadence associated with lower change failure rates and faster recovery. At the time of the survey, roughly 12% of the most ambitious teams reported a develop-to-production lead time of one day or less. The aspiration was for that figure to nearly double (to 23%) within the following year.
At the other end of the spectrum, 41% of respondents reported lead times exceeding a month, with hope that number would fall to around 23% over the same period. Develop-to-production lead time remains one of the most telling indicators of DevOps maturity: when it is measured in weeks or months, the organisation cannot safely respond to market changes, security vulnerabilities, or customer feedback at the pace modern software demands.
The Organisations Still on the Sidelines
Approximately 17% of survey respondents had not yet adopted DevOps practices in any meaningful way. If you are working inside one of those organisations, the immediate task is one of education and internal advocacy. That role — DevOps evangelist — is itself a leadership function, even without a formal title. It requires building the business case, identifying early wins, and connecting cultural change to measurable outcomes that resonate with executives.
Why DevOps Demands a Different Kind of Leader
DevOps is fundamentally a cultural and organisational transformation, not a tooling decision. Marianne Calder, Vice President at Puppet, has described it this way:
“DevOps is not something a company can practice or buy. It is a culture where continuous questioning, experimenting and learning is a part of everyone’s day-to-day activities.”
Marianne Calder, Vice President, Puppet
Calder emphasises that good leaders do not drive DevOps outcomes through direct control. Instead, they create conditions in which teams can re-architect systems, implement continuous delivery, and adopt lean management practices on their own. That is a meaningful shift from command-and-control management: the leader’s leverage is indirect, applied through culture-building, team enablement, and system design rather than task assignment.
Five Competencies of an Effective DevOps Leader
Software designer Des Nnorchiri has outlined a practical set of competencies required to lead DevOps initiatives effectively. These are not strictly technical skills — they span engineering understanding, architectural awareness, security ownership, communication, and collaboration.
1. Understanding of Modern Software Engineering
A DevOps leader does not need to be fluent in every programming language their teams use, but they do need a working understanding of programming algorithms and robust systems design. Without that foundation, it is difficult to evaluate trade-offs, support engineering decisions, or assess technical risk honestly.
2. Familiarity with Modern Software Architecture
Cloud-native architectures, containerisation, managed services, Linux distributions, and cloud-hosted databases are now standard infrastructure for most engineering teams. A DevOps leader who lacks familiarity with these building blocks will struggle to have credible conversations about system reliability, cost optimisation, or pipeline design. As Nnorchiri puts it: “DevOps managers will need to familiarize themselves with cloud instances and services, as well as lower-level software infrastructure such as Linux distributions and databases when deployed in a cloud.”
3. Confidence in Managing Security Incident Response
Security cannot be a separate silo in a DevOps culture; it belongs inside the delivery pipeline and inside the incident response process. A DevOps leader must be able to lead a team calmly and clearly during a security incident, work through root cause analysis, and use the experience to harden processes going forward. Nnorchiri’s advice is direct: “Be able to lead a team during an incident and work with the team to evaluate your security processes.”
4. Ability to Communicate Clearly Under Pressure
Clear communication is arguably the highest-leverage soft skill a DevOps leader can develop. During incidents, deployments gone wrong, or periods of organisational change, the ability to give precise instructions, set expectations, and acknowledge team stress without amplifying it is what separates effective leaders from technically skilled ones who struggle to lead. Nnorchiri notes: “At times you and your team will be under immense pressure and you will need to ensure that you can communicate and give instructions clearly whilst understanding the pressure your team might be feeling.”
5. Knowledge of Collaboration Techniques
DevOps breaks down the walls between development, operations, security, and business stakeholders. A leader who can facilitate structured collaboration — running effective blameless postmortems, leading architecture discussions, creating space for all voices to contribute — builds the psychological safety that sustains a learning culture. Nnorchiri describes this as “the ability to identify and brainstorm infrastructure changes, ensuring that all team members can easily contribute to the discussion.”
Putting It Together: Leadership as a Force Multiplier
The data and the commentary point in the same direction. DevOps adoption has reached the point where technical tooling alone no longer explains the difference between teams that deliver continuously and teams that are stuck in month-long release cycles. The differentiating factor is leadership quality: leaders who understand the technology well enough to be credible, who invest in culture deliberately, who communicate under pressure, and who measure success through team outcomes rather than personal control.
Whether you are stepping into a formal DevOps leadership role or acting as an internal advocate, developing these five competencies is where sustained impact begins.