This article is based on survey findings originally reported by automotiveit.com, citing research conducted by F5 Networks at DevOpsDays Amsterdam.
DevOps Adoption Is Being Held Back — But by What?
Despite broad recognition that DevOps accelerates software delivery and improves collaboration, many enterprises are still struggling to implement it at scale. A survey of 170 IT professionals conducted by F5 Networks at its DevOpsDays Amsterdam gathering identified the three most significant barriers standing in the way of successful DevOps adoption.
The Three Biggest Obstacles to DevOps
1. Corporate Bureaucracy and Rigid Processes
According to the survey, 40% of respondents identified corporate bureaucracy as the number one obstacle to DevOps implementation. Specifically, participants cited:
- Difficult-to-change testing processes
- Rigid ticketing systems
- Heavy reliance on manual workflows
These organizational constraints slow down the iterative, automated delivery cycles that DevOps depends on. When change approval processes require multiple sign-offs or manual interventions, the speed gains promised by continuous integration and continuous delivery (CI/CD) pipelines are quickly eroded.
2. Legacy Code and Legacy Systems
The second most commonly cited barrier was the prevalence of legacy code and legacy infrastructure within organizations. Many enterprises run core business functions on systems that were never designed with automation, APIs, or modern deployment pipelines in mind. Refactoring or replacing these systems is often costly, time-consuming, and politically sensitive — making it difficult to apply DevOps practices uniformly across the organization.
This challenge is particularly acute in sectors such as finance, manufacturing, and healthcare, where mission-critical applications may have been running unchanged for decades.
3. Incompatible Production Environments
The third major challenge identified was environment incompatibility — situations where development, staging, and production environments differ enough to cause deployment failures or unpredictable behavior. This undermines the reliability of CI/CD pipelines and erodes confidence in automated releases, pushing teams back toward slower, manual deployment practices.
Why DevOps Still Matters
Rodrigo Albuquerque, DevOps solution developer at F5 Networks, emphasized that despite these hurdles, the business case for DevOps remains compelling:
“DevOps is clearly playing an ever bigger role. It boosts efficiency through the optimization of processes, the disappearance of silos, automation tools, standardizing of platforms and a strong culture of collaboration.”
Rodrigo Albuquerque, DevOps Solution Developer, F5 Networks
Albuquerque also expressed optimism about the path forward, noting that automation will ultimately drive broader acceptance of DevOps across organizations that are currently held back by manual processes and organizational inertia.
A Positive Trend: Cross-Team Collaboration Is Growing
F5 Networks also noted an encouraging trend emerging from the survey: increased cooperation across traditionally siloed teams. Breaking down the walls between development, operations, security, and QA is a foundational principle of DevOps culture, and the data suggests organizations are making measurable progress in this area even where tooling and process challenges remain.
Key Takeaways for DevOps Practitioners
- Audit your processes before your tools. Bureaucratic workflows are frequently the root cause of DevOps stagnation — not a lack of tooling.
- Create a legacy modernization roadmap. Legacy systems rarely need to be replaced all at once; incremental strangler-fig patterns and API wrappers can enable DevOps practices without a full rewrite.
- Standardize environments. Infrastructure-as-code tools (such as Terraform, Ansible, or Pulumi) and containerization (Docker, Kubernetes) reduce environment drift and make deployments more predictable.
- Invest in automation incrementally. Even partial automation of testing and deployment pipelines can reduce bottlenecks caused by manual approval gates.
- Measure collaboration, not just velocity. Cultural metrics — such as cross-team incident response participation and shared on-call rotations — signal genuine DevOps maturity.
The F5 Networks survey is a useful reminder that DevOps transformation is as much an organizational and cultural challenge as a technical one. Addressing bureaucracy and legacy debt alongside toolchain modernization gives enterprises the best chance of achieving the agility DevOps promises.