Exploring the Beneﬁts of Combining DevOps and Agile

: The combined adoption of Agile and DevOps enables organizations to cope with the increasing complexity of managing customer requirements and requests. It fosters the emergence of a more collaborative and Agile framework to replace the waterfall models applied to software development ﬂow and the separation of development teams from operations. This study aims to explore the beneﬁts of the combined adoption of both models. A qualitative methodology is adopted by including twelve case studies from international software engineering companies. Thematic analysis is employed in identifying the beneﬁts of the combined adoption of both paradigms. The ﬁndings reveal the existence of twelve beneﬁts, highlighting the automation of processes, improved communication between teams, and reduction in time to market through process integration and shorter software delivery cycles. Although they address different goals and challenges, the Agile and DevOps paradigms when properly combined and aligned can offer relevant beneﬁts to organizations. The novelty of this study lies in the systematization of the beneﬁts of the combined adoption of Agile and DevOps considering multiple perspectives of the software engineering business environment.


Introduction
The software development process can be viewed as a set of tasks required to produce high-quality software. The literature shows that the quality of the software produced reflects the way the process was carried out [1][2][3]. Although several software development processes exist, generic activities common to all of them stand out, as Sommerville [4] highlights, such as software specification (e.g., requirements definition, software constraints), software development (e.g., software design and implementation), software validation (e.g., software must be validated to ensure that the implemented functionality conforms to what was specified), and software evolution (e.g., software evolves as per customer need). The software development process provides an interaction between users and software engineers, between users and technology, and between system engineers and technology. In this sense, software development is an interactive learning process, and the result is an embodiment of knowledge gathered, transformed, and organized as the process is conducted.
A software development methodology includes a set of activities that assist in the production of software. These activities result in a product that demonstrates how the development process was conducted. Agile methodologies arise from the need to overcome the difficulties and disadvantages of applying traditional methodologies in project management and implementation. The Agile methodology assumes short periods of time between each delivery to ensure early and continuous delivery of software susceptible to evaluation [5]. In [6] it is also recognized that software implementation according to this paradigm is interactive and incremental, enabling early confirmation of whether or not the delivered artifact meets the needs and making the respective corrections with low risk and cost.
The main social and human factors involved in the adoption of Agile methodologies are the impact on organizational culture, namely by the collaborative culture imposed on developers and the implications of being embedded in an Agile team [7,8]. Constant feedback to all team participants on the activities being carried out, and the commitment to the team's goals, are highlighted in Junker et al. [9] as key elements for a well-functioning Agile team. Feedback and collective awareness are essential as opposed to individualism and lack of communication. This view is also confirmed by Sweetman and Conboy [10] when they highlight that feedback loops are the essence of the empirical and complex processes found in software engineering that require continuous adaptation based on learning obtained daily. Furthermore, complex projects are very unpredictable and therefore need a process that incorporates unpredictability [11].
Inspired by the success of Agile methods, the DevOps (Development and Operations) movement emerged that aims to take this line of reasoning to a higher level. This movement comes to break the traditional culture where there was almost no interaction between teams and, as highlighted by Luz et al. [12], the goal is to create a culture of collaboration between development and operations teams that allows increasing the flow of completed work. In summary, it is intended to increase the frequency of deployments while increasing the stability and robustness of the production environment. Beyond a cultural change, the DevOps movement also focuses on the practices of automating the various activities required to deliver quality code into production, such as creating environments for testing, automating testing, configuring infrastructure, data migration, auditing, and security, among others [13,14].
In the literature, we can essentially find studies on DevOps that explore ways to align development teams with operations [15], the benefits that this methodology can bring to organizations [16], and the challenges that are posed [17]. However, there is a research gap in the characterization of the simultaneous adoption of Agile and DevOps in organizations. In this dimension, the number of available scientific studies is limited and they mostly present individual views of their implementation, which does not allow for a sufficiently comprehensive characterization of the benefits of their combined adoption. We acknowledge the study conducted by Hemon et al. [18], which characterizes the different phases of Agile to DevOps transition (e.g., Agile, ongoing integration, and constant delivery), while Melgar et al. [19] explore the benefits of the combined SCRUM-DevOps approach in terms of increasing speed during the deployment process and increasing the quality of software processes. In both studies, there is just one empirical case study, which makes it difficult to generalize the findings. In this sense, this study seeks to bridge this research gap and presents an analysis of the benefits that can be found by the combined approach of DevOps and Agile considering a comprehensive set of twelve case studies that are representative of practices of simultaneous adoption of both methodologies. This approach supported by multiple case studies avoids the individual limits of each company's vision and reduces the risk of bias, and allows comparing, grouping, and systematizing the main benefits of the combined adoption of both methodologies.
The rest of this manuscript is organized as follows: Initially, a theoretical contextualization of the DevOps model is performed and the similarities between DevOps and Agile are explored. Next, the methodology and associated methods adopted in the study are described. This is followed by the presentation of the results and discussion of their relevance to the perception of the benefits of the combined adoption of DevOps and Agile. Finally, the conclusions are enumerated. It is also in this last phase of the manuscript that the limitations of the study are addressed and some suggestions for future work are provided.  [20]. They explained how the developers' teams (Dev) and operations teams (Ops) could contribute to more agile and scalable software development. Tight integration between Dev and Ops to safely achieve several software deployments (more than 10) in a single day was a disruptive idea regarding software development and its evolution. Later, Patrick Debois coined the term DevOps (Development and Operations) and created the DevOps Day event [21]. Although the DevOps movement has been discussed for more than a decade [13][14][15]22] it still lacks a unique formal definition. For Wiedemann et al. [23], the lack of a unique definition could be intentional to allow each team to choose the definition that better suits its needs. Nevertheless, several authors proposed definitions such as the one by Leite et al. [13]-"DevOps is a collaborative and multidisciplinary effort within an organization to automate continuous delivery of new software versions while guaranteeing their correctness and reliability"-and others view it as a combination of values, principles, methods, practices, and tools [24]. Some other common definitions can be found in [23].
One of the key points in the execution of a project is the approach used to manage it. The traditional approach based on the waterfall model looks at the project in a linear way with several events, while in the iterative approach the development of software is undertaken through successive progress [25]. Therefore, it is common that the system is presented still incomplete or with some deficient parts. The objective is that the refinement of the product happens in stages until the desired result is achieved. The software development process does not end with the release of the code, but only when it closes the feedback loop between those who write the code and those who use it. DevOps aims to remove the barriers between traditionally independent teams: development and operations. Under the DevOps approach, these teams should work together across the entire software life cycle, from development and testing through deployment to operations. More than only a technical subject, DevOps deals with the organizational and human issues that arise in the software life cycle. It promotes a culture of collaboration, integration, and communication between teams to reduce the disconnect between them while assuring the delivery of software in an agile, safe, and stable way. According to Rajapakse et al. [14], the DevOps movement is currently a widely adopted software development approach having as a major benefit the ability to deploy releases more frequently and at a higher rate.
Some related concepts used in conjunction with DevOps are Continuous Integration, Continuous Delivery, and Continuous Deployment. As noted in [14], these concepts are considered key practices within DevOps, but are not always clearly used, as stressed by Stahl et al. [24]. Continuous Integration is a development practice where developers frequently integrate the code they produce, that has successfully passed testing, to the project under development [24]. Those integrations occur typically once a day. Continuous Delivery is a development practice where the software is kept in a reliable deployable state at any time [14]. Potentially, after every change, the software can be released. This leads to several release candidates that are evaluated. The deployment to production is made manually by a team member, with the appropriate authority, who decides when and which candidate should be released [14]. Apart from Continuous Delivery, in Continuous Deployment, release candidates resulting from software changes are automatically deployed to production without the intervention of any team member [14,24].
Regarding how organizations could adopt DevOps and measure its success, the CALMS framework is considered a foundational model for DevOps. CALMS is an acronym for Culture-Automation-Lean-Measurement-Sharing. CALMS was created by Jez Humble, co-author of The DevOps Handbook. The acronym highlights the five core elements of CALMS [23]: • Culture: a cultural change focusing on collaboration and integration between developers' team and operations' team; Sharing: knowledge and best practice should be shared in the organization and across organizational boundaries.
Security issues concerning DevOps led to the spread of another term: DevSecOps. It adds "Security" to "Development" and "Operations", which were already part of the De-vOps term. According to Rajapakse et al. [14], security is often treated as a non-functional requirement, handled at a later stage of the software development life cycle. Under DevSec-Ops, security should be built into every part of the DevOps life cycle. The purpose of the DevSecOps philosophy is to align the speed of code delivery with building secure code, merged into one streamlined process.
The application of DevOps still must deal with some problems and concerns that can limit its use (e.g., resistance to change, organizational vision, legacy systems) [26]. Misuse of the term, lack of clear guidelines and, as already mentioned, the lack of a clear definition creates some ambiguity about how to use DevOps principles. Those principles presuppose that, before DevOps, development teams and operations teams were working independently with almost no knowledge about each other's work. This lack of knowledge across teams is not, in general, as deep as DevOps assume. The whole software development process is improved with better collaboration between teams, as DevOps advocates, but it does not mean that DevOps teams did not previously cooperate. Another concern around DevOps is that its adoption rate is still low.
There is a close relation between DevOps and Agile methods in software development. According to Leite et al. [13], DevOps is an evolution of the Agile movement since software development under Agile favors small release iterations with customer reviews.

