ENHANCING FLEXIBILITY AND EFFICIENCY IN IT PROJECT MANAGEMENT: A DUAL-AXIS AGILE-DEVOPS FRAMEWORK

УДК 004.89

ABSTRACT

The integration of Agile and DevOps practices is increasingly regarded as a key factor in enhancing adaptability and operational stability in IT project management. This paper proposes a strategy that combines iterative development, process automation, and cultural transformation within teams. The study is based on interviews with industry practitioners, enabling the identification of key barriers and challenges associated with implementing these approaches in real-world environments. A thematic analysis of the collected data is presented, forming the basis for a conceptual framework aimed at improving the effectiveness of Agile–DevOps integration and ensuring sustainable project outcomes.

АННОТАЦИЯ

Интеграция практик Agile и DevOps всё чаще рассматривается как ключевой фактор повышения адаптивности и операционной устойчивости в управлении ИТ-проектами. В данной статье предлагается стратегия, сочетающая итеративную разработку, автоматизацию процессов и культурную трансформацию команд. Исследование основано на интервью с практикующими специалистами, что позволяет выявить основные барьеры и проблемы внедрения данных подходов в реальных условиях. Представлен тематический анализ полученных данных, на основе которого разработана концептуальная модель, направленная на повышение эффективности взаимодействия Agile и DevOps и обеспечение устойчивых результатов проектов.

Keywords: Agile–DevOps Integration, IT Project Management, Continuous Integration and Delivery (CI/CD), organizational Culture, software development practices, DevOps Metrics (DORA).

Ключевые слова: интеграция Agile–DevOps, управление ИТ-проектами, непрерывная интеграция и доставка (CI/CD), организационная культура, практики разработки программного обеспечения, метрики DevOps (DORA).

Introduction

According to the 2023 State of DevOps report, elite performers deploy software 973 times faster than low performers. What sets them apart isn’t just tools—it’s how Agile and DevOps are combined. Agile and DevOps have emerged as two dominant methodologies for meeting the demands of modern software delivery. Agile promotes iterative development, customer collaboration, and adaptability to change [5], while DevOps enhances operational efficiency through automation, continuous integration and delivery (CI/CD), and collaboration across traditionally siloed teams [15].

Although both approaches aim to accelerate value delivery, they are often implemented separately, leading to fragmentation in tools, culture, and accountability. Agile may streamline planning and feedback, but without operational integration, delivery pipelines break down. Similarly, DevOps may automate deployments, yet lack clarity in prioritization without Agile alignment [8; 3].

Existing literature explores the technical and cultural components of both approaches. Agile’s iterative structure supports adaptability and user feedback, while DevOps enables continuous delivery and system reliability through automation [7; 11]. Early studies identified strong conceptual overlap between the two, but practical integration remains limited. Researchers such as Shahin et al. [15] and Lwakatare et al. [12] note that although tools like Jenkins, GitLab, and Docker are widely adopted, many organizations struggle to embed them within collaborative workflows.

Moreover, many case studies and empirical reports highlight persistent gaps. Cultural resistance is a recurring challenge, particularly in organizations where development and operations are historically siloed. Without leadership engagement, shared responsibility, and cross-functional collaboration, DevOps cannot thrive [3], [18]. Despite the widespread use of CI/CD, Infrastructure as Code, and automated testing, these tools are not effective unless embedded within a collaborative, value-driven culture [4], [10]. Forsgren et al. [6] propose DORA metrics to evaluate DevOps maturity (deployment frequency, lead time, change failure rate, and time to restore service), yet studies show that few SMEs apply these metrics consistently [16], [13].

What is missing from current models is a balanced, scalable approach that treats Agile and DevOps not as separate tools, but as complementary parts of a unified delivery system. Most academic work either focuses narrowly on technical enablers or presents abstract frameworks without empirical grounding [1]. SMEs, in particular, lack practical guidance for implementing both methodologies under resource and staffing constraints. Hybrid frameworks do exist, but they often ignore the day-to-day realities of cross-functional alignment, tool integration, and leadership inertia [17], [9].

