This article is based on reporting originally published by TechRepublic, drawing on survey data from cloud sandbox software provider Quali and analyst commentary from Enterprise Management Associates (EMA) and Forrester Research.
DevOps Adoption Is Growing—But So Are the Obstacles
As more organizations turn to DevOps to improve software delivery speed and team productivity, a consistent set of implementation challenges keeps surfacing. A survey of more than 2,000 IT industry executives conducted by Quali found that infrastructure bottlenecks, cultural friction, and tool sprawl are among the most cited barriers.
The survey highlighted a striking infrastructure gap: 54% of respondents reported no access to self-service infrastructure, relying instead on ticket-based provisioning systems that slow delivery and increase time to market. Only 23% said infrastructure could be provisioned in under 24 hours, while 33% said it takes up to a month—and 26% reported it takes even longer than that.
Torsten Volk, managing research director of hybrid cloud and infrastructure management at Enterprise Management Associates (EMA), summed up the root problem: “Despite the immense popularity of DevOps today, research data shows a general lack of central governance and automation when it comes to creating new application environments. This leads to pockets of developers using their favorite, often not well-integrated, DevOps tools.”
The survey also found that DevOps teams are using a mix of open source and commercial tools. The most widely adopted at the time of the survey included Jenkins (21% of respondents), Docker (16%), Puppet (14%), and Chef (13%).
Forrester analyst Diego Lo Giudice captured a broader truth about DevOps maturity: “Mastering DevOps isn’t only about innovating on the ‘cool’ technologies faster; it’s also about building the capabilities to perform modern application development across the board. The underlying cultural shifts, process improvements, and automation of DevOps build the foundation for development teams to mature to the next generation of modern software development.”
The Top 10 Barriers to DevOps Implementation
Based on the survey findings and guidance from Quali, here are the ten most common challenges IT executives identified—along with recommended approaches for overcoming each one.
1. Culture
Cultural resistance is consistently ranked as the top barrier to DevOps adoption. Siloed development and operations teams that are accustomed to separate workflows, separate goals, and separate accountability structures do not naturally converge without deliberate effort.
Solution: Build a collaborative culture with shared goals and shared ownership of outcomes. Identify internal DevOps champions—employees who understand the value of cross-functional collaboration and can model the right behaviors for their peers. Structural changes like shared on-call rotations, joint retrospectives, and unified KPIs help reinforce culture change over time.
2. Test Automation
Many teams invest heavily in CI/CD pipeline tooling while neglecting automated testing. The result is faster deployments that still break in production—undermining the very reliability DevOps is supposed to deliver.
Solution: Treat continuous testing as a first-class citizen in your DevOps pipeline, not an afterthought. Automated unit, integration, and end-to-end tests should run on every commit. Security testing (SAST, DAST, dependency scanning) must also be embedded into the pipeline from the start rather than bolted on later.
3. Legacy Systems
Older applications and infrastructure were not designed with automation or continuous delivery in mind. Integrating them into a modern DevOps workflow is one of the most technically demanding challenges teams face.
Solution: Include legacy infrastructure and applications explicitly in your DevOps planning—do not assume the model only applies to greenfield projects. Identify which legacy components can be wrapped with APIs, containerized, or gradually refactored. Accept that legacy coexistence is a long-term project and plan accordingly.
4. Application Complexity
Modern applications often span on-premises infrastructure, public cloud, private cloud, and containerized environments. This heterogeneity makes it difficult to standardize deployment pipelines and maintain consistent environments across the software lifecycle.
Solution: Address architectural decisions early. Evaluate whether your application architecture is compatible with your target deployment model—whether that is Kubernetes on cloud, VMs on-premises, or a hybrid combination. Retrofitting architecture decisions is far more expensive than making them upfront.
5. No DevOps Plan
Some organizations declare a DevOps initiative without defining what success looks like, who owns it, or how progress will be measured. Without a clear roadmap, DevOps efforts stall or fragment across teams.
Solution: Create a structured plan that includes milestones, designated project owners, and well-defined deliverables. Define measurable outcomes—such as deployment frequency, lead time for changes, mean time to recovery (MTTR), and change failure rate—so progress can be tracked and communicated.
6. Managing Environments
Maintaining consistent, reproducible environments across development, testing, staging, and production is a persistent pain point. Environment drift—where configurations diverge over time—causes bugs that are difficult to trace and reproduce.
Solution: Standardize and automate environment provisioning using infrastructure-as-code tools and, where appropriate, cloud sandboxing platforms. Environments should be treated as ephemeral and reproducible, not as long-lived snowflakes that accumulate manual changes.
7. Skills Gap
DevOps requires a broad and evolving skill set—spanning scripting, cloud platforms, containerization, monitoring, and security—that many existing team members were not hired to possess.
Solution: Invest in structured training programs and give engineers protected time to develop new skills. Standardize processes and establish common operational procedures so that institutional knowledge is codified rather than locked in individuals. Pair experienced DevOps practitioners with team members who are earlier in their learning curve.
8. Budget
DevOps tooling costs are frequently underestimated. Teams often plan around open source tools assuming the cost is zero, then discover that integration, operational overhead, licensing for enterprise features, and training add up significantly.
Solution: Build a realistic total cost of ownership (TCO) model that accounts not just for licensing but for integration complexity, staffing, training, and ongoing maintenance. Open source is not free—it shifts costs from licensing to operations. Include these factors when presenting budgets to leadership.
9. Tool Sprawl
The DevOps tooling ecosystem is vast. Teams often adopt tools organically—different teams choosing different tools for similar jobs—resulting in fragmented, poorly integrated toolchains that are difficult to maintain and that create inconsistency across pipelines.
Solution: Establish a governed toolchain strategy at the organizational level. Evaluate tools against clear criteria—integration capability, community support, security posture, and operational overhead—before adopting them. Consolidating tools may have an upfront cost but reduces complexity and maintenance burden over time.
10. Lack of Executive Support
DevOps transformations require sustained investment in people, tooling, and process change. Without executive sponsorship, these initiatives are vulnerable to being deprioritized when budgets tighten or competing projects arise.
Solution: Translate DevOps outcomes into business language that resonates with executive stakeholders—faster time to market, reduced incident frequency, lower cost of defects, and improved developer retention. Frame DevOps investment as a strategic capability rather than a technical preference. Early wins and measurable metrics are the most effective tools for building and maintaining executive buy-in.
Key Takeaways
- Infrastructure bottlenecks—particularly the lack of self-service provisioning—remain a major drag on DevOps velocity.
- Cultural and organizational challenges are as significant as technical ones; tool adoption alone does not create a DevOps culture.
- Test automation and security must be integrated into the pipeline from the start, not added after the fact.
- Legacy system integration requires explicit planning and should not be treated as out of scope.
- Tool sprawl and underestimated costs are common pitfalls; a governed toolchain strategy mitigates both.
- Executive support is a prerequisite for sustained DevOps transformation—and it must be earned through demonstrated, measurable outcomes.
DevOps implementation is a journey that spans technology, process, and culture. Understanding these barriers in advance—and planning deliberately to address them—significantly improves the likelihood of a successful, lasting transformation.