Similarities and Differences between DevOps and Agile
In the context of Software Engineering, as discussed in this paper, DevOps can be understood as a behavioral evolution of Agile development [27], which was gradually conceived through practical experiences of implementation in software development. However, it is important to point out that the Agile method has its focus directed specifically to software development [28], while DevOps aims to involve the software development area in the implementation and operation of the software developed or still under development, which shows us that DevOps processes are being implemented within the Agile processes.
Currently, in the professional community of Information and Communication Technologies (ICT) there is a growing consensus, in practice, that DevOps can be understood as "DevOps = Agile + Lean + IT service management (ITSM)" [29]. In its method and processes, DevOps adopts characteristics of frameworks related to the technical area of Agile software development together with ICT management processes. Complementarily, other relevant methodologies (e.g., Extreme Programming, Dynamic Systems Development Method, Kanban, SCRUM) have approaches intrinsically related to the Agile philosophy [30][31][32][33]. SCRUM is very well-known and intensely used in the Agile method, and is generally enhanced by the Kanban tool, for managing the workflow of software development, but which also fits very well into the DevOps development process itself [34]. Table 1 presents the problems or gaps in the Agile method that are solved by adopting the DevOps method.  [35]).

Problem with Agile Development DevOps Solution
Delivery of new features to the customer is often delayed.
DevOps tools are used to test and release new features as they are completed.
Completed software components are not compatible with each other.
Open interfaces and test automation make it possible to divide development into independent yet compatible parts.
Quality of the product is not ensured properly prior to release.
DevOps tools and practices help automating quality assurance and reduce the need for repetitive manual work.
New features break old functions. The quality of existing functions is ensured quickly and automatically after each change.
Budget goals and deadlines are missed.
The tools and procedures of DevOps increase the transparency and predictability of the development work.
Developer teams and IT operations crews are not cooperating.
Developer teams and IT operations crews agree upon responsibilities together. Their goals are unified.
In the context of the Agile method workflow, under the SCRUM framework implementation, DevOps presents four metrics [36] that are directly related to software delivery through enhanced software engineering: i-waiting time, ii-deployment frequency, iiimean time to restore (MTTR), and iv-change failure percentage. These metrics can be implemented in the execution cycle of the Agile by SCRUM approach, enhancing the qualitative process of the organizational performance of software companies, in meeting the planned objectives, because it increases in a relevant way the level of monitoring and maturity of the activities performed in each work cycle.
Organizations that implement Agile methodologies focus on productivity and process optimization by reducing execution time [37]. However, software development environments are shrouded in constant change, with continuous interactions of teams that focus on deliverable products. DevOps processes can improve the interactivity of the development teams, improving the integration process of the stakeholders of a project in an Agile environment, facilitating the continuity of the processes in a more balanced and stable way.
According to [38], the DevOps culture can be implemented to carry out an incident management process for deliverable products, allowing Agile development teams to be continuously monitored, because it integrates the software deployment process by monitoring operations, as provided by the DevOps framework. Therefore, DevOps enhances the stability of the Agile cycle, as we mentioned before; that is, while Agile focuses on productivity in product deliverables in a more technical approach around ICT [39], DevOps directs its processes to checking the level of effectiveness of what is produced in the work cycles of the development teams. Therefore, in this central aspect of integration, there will be a tendency toward an improved qualitative increment in the scope of Software Engineering.
Within what we have discussed so far, it was verified that the processes originated from Agile methodologies are the structural base of DevOps [18,39], and that the union of these methodologies increases the level of intelligence of the information system that is generated in the work cycles, because it implements several functions, such as Developers, System Architects, Product Owners, Release Engineers, and Testers. Therefore, the level of collaboration is elevated with professionals that are beyond the initially foreseen roles, for example, in the SCRUM approach that is currently used in Agile, promoting the creation of cross-functional teams in the context of the DevOps approach.
The approach of development teams that implement Agile methodologies, to operations teams as proposed by DevOps, tends to accelerate the software release process, with studies [40] indicating that in addition to acceleration, there is an increase in software quality in terms of reliability and maintainability. As a result, the deliverable product meets the conditions foreseen in the essential objectives of the project, from software development (Agile), as in deployment and testing in operations (DevOps). However, despite DevOps decreasing the gap between Developers and Operators, in terms of standardization, the DevOps methodology lacks a simple approach or a roadmap to be followed for its implementation in an organization [41], leaving it up to companies to define their standards and metrics. This can present as a complicating factor, very dependent on the maturity level of organizations and work teams, which will have to define their specific integration processes in a DevOps approach.