This study addresses these gaps by proposing a dual-axis Agile-DevOps framework that combines technical practices such as CI/CD, IaC, and monitoring with cultural strategies like team autonomy, leadership support, and continuous learning. Based on qualitative interviews with IT professionals, this research explores how real teams navigate integration challenges, where they succeed, and where they encounter barriers. The goal is to provide actionable insights for building flexible and efficient project management strategies that align business goals with technical execution..

Materials and methods

To understand how organizations combine Agile and DevOps in practice, a qualitative multiple case study approach was used. This method provides insight into the challenges teams face, the strategies they apply, and the outcomes they achieve in real project settings.

Participants were recruited from five small to medium-sized enterprises (SMEs) operating in the software development, fintech, and infrastructure domains. These companies were selected based on their active use of Agile methodologies (e.g., Scrum, Kanban) and DevOps practices (e.g., CI/CD, Infrastructure as Code, cloud-native tools). The selection process followed purposive sampling principles, focusing on organizations that exhibited diversity in team size, DevOps maturity level, and industry sector. This ensured the inclusion of varied perspectives on Agile-DevOps integration.

The primary data collection method was semi-structured interviews. An interview guide was developed to ensure consistency while allowing flexibility in exploring specific experiences and contexts. The guide covered five thematic areas: (1) organizational background and context; (2) current Agile and DevOps practices; (3) cultural and leadership factors; (4) technical challenges and tool integration; and (5) success metrics and perceived outcomes.

Interviews were conducted remotely via video conferencing platforms, each lasting approximately 35–50 minutes. Participants included project managers, DevOps engineers, QA leads, and software developers with direct experience in Agile and/or DevOps initiatives. All interviews were audio-recorded (with consent) and transcribed verbatim for analysis.

The analytical process followed the thematic analysis method, as outlined by Braun and Clarke [2]. This involved multiple stages: familiarization with the data, generation of initial codes, grouping of codes into candidate themes, reviewing and refining the themes, and defining and naming final themes. Coding was conducted manually to ensure deep engagement with the data. Recurring concepts, language patterns, and contrasting cases were noted and compared across interviews.

To improve the validity of the findings, triangulation was used by comparing responses across different roles and organizations. Additionally, member checking was performed in selected cases by sharing key interpretations with participants and gathering feedback. Ethical guidelines were followed throughout the research process, including informed consent, voluntary participation, and anonymization of responses.

The combination of multiple sources (interviews, participant roles, organizational contexts) and the structured yet flexible analytical approach provided a strong foundation for drawing robust insights about Agile-DevOps integration in practice. The findings derived from this methodology informed the development of the dual-axis framework presented in the subsequent section.

To ensure the transparency and reproducibility of the analytical process, Table 1 presents a selection of representative raw data extracts and their corresponding codes, sub-themes, and final themes, as derived during the Braun and Clarke coding procedure. This coding frame demonstrates the progression from empirical data to interpretive themes.

Table 1.

Braun & Clarke Thematic Analysis Coding Frame — Selected Extracts

Results and discussion

Thematic analysis of the five interviews revealed several recurring themes that highlight both the technical and cultural dynamics involved in Agile-DevOps integration. The analysis produced five dominant themes: cultural resistance, tooling challenges, lack of visibility through standardized metrics, insufficient leadership support, and cross-functional collaboration gaps.

A. Key Themes Identified

Figure 1. Frequency of Interview Themes Mentioned by Participants

Tooling challenges, particularly involving fragmented systems and inconsistent usage of DevOps tools, were also prevalent. In some companies, teams used different CI/CD tools across departments without integration, leading to inefficiencies and duplicate work.

Another frequently discussed theme was the inconsistent use of metrics. Although all participants acknowledged the value of DORA metrics, few tracked them formally. Instead, companies relied on ad hoc indicators like delivery delays or informal team feedback.

Leadership support emerged as a mixed factor: in some cases, strong leadership enabled smoother transitions and cultural buy-in, while in others, a lack of strategic direction created confusion and resistance to change.

