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%
What is more important is to follow best practices in development with proper comments and well organised code structure
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).