Methodology
This study adopts a qualitative methodology to explore the benefits of the combined adoption of DevOps and Agile. This type of methodology is used in the context of social sciences and engineering and, according to Merriam and Tisdell [42], is concerned with a level of reality that cannot be quantified, exploring meanings, aspirations, beliefs, values, and attitudes that correspond to a deeper space of relationships, processes, and phenomena, and cannot be reduced for operationalization of variables. Dyba et al. [43] recognize that the software industry presents lines of research that are not only limited to exploring technical software engineering issues, but also need to look at the challenges of the intersection between technical and non-technical aspects. In this sense, adopting a purely quantitative approach is insufficient. Moreover, phenomena addressed in the field of project development in a DevOps and Agile paradigm are complex and unique. Therefore, the qualitative approach adopted in this study allows for exploring and understanding the relationships and activities performed by organizations in their software development activity.
In the scope of this study, twelve case studies were incorporated that report the simultaneous inclusion of DevOps and Agile methodologies in their software development teams. These cases correspond to reports and press releases from commercial vendors of reference in this area. The data come from secondary sources and the authors have not made any changes to the press releases that represent the view of each manufacturer. No summarization of the press releases has been made. It cannot be guaranteed that there is no risk of bias since the identified benefits come from press releases from commercial companies in the area and that have commercial goals in the market. However, to minimize this risk, external and internal validity mechanisms were used. To ensure external validity, multiple case studies were used of companies in different geographic areas, and to ensure internal validity, the same identifier was used to associate similar benefits between the case studies. Table 2 presents brief descriptions of the profiles of the case studies. In general, it can be concluded that the area of activity of the organizations is similar through the offer of IT products and services based on cloud architecture. We also highlight the offer of consulting services in the field of web and mobile development, and the offer of complementary services in the field of artificial intelligence, big data, and cybersecurity.
Thematic analysis is an interpretive data analysis method widely used in the social sciences and engineering and was adopted in the context of this study to identify common benefits in the combined adoption of DevOps and Agile. Flexibility is, according to Braun and Clarke [44], one of the benefits of thematic analysis. Through its theoretical freedom, the thematic analysis provides a flexible and useful research tool that can potentially provide a rich and detailed set of information about the data. Figure 1 shows the process of conducting data. The step begins with the coding process in which one coded the advantages present in each case study report. After that, an iterative process follows in which common themes of the advantages among the case studies are identified. Finally, the last step consists of accounting for the benefits identified in the case studies. This approach allows for a ranking of the top benefits.