Cross-functional collaboration, while conceptually encouraged in Agile and DevOps philosophies, was often hindered by structural silos or unclear responsibilities. Teams that had implemented regular joint retrospectives or planning sessions reported more fluid communication and better alignment between development and operations.

B. Dual-Axis Framework in Practice

Based on these themes, a dual-axis integration framework was proposed and is illustrated in Figure 2. The framework positions Agile and DevOps not as separate methodologies but as interdependent pillars, jointly supported by two categories of enablers: technical and cultural.

The framework operates across two axes. The horizontal axis represents the integration continuum between Agile planning and DevOps execution: Agile practices (Scrum, Kanban, retrospectives) define the planning, prioritization, and feedback cadence, while DevOps practices (CI/CD, IaC, monitoring) govern how work is continuously built, tested, and deployed. The vertical axis represents the transformation depth, spanning from technical tool adoption at the surface level to cultural and organizational change at the foundational level.

Critically, the framework posits that neither axis is sufficient alone. Technical enablers — CI/CD pipelines, automated testing, containerization, and Infrastructure as Code — reduce manual effort, decrease deployment risk, and increase delivery speed. However, these tools only produce lasting outcomes when activated by cultural enablers: leadership commitment that models and reinforces cross-team collaboration; shared responsibility across development, QA, and operations roles; psychological safety that allows teams to fail fast and learn; and continuous feedback loops embedded in both retrospectives and operational monitoring dashboards. Without this cultural foundation, tools are adopted without being internalized, and practices are performed without being understood.

The two axes converge at the center of the framework in what is labeled Agile–DevOps Synergy: the state in which iterative planning and continuous delivery reinforce each other, teams share ownership of outcomes across the full software delivery lifecycle, and organizational performance is measured and improved using DORA metrics. This synergistic state is not a final destination but a dynamic equilibrium that requires ongoing leadership attention, team learning, and tooling evolution.

Figure 2. Dual-Axis Agile-DevOps Integration Framework

C. . Clarification of the 'Cultural Factors' Concept

The concept of 'cultural factors' as used in this study refers to the set of shared values, behavioral norms, and relational structures within an organization that either enable or inhibit the sustained adoption of Agile and DevOps practices. This definition draws on Schein's [14] organizational culture model, which distinguishes between surface-level artifacts (tools, rituals), espoused values (stated policies, leadership declarations), and underlying assumptions (deeply held beliefs about how work should be done and who is responsible for outcomes).

In the context of Agile-DevOps integration, cultural factors manifest in three observable dimensions: (1) Accountability structures — whether teams collectively own the delivery pipeline or whether responsibility is fragmented across functional silos; (2) Learning orientation — whether retrospectives and post-mortems result in process change, or whether they are performed as ceremonial compliance; and (3) Interpersonal trust — whether developers and operations engineers communicate proactively or treat each other as adversaries with competing incentives. Interview data confirmed that organizations exhibiting strong scores across these three dimensions consistently reported smoother integration, reduced tool fragmentation, and more consistent metric tracking.

D. Metrics and Perceived Outcomes

Table 2 presents an overview of key metrics discussed in the interviews. Deployment frequency and lead time were the most commonly referenced metrics, with some teams achieving daily or weekly deployments. However, many organizations still lacked systems to formally track change failure rates or time to restore service.

Table 2.

Summary of DevOps Metrics Identified in Interviews

While most participants reported subjective improvements in collaboration and delivery speed, few had empirical data to validate these gains. One participant highlighted a 30% reduction in incident reports following the implementation of cross-functional planning and CI/CD automation. These results highlight the central insight of this study: integration of Agile and DevOps must be approached as both a technical and cultural transformation. Focusing on tools alone may deliver short-term gains but fails to establish the systemic alignment necessary for long-term agility and reliability.

Conclusion

Agile and DevOps, when implemented in isolation, deliver only partial benefits. Their true value emerges at the intersection — where iterative planning meets continuous delivery, and where shared ownership replaces departmental boundaries. The evidence gathered across five SME organizations confirms that sustainable integration depends less on the tools an organization adopts and more on the cultural conditions it cultivates: shared responsibility, leadership commitment, and the psychological safety to learn from failure.

