Limited environment/Infrastructure resources24%
Inability to quickly identify the root cause of CI/CD pipeline failures48%
Lack of standardized CI/CD pipeline templates across the organization52%
Integrating security tools - inefficient security implementation leading to false positives32%
Poor communication across business and product teams/coordination challenges28%
Cost/resource management26%
Implementation of CI/CD into on-going projects and workflows21%
Internal resistance: training issues, culture, etc.12%
Inefficient implementation of CI/CD due to lack of expertise, poor training, etc.14%
Poorly written unit and acceptance testing6%
Strongly agree5%
Agree68%
Neutral16%
Disagree9%
Strongly disagree
Other (please explain in the comments)
No selling.
No recruiting.
No self promotion.
Rules of EngagementFAQsPrivacy
© 2025 Gartner, Inc. and/or its affiliates. All rights reserved.
Some clear indicators that a software engineering team may require an organizational redesign include:
- Excessively large teams that hinder agile performance
- Unclear or overlapping responsibilities across roles
- Misalignment of job titles with actual responsibilities
- Insufficient leadership for Centers of Excellence or Practice
- A proliferation of siloed teams and fragmented practices
To convince the C-suite, start by defining the specific organizational and performance issues currently limiting the team. Emphasize how these structural gaps impact performance, culture, and business outcomes. Support this case with a detailed plan that includes a career ladder aligned to defined job families, roles, reporting structures, and growth paths. Highlight the cultural benefits of the redesign, demonstrating how it would enhance both collaboration and team coherence across the department.