CS1 India
A company that operates in the IT outsourcing services market in building technological solutions in areas such as web apps, mobile apps, cloud strategy, analytics and business intelligence, testing, quality assurance services, and Agile project management. Their report looks to different ways to enable DevOps in Agile environments.

CS2 USA
Information technology company and advanced training for IT professionals in the fields of programming and technological development. Their report explores the relevance of Agile principles for deployment activities.

CS3 Canada
A global company that offers consulting services to help companies adjust their development teams by integrating new practices and technologies. Their report explores how Agile practices should be updated considering the needs of operations teams in organizations.

CS4 USA
Cloud services provider offering technology infrastructures based on public cloud, private cloud, hybrid cloud, and multi-cloud. Their report explores the difference and similarities between both paradigms.

CS5 Australia
Australian software company that develops products for software developers, project managers, and other software development teams.
Their press release presents how automation processes can be implemented using a combination of both paradigms.

CS6 USA
Global business and technology consulting firm dedicated to helping organizations leverage emerging technologies and the latest business management thinking to achieve competitive advantage and mission success. Provides consulting and training services, primarily targeted at executives. Their article explores the differences between the two paradigms and suggests points of convergence between them.

CS7 USA
Company specialized in the dissemination of technological information in the field of information and communication technologies. Their press release looks to important aspects observed while combining DevOps and Agile.
CS8 USA Multinational company in information technologies that develops automation solutions and advanced knowledge in areas such as automation, enterprise DevOps, data-driven business, and adaptive cybersecurity. Their article explores the role that Agile practices can play in DevOps.