Five recurring challenges shaped the empirical findings: cultural resistance to cross-team collaboration, fragmented tooling ecosystems, inconsistent use of delivery metrics, unclear leadership direction, and structural barriers between development and operations. Taken together, these challenges informed the construction of the dual-axis framework — a model that places technical enablers (CI/CD, Infrastructure as Code, automated testing) and cultural enablers (accountability structures, learning orientation, interpersonal trust) on equal footing, treating neither as subordinate to the other.

For organizations — particularly SMEs operating under resource and staffing constraints — the framework offers a practical entry point: begin with the cultural foundations, align leadership, and let tooling choices follow from a shared understanding of goals. Scalability and long-term agility are not products of any single pipeline or platform, but of teams that communicate, measure, and improve together.

Future work may extend validation to larger enterprises or hybrid cloud environments, embed the framework within established governance models such as SAFe, ITIL, or SRE, and pursue longitudinal or quantitative studies to strengthen the empirical base.

References:

1. Bass L. DevOps: A Software Architect’s Perspective. – Boston: Addison-Wesley Professional, 2018.
2. Braun V., Clarke V. Using thematic analysis in psychology // Qualitative Research in Psychology. – 2006. – Vol. 3, No. 2. – P. 77–101.
3. Doukoure B., Badreddin L. Adopting DevOps in practice: A case analysis in agile software development // Proceedings of the 11th International Workshop on Cooperative and Human Aspects of Software Engineering. – 2018. – P. 113–116.
4. Erich F., Amrit C., Daneva M. A qualitative study of DevOps usage in practice // Journal of Software: Evolution and Process. – 2017. – Vol. 29, No. 6. – P. e1885.
5. Fitzgerald B., Stol K.-J. Continuous software engineering: A roadmap and agenda // Journal of Systems and Software. – 2017. – Vol. 123. – P. 176–189.
6. Forsgren N., Humble J., Kim G. Accelerate: The Science of Lean Software and DevOps. – Portland: IT Revolution, 2018.
7. Gruhn V., Schäfer C. The impact of agile methods on software and system architecture // International Journal of Software Engineering and Knowledge Engineering. – 2015. – Vol. 25, No. 2. – P. 151–197.
8. Hémon P., Estublier A., Ahmed-Nacer M. Bridging the gap between agile and DevOps: A case study // Journal of Software: Evolution and Process. – 2020.
9. Hilton A. Mastering Agile-DevOps integration: Overcoming challenges for enhanced productivity and quality // Medium. – 2023.
10. Kim G., Debois P., Willis J., Humble J. The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations. – Portland: IT Revolution, 2016.
11. Lenarduzzi V., Taibi D., Janes A. Does DevOps affect software architectures? An empirical study on technical debt // IEEE Transactions on Software Engineering. – 2020. – Vol. 46, No. 6. – P. 626–643.
12. Lwakatare L. E., Kuvaja P., Oivo M. Dimensions of DevOps // Agile Processes in Software Engineering and Extreme Programming. – 2016. – P. 212–217.
13. Maharao C. S. A study on impact of Agile and DevOps practices on software project management success // ShodhKosh: Journal of Visual and Performing Arts. – 2024. – Vol. 3, No. 1. – P. 757–767.
14. Schein E. H. Organizational Culture and Leadership. – San Francisco: Jossey-Bass, 1985.
15. Shahin M., Babar M. A., Zhu L. Continuous integration, delivery and deployment: A systematic review // IEEE Access. – 2017. – Vol. 5. – P. 3909–3943.
16. Team P. 26 DevOps KPIs and metrics: Guide to DORA progress // Pluralsight. – 2023.
17. Team P. Metrics for different levels of Agile DevOps maturity // Plandek Guide. – 2024.
18. Wiedemann A., Wiesche M., Krcmar H. The role of culture in DevOps: Investigating adoption barriers // Journal of Information Technology. – 2019. – Vol. 34, No. 4. – P. 289–309.