What inhibitors to DevOps adoption do you face?

Engineering, DevOps - 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). 

3 comments

https://www.pulse.qa

Pulse User

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). 

Pulse User

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.

Pulse User

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.