CS9 Switzerland
Company that operates mainly in the European market in providing captivating scalable cloud-based solutions. Their article looks at the isolated benefits of each paradigm and tries to predict the benefits of their combined adoption.

CS10 India
Company that develops technological solutions for the education field and relies on the application of the Agile scalability paradigm, especially the SAFe model. Their article explores the change-driven management approach and looks at how DevOps and SCRUM address this challenge.

CS11 Germany
IT company that operates in the global market implementing cloud solutions, DevOps, software testing, quality assurance, artificial intelligence, and big data. Their press release looks at the problems in software engineering that the joint adoption of both paradigms can solve.

CS12 UK
A consulting company that aims to optimize work processes in organizations using cloud solutions, slack, and Trello services. Their press release looks at the role of the cloud and Agile methodologies in developing the DevOps paradigm. the thematic analysis provides a flexible and useful research tool that can potentially provide a rich and detailed set of information about the data. Figure 1 shows the process of conducting data. The step begins with the coding process in which one coded the advantages present in each case study report. After that, an iterative process follows in which common themes of the advantages among the case studies are identified. Finally, the last step consists of accounting for the benefits identified in the case studies. This approach allows for a ranking of the top benefits.

Results
The twelve case study reports associated with each company presented in Table 2 were thoroughly read and each identified benefit was assigned a unique identifier. Each theme is identified by the acronym "BF" and a number is associated to differentiate each benefit. Common themes have the same acronym. A brief description of how each benefit is understood in the case studies is also included. Table 3 presents the identification process of the themes associated with each case study. Table 3 shows the themes for all the case studies mentioned in Table 2. We highlight the existence of themes that are common to several case studies. Although the themes are common, the vision of each case study in relation to them has some relevant oscillations, which indicate a complementary vision of the institutions present in the case studies. For example, in CS1 time to market emerges due to increased collaboration between teams, whereas in CS8 process integration is highlighted. Something similar emerges in relation to cost. Cost reduction is understood in CS6 as achieved from the existence of multi-skilled human resources, whereas in CS8 cost reduction is motivated by the effects of increased team performance. Table 3. Identified benefits themes in the case studies.

