What inhibitors to DevOps adoption do you face?

4.5k views1 Upvote4 Comments

CIO, Self-employed
IMHO Lack of talent, low budget/salaries are usually the first inhibitors to start a DevOps Project. 
With people: professional jargon is a real problem. Some terminology has different meanings depending on the expertise of people. Finding common grounds to define interoperatibility among different working areas, might become quite difficult.
Most of all, what is really complex is to achieve interoperatibility of good, solid systems and others with lack of vision/profesionalism for the design of some dbs and interfaces.
Some of them don't even full fill to the design standards of their time, or solved one specific problem (only one). 
Chief Information Officer in Software, 501 - 1,000 employees
Lack of patience from business leadership can be a big inhibitor.  You are effectively transforming the delivery culture and it takes time to train, practice, learn, re-train, lather, rinse, repeat.  Your journey to continuous improvement is never finished.  Partner up with your peers and remain close to your DevSecOps adoption.  The changes you will see are worth working through any inhibitor.
CIO in Construction, 51 - 200 employees
DevOps literature clearly shows that providing a complete and clear definition of the term is a challenge. The geographical distribution might also pose other, eg process related, challenges. Automating and having common tools and processes have always been challenging.
Venture Partner, VP Products, Chief Product Officer in Energy and Utilities, 10,001+ employees
Hiring good talent who have both the technical experience but also sdlc agile Kanban process experience to execute on infrastructure as code.

Content you might like

Limited environment/Infrastructure resources31%

Inability to quickly identify the root cause of CI/CD pipeline failures45%

Lack of standardized CI/CD pipeline templates across the organization53%

Integrating security tools - inefficient security implementation leading to false positives38%

Poor communication across business and product teams/coordination challenges26%

Cost/resource management26%

Implementation of CI/CD into on-going projects and workflows22%

Internal resistance: training issues, culture, etc.14%

Inefficient implementation of CI/CD due to lack of expertise, poor training, etc.19%

Poorly written unit and acceptance testing9%



We are not doing regression testing10%

25% manual, 75% automated50%

50% manual, 50% automated27%

100% manual, 0% automated8%

Don't know2%


1.6k views3 Upvotes2 Comments

CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.
Read More Comments
41k views131 Upvotes319 Comments