CS1
(BF1) Time to market: greater collaboration between teams reduces software delivery cycles (BF2) Automation: the combined development and production process becomes more automated to meet market needs CS2 (BF2) Automation: continuous delivery and integration combined with fast releases lead to the automation of activities

Results
The twelve case study reports associated with each company presented in Table 2 were thoroughly read and each identified benefit was assigned a unique identifier. Each theme is identified by the acronym "BF" and a number is associated to differentiate each benefit. Common themes have the same acronym. A brief description of how each benefit is understood in the case studies is also included. Table 3 presents the identification process of the themes associated with each case study. Table 3 shows the themes for all the case studies mentioned in Table 2. We highlight the existence of themes that are common to several case studies. Although the themes are common, the vision of each case study in relation to them has some relevant oscillations, which indicate a complementary vision of the institutions present in the case studies. For example, in CS1 time to market emerges due to increased collaboration between teams, whereas in CS8 process integration is highlighted. Something similar emerges in relation to cost. Cost reduction is understood in CS6 as achieved from the existence of multi-skilled human resources, whereas in CS8 cost reduction is motivated by the effects of increased team performance. Table 3. Identified benefits themes in the case studies.

CS1
(BF1) Time to market: greater collaboration between teams reduces software delivery cycles (BF2) Automation: the combined development and production process becomes more automated to meet market needs

CS6
(BF1) Time to market: deployment chains cut the time needed to get a product to market (BF9). Cost: combining people and activities makes people more multi-skilled with future reduction in human resource costs  Table 4 summarizes the comparative analysis of the identified benefits. All previously identified benefits are mapped. The "ranking" attribute allows us to understand the relative importance of the benefits and to perceive which ones are transversal to several case studies and which ones emerge only in a very specific context of each organization. The benefits related to automation (BF2), communication (BF3), and time to market (BF1) stand out. These are the three main benefits that can be found in the combined adoption of Agile and DevOps. Conversely, there are other benefits that are identified in a smaller number of case studies, namely, those related to efficiency (BF11), risk mitigation (BF7), and software quality (BF8). These benefits are less relevant and arise in the specific context of each organization, which indicates that they are more difficult to replicate in other software companies. Table 4. Comparative analysis of benefits and ranking.

Discussion
Although Agile and DevOps are widespread and different concepts, they can be combined and offer relevant benefits to organizations. As reported in [45], companies have problems in the process of implementing and releasing new software versions because most of the time this is a process performed manually. In addition, this approach leads to a high quantity and frequency of errors [46]. To reduce the incidence of problems and increase flexibility and automation, non-operational resources can be used and in environments that are not in production. The combined adoption of Agile and DevOps allows the developer to gain greater control over the environment, infrastructure, and applications.
The seamless integration between Agile and DevOps generates a more collaborative and Agile framework. This approach leads to a simplification and automation of model processes to make them more rational and efficient. A classic example of this benefit is given by Fabro [47] when highlighting the reduction in delivery cycles, endowing small development packages with a previously unrecognized value. Hemon-Hildgen et al. [48] also highlight the role of orchestration, which consists of automating tasks to optimize the process and reduce repetitive steps that add little to the development cycle. Finally, automated testing along the Agile and DevOps chain allows the reuse of tests between environments and makes them more sustainable [49].
Team communication is recognized in DeFranco and Laplante [50] and Schmutz et al. [51] as the main cause for product delivery failures. By starting to work together, teams can more easily track the evolution of processes from their inception, which fosters the emergence of process improvements. Cois et al. [52] recognize that the great differentiator of DevOps lies in its ability to optimize communication between the teams involved and the customer. This allows, for example, the team to involve the operations team, which enables the implementation of the ITOps model [53]. This enables it to provide a sufficiently secure development environment. However, interconnecting it with an organization's Agile teams offers more potential. For example, the marketing and sales departments can be involved in the activities covering the delivery of the releases, which allows companies to add even more value to the product by using the full potential of their available resources.
The findings further revealed a very diverse number of benefits, such as increased visibility over processes, better identification and mitigation of risks, or increased software quality. The integration of the two paradigms fosters consolidation, which allows project managers to have greater visibility of both the work of the teams and the interdependencies between them [54]. Furthermore, iterative planning between teams makes it easier to adapt in case of changes, and continuous customer feedback generates value from the beginning of the project, lowering the risks associated with development and operation [55]. In the joint Agile and DevOps paradigm, both teams share responsibility for producing functional and quality code and need to work together to achieve these common goals.
Finally, it is recognized that in recent years there has been a growing adoption of the term "DevOps culture", as a counter position to DevOps implementations based only on tools. In DevOps culture, it is advocated that software development and infrastructure teams work together towards the same goal [56,57]. As Clavier and Kaminski [58] argue, DevOps not only optimizes development processes but changes the way employees think about their products and interact with customers. The combined Agile and DevOps approach allows the leveraging of these benefits by enhancing empathy among team members and unites sectors that previously worked independently and without personal connection. Furthermore, as Venugopal [59] acknowledges, when there is trust between teams, then it also increases the freedom that professionals have to experiment and innovate, without the problems of incompatibility and miscommunication as there would be with separate teams.

Conclusions
This study demonstrates that the Agile and DevOps paradigms are not incompatible but can bring benefits to organizations when properly aligned. While Agile brought about a fast delivery model aligned with customer expectations, DevOps optimized this system. In this sense, an alternative that usually gives great results is the adoption of both methodologies. They not only complement each other but also help companies to face changes in a team.
Changing the strategy and methodology of a team can be a delicate process full of obstacles. Therefore, organizations must address this challenge in a cross-cutting way within the organization to avoid isolated silos that do not contribute to collaborative work. Agile creates a space for more agile work with partial deliveries, while DevOps creates an environment conducive to managing these processes, with effective communication.
This study offers both theoretical and practical relevant contributions. In the theoretical dimension, this study has enabled the identification of a set of benefits of the combined adoption of both paradigms through the adoption of multiple case studies of software companies in the international market. The study identifies a total of 12 benefits and allows us to explore the relative relevance of each of them. From a practical perspective, the benefits identified are relevant to companies that, having adopted Agile and DevOps alone, have not yet taken steps towards the combined adoption of both models. The findings of the study made it evident that the two models are not incompatible, but when combined they can amplify their impacts on organizations.

Limitations and Future Research Directions
This study presents some limitations. Firstly, the case studies included in this study come from secondary sources, which does not allow us to deepen the knowledge on the themes with the use of interviews that may evidence the application of both paradigms. Furthermore, the case studies come from companies with commercial purposes, which may not give a totally unbiased view of the benefits to the organizations or represent very specific groups of the population. Nevertheless, this study adopted external and internal validation mechanisms to reduce this risk of bias. As future work it is recommended that the business view be complemented with a scientific view of the benefits of combining DevOps and Agile and, to this end, a systematic review of the literature in the field can be conducted. Moreover, the qualitative approach used does not allow us to systematically identify all the advantages and make a rigorous quantification of these benefits. As future work, a quantitative study based on a large dataset is suggested to identify the advantages of the combined adoption of both paradigms considering also different sectors of activity of the organizations. It would also be relevant to consider the degree of maturity in the implementation of Agile and DevOps in these organizations and, thus, explore its relevance in the benefits found, since it is expected that some of the benefits may be more easily achieved by organizations with lower levels of maturity in these processes.