Academic literature on the topic 'DevOps adoption'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'DevOps adoption.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "DevOps adoption"

1

Salih, Ahmad Mahdi, Sharifah Mashita Syed-Mohamad, Pantea Keikhosrokiani, and Nur Hana Samsudin. "Adopting DevOps practices: an enhanced unified theory of acceptance and use of technology framework." International Journal of Electrical and Computer Engineering (IJECE) 13, no. 6 (2023): 6701. http://dx.doi.org/10.11591/ijece.v13i6.pp6701-6717.

Full text
Abstract:
<div align="center"><span lang="EN-US">DevOps software development approach is widely used in the software engineering discipline. DevOps eliminates the development and operations department barriers. The paper aims to develop a conceptual model for adopting DevOps practices in software development organizations by extending the unified theory of acceptance and use of technology (UTAUT). The research also aims to determine the influencing factors of DevOps practices’ acceptance and adoption in software organizations, determine gaps in the software development literature, and introduce a clear picture of current technology acceptance and adoption research in the software industry. A comprehensive literature review clarifies how users accept and adopt new technologies and what leads to adopting DevOps practices in the software industry as the starting point for developing a conceptual framework for adopting DevOps in software organizations. The literature results have formulated the conceptual framework for adopting DevOps practices. The resulting model is expected to improve understanding of software organizations’ acceptance and adoption of DevOps practices. The research hypotheses must be tested to validate the model. Future work will include surveys and expert interviews for model enhancement and validation. This research fulfills the necessity to study how software organizations accept and adopt DevOps practices by enhancing UTAUT.</span></div>
APA, Harvard, Vancouver, ISO, and other styles
2

Ahmad, Mahdi Salih, Mashita Syed-Mohamad Sharifah, Keikhosrokiani Pantea, and Hana Samsudin Nur. "Adopting DevOps practices: an enhanced unified theory of acceptance and use of technology framework." International Journal of Electrical and Computer Engineering (IJECE) 13 (December 1, 2023): 6701–17. https://doi.org/10.11591/ijece.v13i6.pp6701-6717.

Full text
Abstract:
DevOps software development approach is widely used in the software engineering discipline. DevOps eliminates the development and operations department barriers. The paper aims to develop a conceptual model for adopting DevOps practices in software development organizations by extending the unified theory of acceptance and use of technology (UTAUT). The research also aims to determine the influencing factors of DevOps practices’ acceptance and adoption in software organizations, determine gaps in the software development literature, and introduce a clear picture of current technology acceptance and adoption research in the software industry. A comprehensive literature review clarifies how users accept and adopt new technologies and what leads to adopting DevOps practices in the software industry as the starting point for developing a conceptual framework for adopting DevOps in software organizations. The literature results have formulated the conceptual framework for adopting DevOps practices. The resulting model is expected to improve understanding of software organizations’ acceptance and adoption of DevOps practices. The research hypotheses must be tested to validate the model. Future work will include surveys and expert interviews for model enhancement and validation. This research fulfills the necessity to study how software organizations accept and adopt DevOps practices by enhancing UTAUT.
APA, Harvard, Vancouver, ISO, and other styles
3

Guerrero, Jonathan, Karen Zúñiga, Camilo Certuche, and César Pardo. "A systematic mapping study about DevOps." Journal de Ciencia e Ingeniería 12, no. 1 (2020): 48–62. http://dx.doi.org/10.46571/jci.2020.1.5.

Full text
Abstract:
DevOps is a very trendy term these days in the software development companies (SDC), term that emerges as a possible solution to finally reach an acceleration and a rise of productivity expected with the appearance of agile development approaches, but that until now had not materialized, through automation practices, continuous integration, continuous build, and continuous deployment. This paper aims to show current knowledge about the process of adopting DevOps in SDC through a systematic mapping of the literature. However, the results obtained show that there is little detailed information regarding activities, tasks, roles, and other important process elements for the adoption of DevOps. Similarly, it has been concluded that there is no a unified terminology, therefore, it is important to standardize it to simplify the understanding and application of DevOps. Furthermore, this paper shows the preview of the framework that it is being developed for the adoption of DevOps in the SDC.
APA, Harvard, Vancouver, ISO, and other styles
4

Akinola, Omolola, Omowunmi Oyerinde, and Akintunde Akinola. "Implementing DevOps Adoption within United States SMEs." Journal of Artificial Intelligence General science (JAIGS) ISSN:3006-4023 3, no. 1 (2024): 47–50. http://dx.doi.org/10.60087/jaigs.vol03.issue01.p50.

Full text
Abstract:
DevOps is an integration of "Development" (Dev) and "Operations" (Ops) and has emerged as a transformational way of software development, with the objective of enabling rapid and efficient delivery of software. While accepted at larger scales in enterprises, there has been hardly any literature review based on the implementation of DevOps in Small and Medium Enterprises (SMEs) in the United States. This research, therefore, seeks to analyze in detail the challenges, methodologies, and outcomes of implementing DevOps adoption within SMEs in the United States. This research investigates the strategies, benefits, and barriers of SMEs toward the implementation of DevOps using mixed-methods research, including qualitative data from a case study and both interview and quantitative survey data. The results offer a contribution to an understanding of how SMEs adopt DevOps and present valuable knowledge for both practitioners and researchers.
APA, Harvard, Vancouver, ISO, and other styles
5

Akinola, Omolola, Omowunmi Oyerinde, and Akintunde Akinola. "Implementing DevOps Adoption within United States SMEs." Journal of Artificial Intelligence General science (JAIGS) ISSN:3006-4023 2, no. 1 (2024): 217–19. http://dx.doi.org/10.60087/jaigs.v2i1.115.

Full text
Abstract:
DevOps is an integration of "Development" (Dev) and "Operations" (Ops) and has emerged as a transformational way of software development, with the objective of enabling rapid and efficient delivery of software. While accepted at larger scales in enterprises, there has been hardly any literature review based on the implementation of DevOps in Small and Medium Enterprises (SMEs) in the United States. This research, therefore, seeks to analyze in detail the challenges, methodologies, and outcomes of implementing DevOps adoption within SMEs in the United States. This research investigates the strategies, benefits, and barriers of SMEs toward the implementation of DevOps using mixed-methods research, including qualitative data from a case study and both interview and quantitative survey data. The results offer a contribution to an understanding of how SMEs adopt DevOps and present valuable knowledge for both practitioners and researchers.
APA, Harvard, Vancouver, ISO, and other styles
6

Qumer Gill, Asif, Abhishek Loumish, Isha Riyat, and Sungyoup Han. "DevOps for information management systems." VINE Journal of Information and Knowledge Management Systems 48, no. 1 (2018): 122–39. http://dx.doi.org/10.1108/vjikms-02-2017-0007.

Full text
Abstract:
Purpose Development and operations (DevOps) is complex in nature. Organizations are unsure how to effectively establish a DevOps capability for the continuous delivery of information management systems. This paper aims to compile and analyze DevOps by applying the well-known systematic literature review (SLR) approach. This review is intended to provide a knowledge base to support the informed, effective and less risky adoption of DevOps for information management systems. Design/methodology/approach In this qualitative research study, the SLR method was applied to identify 3,790 papers, of which, 32 relevant papers were selected and reviewed. Findings The results are organized using the well-known ISO/IEC 24744 metamodel elements: people (roles), process, technology and artifacts. In total 11 major roles, 6 processes, 23 technologies, 5 artifacts and 7 challenges (including 6 corresponding solutions) were found. DevOps engineer is becoming a newly identified role. Continuous delivery pipeline and continuous improvement are the most highlighted major DevOps processes. Build system technology is becoming the key focus of DevOps. Finally, major challenges are around people and culture and the misunderstanding of DevOps. Potential research areas are: DevOps analytics, artifacts and tool–chain integration. Research limitations/implications The research findings will serve as a resource for both practitioners and researchers who have interest in the research and adoption of DevOps for information management systems. Originality/value This paper provides a comprehensive systematic review of the body of knowledge to support the ongoing research and adoption of emerging trends of DevOps for information management systems.
APA, Harvard, Vancouver, ISO, and other styles
7

Jayakody, J. A. V. M. K., and W. M. J. I. Wijayanayake. "Critical success factors for DevOps adoption in information systems development." International Journal of Information Systems and Project Management 11, no. 3 (2023): 60–82. http://dx.doi.org/10.12821/ijispm110304.

Full text
Abstract:
Adopting DevOps is challenging since it makes a significant paradigm shift in the Information Systems Development process. DevOps is a trending approach attached to the Agile Software Development Methodology, which facilitates adaptation to the customers' rapidly-changing requirements. It keeps one front step by introducing software operators who support the transmission between software and implementation into the software development team by confirming faster development, quality assurance, and easy maintenance of Information Systems (IS). However, software development companies reported challenges in adopting DevOps. It is critical to control those challenges while getting hold of the benefits by studying Critical Success Factors (CSF) for adopting DevOps. This study aimed to analyze the use of DevOps approach in IS developments by exploring CSFs of DevOps. A systematic literature review was applied to identify CSFs. These factors were confirmed by interviewing DevOps practitioners while identifying more frequent CSFs in the software development industry. Finally, the research presents a conceptual model for CSFs of DevOps, which is a guide to reap the DevOps benefits while reducing the hurdles for enhancing the success of IS. The conceptual model presents CSFs of DevOps by grouping them into four areas: collaborative culture, DevOps practices, proficient DevOps team, and metrics & measurement.
APA, Harvard, Vancouver, ISO, and other styles
8

J., A. V. M. K. Jayakody, and M. J. I. Wijayanayake W. "Devops Adoption in Information Systems Projects; A Systematic Literature Review." International Journal of Software Engineering & Applications (IJSEA) 13, no. 3 (2022): 39–53. https://doi.org/10.5281/zenodo.6837212.

Full text
Abstract:
The word DevOps derives from two different words Development and Operations. DevOps has recorded as an interesting and novel approach adopted to the commonly used Agile software development methodology. It raised agility of the software development process. Practical issues of Agile methodology emphasize the requirement for collaboration of software development and operating teams. This collaboration completed by the DevOps approach engages with the Agile methodology to improve the quality, performance, and speed of the software developments. Since DevOps is an accentuating approach in the software development industry, this research aimed to conduct a literature review to study the evolution of the DevOps approach and its adoption in information systems projects. This target has accomplished by reviewing the Agile methodology, issues of the Agile methodology, DevOps approach, challenges and overcoming strategies of DevOps, and success factors of the DevOps approach. Finally, the paper provides better acquaintance about the DevOps adoption in Information System projects developments.
APA, Harvard, Vancouver, ISO, and other styles
9

Craciun, Pavel-Cristian, and Robert-Cristian Necula. "Why Startups Outpace Multinationals in Leveraging DevOps." Proceedings of the International Conference on Business Excellence 18, no. 1 (2024): 3421–29. http://dx.doi.org/10.2478/picbe-2024-0277.

Full text
Abstract:
Abstract This paper explores the differential impacts of DevOps across varying organizational structures, specifically analyzing why startups may outpace multinational companies in leveraging the benefits of DevOps methodologies. DevOps drives organizational efficiency and innovation. Comparative studies often examine its implementation in startups versus large-scale enterprises. The literature pinpoints the agility, culture, and size of an organization as key determinants influencing the adoption of DevOps principles. In response, this study employs an extensive questionnaire distributed to DevOps and related professionals to investigate the hypothesis that startups are uniquely positioned to harness DevOps for technological advancement and cultural synergy. The survey gathered quantitative and qualitative data reflecting experiences with DevOps adoption, challenges faced, and the perceived benefits drawn from such practices. The findings reveal that while startups and multinationals share common challenges, the former's organizational agility, innovative mindset, and less encumbered cultural practices offer startups a distinct advantage in the effective assimilation of DevOps practices. This paper contributes to the field by providing evidence supporting the notion that startups possess intrinsic advantages over multinationals in DevOps implementation, chiefly due to their flexibility and lean structures for rapid innovation. By mapping out the relative successes and impediments to DevOps adoption in diverse corporate environments, this research extends the understanding of how organizational characteristics can be leveraged to optimize DevOps strategies in the evolving landscape of software engineering.
APA, Harvard, Vancouver, ISO, and other styles
10

P P, Joby. "EXPLORING DEVOPS: CHALLENGES AND BENEFITS." Journal of Information Technology and Digital World 01, no. 01 (2019): 27–37. http://dx.doi.org/10.36548/jitdw.2019.1.004.

Full text
Abstract:
The continuous evolving of the information technology towards the enhanced agile and collective strides of working from the document driven working has turned the focus to the features of the information system development and the operations. These agile approaches have paved way for the concepts that provide an incorporated development and operations coined as the DevOps. The DevOps is an enterprise software development and viewed as the appropriate perception for the simultaneous distribution and the positioning of the working software. It enhances and modifies the relationship by promoting improved communication and the cooperation among the business unit. However the adoption of the Development and the Operation being a complex task the paper presents the review on the challenges and the benefits of the DevOps and also explores the DevOps to offer an enhancement in the adoption of the DevOps in the information systems.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "DevOps adoption"

1

Burrell, Iris Shendell. "Examining the Effect of DevOps Adoption capability on organizational agility." Diss., Temple University Libraries, 2018. http://cdm16002.contentdm.oclc.org/cdm/ref/collection/p245801coll10/id/506178.

Full text
Abstract:
Business Administration/Management Information Systems<br>D.B.A.<br>The purpose of this research is to investigate the effect of DevOps adoption on organizational agility. The first chapter establishes through literature review and a pilot study, a theoretical definition of DevOps and identifies through survey data, the key DevOps adoption capabilities. The definition and key capabilities identified during the pilot study establishes the foundation through which a subsequent study is performed. The second chapter details an examination of the effects of DevOps adoption capability on organizational agility. Through capability theory, we propose that DevOps adoption capability positively affects organizational agility. We also propose that the capabilities of collaboration/communication, continuous monitoring, measurement and automation positively affect DevOps adoption capability and likewise; the capabilities of responsiveness, competency, flexibility, and quickness affect organizational agility capability. We test our model with survey data collected from 333 respondents and find that our hypotheses are supported and that DevOps adoption capability has a positive effect on organizational agility capability.<br>Temple University--Theses
APA, Harvard, Vancouver, ISO, and other styles
2

Anderson, Andrew John. "Examination of Adoption Theory on the DevOps Practice of Continuous Delivery." ScholarWorks, 2019. https://scholarworks.waldenu.edu/dissertations/7457.

Full text
Abstract:
Many organizations have difficulty adopting advanced software development practices. Some software development project managers in large organizations are not aligned with the relationship between performance expectancy, effort expectancy, social influence, and facilitating conditions, as moderated by experience, with intent to adopt the DevOps practice of continuous delivery. The purpose of this study was to examine the statistical relationships between the independent variables—performance expectancy, effort expectancy, social influence, and facilitating conditions, as moderated by experience—and the dependent variable of behavioral intent to adopt a continuous delivery system. Venkatesh, Morris, Davis, and Davis's unified theory of acceptance and use of technology provided the theoretical framework. A stepwise multiple linear regression analysis was performed on survey data from 85 technical project managers affiliated with LinkedIn project management groups. The analysis reflected that only performance expectancy was significant in predicting intent to adopt continuous delivery. The findings may contribute to social change by providing project managers with the information they need to support organizational change, collaboration, and facilitation. The knowledge gained may additionally help organizations develop operational efficiency, competitive advantage, and generate higher value to their clients and society.
APA, Harvard, Vancouver, ISO, and other styles
3

Lwakatare, L. E. (Lucy Ellen). "DevOps adoption and implementation in software development practice:concept, practices, benefits and challenges." Doctoral thesis, Oulun yliopisto, 2017. http://urn.fi/urn:isbn:9789526217116.

Full text
Abstract:
Abstract In the last decade, the software industry has been marked by a growing trend of software companies’ ability to deploy new software features fast and frequently in short release cycle times. The companies’ software release cycles have been shortened to hours and minutes rather than months. To enable the transformation towards short release cycle times, companies have adopted several different strategies, including the DevOps approach. DevOps in the software industry emerged to represent a professional movement emphasising the collaboration between software development and operations. In practice, DevOps affects the company culture, processes, products, associated technologies and organisational structures used in software development and operations processes. The multifaceted nature of DevOps makes the concept ambiguous and difficult for software companies to adopt as there are many different paths to its adoption. The purpose of the thesis is to provide detailed description of the adoption and implementation of DevOps in software development comprehending the DevOps concept definition, and its practices, benefits and challenges. The research was performed by systematically reviewing the literature, multi-vocal documents and making qualitative inquiries among software practitioners; and based on that the consolidated body of knowledge of DevOps was constructed. The key finding of the research is that the DevOps approach includes an automated software deployment mechanism focusing on the rapid and repeatable release of software changes and automated management of operational infrastructure. The adoption and implementation of DevOps practices are prominent in software companies that use cloud computing technology, while its adoption is challenging in the embedded system domain. DevOps is not a silver bullet; challenges pertaining to the management of infrastructures due to legacy technologies still persist. The key lesson learned in the adoption and implementation of DevOps is that the software operational infrastructure is no longer considered separate from the development of software features; and this is achieved by having software development and operations teams jointly working together<br>Tiivistelmä Viimeisen vuosikymmenen aikana ohjelmistoteollisuudessa on ollut kasvavana trendinä ohjelmistotalojen lisääntyvä kyky toimittaa ohjelmistomuutoksia nopeasti ja usein toistuvina päivityksinä. Yritysten ohjelmistotoimitus- ja päivitysjaksot ovat lyhentyneet kuukausista tunneiksi ja jopa minuuteiksi. Yritykset ovat ottaneet käyttöön useita erilaisia toimintatapoja kyetäkseen muuttamaan toimintaansa lyhyen aikavälin ohjelmistopäivityksiin kykeneväksi, joista yksi viimeisimmistä on DevOps (saumaton ohjelmiston kehittäminen ja käyttö). Ohjelmistotuotannossa DevOps syntyi ohjelmistoteollisuudessa ammattilaisten alkaessa painottaa ohjelmistojen kehittämisen ja käytön yhteistyön tärkeyttä. Käytännössä DevOpsilla on vaikutusta ohjelmisto-organisaation toimintakulttuuriin, prosesseihin, tuotteisiin, sekä teknologioihin ja organisaatiorakenteisiin, joita käytetään ohjelmistokehityksessä ja käyttöönottoprosessissa. DevOpsin käsitteen moniulotteisuudesta johtuen käsitteen sisältö jää usein epäselväksi ja samalla sen mukainen toiminta vaikeasti käyttöön otettavaksi ohjelmistoyrityksissä, koska toteutus on mahdollista tehdä monella eri tavalla. Tämän väitöksen tarkoituksena on antaa selkeä kuvaus DevOpsista ja sen toteutuksesta ohjelmistokehityksessä niin, että sen käsite, ja käytännöt, sekä sen tarjoamat edut ja haasteet tulevat ymmärretyiksi. Tutkimuksessa suoritettiin systemaattinen kirjallisuuskatsaus tieteellisiin julkaisuihin ja muihin lähinnä käytännön kokemuksiin pohjautuviin lähteisiin, suoritettiin kvalitatiiviset kyselytutkimukset, joiden kohteena olivat ohjelmistoammattilaiset, sekä muodostettiin näiden pohjalta saumattoman ohjelmistokehityksen ja käytön yhtenäinen tietämyskanta. Tutkimuksen keskeinen tulos on, että DevOps-lähestymistapa sisältää automaattisen ohjelmiston käyttöönottomekanismin, joka keskittyy nopeiden ja toistettavien ohjelmistomuutosten käyttöönottoon ja sitä tukevan operatiivisen infrastruktuurin hallintaan. DevOpsin omaksuminen ja käyttöönotto ovat näkyvästi esillä pilvipalvelinteknologiaa käyttävissä ohjelmistoyrityksissä, kun taas sen käyttöönotto on haastavaa sulautettujen järjestelmien alueella. DevOps ei ole mikään ’hopealuoti’, vaan sisältää erityisesti infrastruktuurien hallintaan liittyviä haasteita, jotka johtuvat edelleen käytössä olevista vanhoista tekniikoista. Keskeisin oppima DevOpsin omaksumisesta ja soveltamisesta käytäntöön on, että ohjelmistojen käyttöinfrastruktuuria ei enää tarkastella erillään ohjelmistojen kehittämisestä, vaan ne toimivat saumattomassa yhteistyössä keskenään
APA, Harvard, Vancouver, ISO, and other styles
4

Enoch, John. "Application of Decision Analytic Methods to Cloud Adoption Decisions." Thesis, Högskolan i Gävle, Avdelningen för Industriell utveckling, IT och Samhällsbyggnad, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:hig:diva-25560.

Full text
Abstract:
This thesis gives an example of how decision analytic methods can be applied to choices in the adoption of cloud computing. The lifecycle of IT systems from planning to retirement is rapidly changing. Making a technology decision that can be justified and explained in terms of outcomes and benefits can be increasingly challenging without a systematic approach underlying the decision making process. It is proposed that better, more informed cloud adoption decisions would be taken if organisations used a structured approach to frame the problem to be solved and then applied trade-offs using an additive utility model. The trade-offs that can be made in the context of cloud adoption decisions are typically complex and rarely intuitively obvious. A structured approach is beneficial in that it enables decision makers to define and seek outcomes that deliver optimum benefits, aligned with their risk profile. The case study demonstrated that proven decision tools are helpful to decision makers faced with a complex cloud adoption decision but are likely to be more suited to the more intractable decision situations.
APA, Harvard, Vancouver, ISO, and other styles
5

Oachesu, Alex, and Nemanja Negovanovic. "The core problems of globally distributed work in software development environments, and possible solutions : DevOps environments' opportunities for better adoption of a globally distributed working culture." Thesis, Högskolan Kristianstad, Fakulteten för naturvetenskap, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hkr:diva-21956.

Full text
Abstract:
Both distributed work and DevOps are on an upward trend. There is a slight resemblance between the problems that DevOps is trying to find answers to, the solutions, and the common problems that geographically distributed work faces. Mainly, they are related to isolated environments that have difficulties in mutual understanding and communication, collaboration. All this leads to inefficiencies and costs that affect the overall efficiency of companies. This report identifies how DevOps engineering principles and implementations provide solutions to common problems in globally distributed work environments. It uses a literature systematic literature search and review to extract the recent and relevant academic data in the scope of the two research questions. Then, a proof-of-concept is implemented for DevOps, which confirms the literature. In parallel, a survey addressed to Swedish companies provides subject-related data from the professional environment, which largely supports the literature and brings extra knowledge. All of this is considered in data analysis and formulation of conclusions, showing DevOps features that can improve and support work in globally distributed environments and outlining the importance of the tailored organizational culture for the modern need of large-scale distributed work.
APA, Harvard, Vancouver, ISO, and other styles
6

Lindström, Gustav. "The Challenges of adopting DevOps." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-264179.

Full text
Abstract:
In traditional Software Development Life Cycle, medium and large organizations tend to divide the activities of Operations and Development into separate departments. These groups often have a troublesome relationship because of different incentives during the software delivery process. As a result, conflicts occur between development and operations personnel as they blame each other to be the cause of long lead times and inefficient software delivery processes. The concept of DevOps emerged trying to resolve the problem that arises when separating the work of Development and Operations into organizational silos. The term DevOps is a combination of the abbreviations of Development (Dev) and Operations (Ops). DevOps aim to create a coalition that spans between Development (software developers and quality assurance) and Operation (experts responsible to roll out software to production and managing the infrastructure, e.g. system, network and database administrators and technicians). The idea is to increase the speed of the software delivery process and to quickly solve critical issues, enable organizations to better serve their customers. DevOps means that development teams who previously were solely responsible for the development of their applications now have to manage and govern both development and operational responsibilities. Thus, the adoption of DevOps might introduce new type of challenges and implications for the traditional development teams. Current literature and research about DevOps focus mainly on the challenges that DevOps attempts to overcome. There is a lack of literature on the challenges that practitioners encounter during the adoption of DevOps. As more organizations and companies tend to adopt the concept of DevOps, it increases the need to understand potential challenges and effects of adopting DevOps. Therefore, the aim of this study is to investigate the challenges that development teams encounter during the adoption of DevOps. This research was conducted by an inductive research approach through a single qualitative case study, with the use of semi-structured interviews. In total, four main challenges and fourteen sub-challenges were identified in this study. The four main challenges identified was, lack of awareness, lack of support for DevOps, implementing DevOps technology and adapting organizational processes to DevOps. This study concludes that the adoption of DevOps has a profound impact on the role of a software developer, and that the traditional role of a software developer needs to be evolved. The research provides four recommendations and means to overcome the challenges identified in this research, establishing common ways of working and spreading the knowledge, building commitment and trust by smarter seating, allocate time and resources to transition and trying out with one team and one application.<br>I traditionell livscykel för mjukvaruutveckling tenderar medelstora och stora organisationer att dela upp verksamheten i drift och utveckling i separata avdelningar. Dessa grupper har ofta en besvärlig relation på grund av olika incitament under mjukvaruleveransprocessen. Som ett resultat uppstår konflikter mellan utvecklings- och driftpersonal eftersom de beskyller varandra för att vara orsaken till långa ledtider och ineffektiva mjukvaruleveransprocesser. Konceptet DevOps uppstod för att försöka lösa det problem som uppstår när man separerar utveckling och drift i organisationella silosar. Termen DevOps är en kombination av förkortningarna för utveckling (Dev) och drift (Ops). DevOps syftar till att skapa en koalition som sträcker sig mellan utveckling (mjukvaruutvecklare och kvalitetssäkring) och drift (system-, nätverks- och databasadministratörer och tekniker). Idén är att öka hastigheten av mjukvaruleveranser och att snabbt lösa kritiska problem för att förbättra organisationens förmåga att betjäna sina kunder. DevOps innebär att utvecklingsgrupper som tidigare enbart ansvarade för utvecklingen av sina applikationer nu även har driftansvar. Således kan antagandet av DevOps introducera nya typer av utmaningar och konsekvenser för de traditionella utvecklingsgrupperna. Aktuell litteratur och forskning kring DevOps fokuserar främst på de utmaningar som DevOps försöker övervinna. Därav finns det brist på litteratur kring de utmaningar som utövare stöter på under antagandet av DevOps. Eftersom fler organisationer och företag tenderar att adoptera begreppet DevOps ökar behovet av att förstå potentiella utmaningar och effekter av att anta DevOps. Därav är syftet med denna studie att undersöka de utmaningar som utvecklingsgrupper bemöter under antagandet av DevOps. Denna forskning utfördes genom en induktiv forskningsinriktning, en kvalitativ fallstudie och datainsamling genom halvstrukturerade intervjuer. Totalt identifierades fyra huvudutmaningar och fjorton sub utmaningar i denna studie. De fyra huvudsakliga utmaningar som identifierades var, brist på medvetenhet, brist på stöd för DevOps, implementering av DevOps-teknik och anpassning av organisationsprocesser till DevOps. Den här studien drar slutsatsen att antagandet av DevOps har en djupgående inverkan på rollen som en mjukvaruutvecklare och att den traditionella rollen som en mjukvaruutvecklare behöver utvecklas. Studien ger fyra rekommendationer och medel för att övervinna de utmaningar som identifierats, etablering av gemensamma sätt att arbeta och sprida kunskapen, bygga upp engagemang och förtroende genom smartare sittplatser, fördela tid och resurser till övergången samt prova med ett lag och en applikation.
APA, Harvard, Vancouver, ISO, and other styles
7

Wang, Cheng, and Changling Liu. "Adopting DevOps in Agile: Challenges and Solutions." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16651.

Full text
Abstract:
Background. DevOps is a hot topic in recent years. It emphasizes the combination of development and operation. Agile is one of the most popular development methods, but Agile mainly focused on software development part, there is no more involvement in deployment and operations. In this case, many companies consider adopting DevOps in Agile to attempt to improve the situation. Objectives. The combination of two different technologies is bound to produce some challenges, whether it is for practitioners or researchers, it is very important to find these challenges and mitigate them, so this article aims to investigate the challenges of adopting DevOps in Agile, then through the systematic literature review and survey questionnaire to determine the corresponding mitigation strategy. Then, in order to detail understand the process of adopting DevOps in Agile, we use interview to research the real process of adopting DevOps in agile. Methods. According to our research question, we used the systematic literature review(SLR), survey questionnaire and interview as our research methodology. Through literature review, we collected data of adopting DevOps in Agile, and summary the challenges and its relevant mitigation strategies. Then survey questionnaire helped us linking the content of literature to the industry, and compare their difference. Through the interview, we explored the actual process of adopting DevOps in Agile in industry, and correspond the challenges to the actual process. Results. Our study summarized the software development process of adopting DevOps based on Agile and revealed 23 challenges and corresponding mitigation strategies. The report also compares the commonalities and gaps between the results from the literature and the findings of real-life adopting of DevOps challenges and mitigation strategies. Conclusions. In this article, we introduced the challenges and corresponding mitigation strategies for adopting DevOps based on agile and summarize the corresponding software development process. The obvious challenges and mitigation strategies were divided into four categories: 1) People 2) Project 3) Process 4) Organization, after which we conducted further discussions based on the actual conditions and compared the results of systematic literature review and the results of questionnaire to detail explore their difference.
APA, Harvard, Vancouver, ISO, and other styles
8

Silva, Miguel Ângelo Rodrigues da. "Productivity gains of DevOps adoption: a case study." Master's thesis, 2018. http://hdl.handle.net/10071/18293.

Full text
Abstract:
The main purpose of this research is to assess the productivity gains from the merge of two traditional IT teams: Development and Operations into a single DevOps team implementing 6 DevOps capabilities This research was conducted using the Case Study methodology, the author goes through the existing DevOps literature to better frame this research and the reader. To answer the formulated research question the author analyzed the team capacity planning divided by tasks type before and after a DevOps transition and interviewed 5 senior team members to collect their opinion about this transition. Observation was also part of this research and it was done by the author. The main objective is to analyze if there were productivity gains of that team after making the transition to a DevOps approach. The main contribution of this research is to analyze and extract results of the application of the DevOps capabilities in a real-world scenario where two teams are merged into a single DevOps team. As an example, we can observe that the operational work of the team decrease from 50% to 20%<br>O objectivo principal desta pesquisa é aferir os ganhos de produtividade ao efetuar a fusão de duas equipas tradicionais de IT: Desenvolvimento e Operações numa única equipa DevOps implementando as 6 capacidades de DevOps. Esta pesquisa foi efetuada utilizado o método Caso de Estudo, o autor efetua uma revisão da literatura para melhor enquadrar esta pesquisa e o leitor. Para responder a pergunta enunciada nesta pesquisa o autor analisou o planeamento da capacidade da equipa dividido por tipo de tarefas antes e depois da fusão para DevOps, foram também efetuadas 5 entrevistas a membros seniores da equipa para recolher a sua opinião acerca desta transiçao para um modelo DevOps. E foi efetuada também a observação no terreno pelo autor do estudo. A maior contribuição desta pesquisa reside na extração dos resultados da aplicação das capacidades de DevOps num cenário real onde duas equipas foram fundidas numa só equipa DevOps. Como exemplo podemos observar a diminuição das tarefas operacionais das equipas decresceram de 50% para 20%.
APA, Harvard, Vancouver, ISO, and other styles
9

Yu, Liang, and Clemente Guerra. "Exploring the disruptive power of adopting DevOps for software development." Thesis, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-18378.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "DevOps adoption"

1

Sharma, Sanjeev. The DevOps Adoption Playbook. John Wiley & Sons, Inc., 2017. http://dx.doi.org/10.1002/9781119310778.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Biguenet-Maurel, Cécile. Le devoir de conseil des notaires. Defrénois, 2006.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Devops: This Book Includes Devops Handbook and Devops Adoption. Independently Published, 2018.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Sharma, Sanjeev. DevOps Adoption Playbook: A Guide to Adopting DevOps in a Multi-Speed IT Enterprise. Wiley & Sons, Limited, John, 2017.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Sharma, Sanjeev. DevOps Adoption Playbook: A Guide to Adopting DevOps in a Multi-Speed IT Enterprise. Wiley & Sons, Incorporated, John, 2017.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Sharma, Sanjeev. DevOps Adoption Playbook: A Guide to Adopting DevOps in a Multi-Speed IT Enterprise. Wiley & Sons, Incorporated, John, 2017.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

The DevOps adoption playbook: A guide to adopting DevOps in a multi-speed IT enterprise. Wiley, 2017.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Learning DevOps: A Comprehensive Guide to Accelerating DevOps Culture Adoption with Terraform, Azure DevOps, Kubernetes, and Jenkins. de Gruyter GmbH, Walter, 2022.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Krief, Mikael. Learning DevOps: A comprehensive guide to accelerating DevOps culture adoption with Terraform, Azure DevOps, Kubernetes, and Jenkins, 2nd Edition. Packt Publishing, 2022.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Coupland, Martyn. DevOps Adoption Strategies : Principles, Processes, Tools, and Trends: Embracing DevOps through effective culture, people, and processes. Packt Publishing, 2021.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "DevOps adoption"

1

Pando, Brian, Abel Silva, and Abraham Dávila. "DevOps Adoption: A Tertiary Study." In Studies in Computational Intelligence. Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-50590-4_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Smeds, Jens, Kristian Nybom, and Ivan Porres. "DevOps: A Definition and Perceived Adoption Impediments." In Lecture Notes in Business Information Processing. Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-18612-2_14.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Pérez-Sánchez, Juanjo, Saima Rafi, Juan Manuel Carrillo de Gea, Joaquín Nicolás Ros, and José Luis Fernández Alemán. "A Taxonomy on Human Factors that Affect DevOps Adoption." In Lecture Notes in Networks and Systems. Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-60221-4_31.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Krey, Mike, Stefan Koruna, Ahmad Kabbout, Armend Saliji, and Lavdrim Osmani. "A Method for the Adoption of DevOps in SMEs." In Springer Proceedings in Business and Economics. Springer Nature Switzerland, 2025. https://doi.org/10.1007/978-3-031-77363-1_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Riungu-Kalliosaari, Leah, Simo Mäkinen, Lucy Ellen Lwakatare, Juha Tiihonen, and Tomi Männistö. "DevOps Adoption Benefits and Challenges in Practice: A Case Study." In Product-Focused Software Process Improvement. Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-49094-6_44.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Sallin, Marc, Martin Kropp, Craig Anslow, James W. Quilty, and Andreas Meier. "Measuring Software Delivery Performance Using the Four Key Metrics of DevOps." In Lecture Notes in Business Information Processing. Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-78098-2_7.

Full text
Abstract:
Abstract The Four Key Metrics of DevOps have become very popular for measuring IT-performance and DevOps adoption. However, the measurement of the four metrics deployment frequency, lead time for change, time to restore service and change failure rate is often done manually and through surveys - with only few data points. In this work we evaluated how the Four Key Metrics can be measured automatically and developed a prototype for the automatic measurement of the Four Key Metrics. We then evaluated if the measurement is valuable for practitioners in a company. The analysis shows that the chosen measurement approach is both suitable and the results valuable for the team with respect to measuring and improving the software delivery performance.
APA, Harvard, Vancouver, ISO, and other styles
7

Alves, Álax, and Carla Rocha. "Assuring the Evolvability of Legacy Systems in Devops Transformation/Adoption: Insights of an Experience Report." In Agile Methods. Springer International Publishing, 2023. http://dx.doi.org/10.1007/978-3-031-25648-6_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Curry, Edward, Sonja Zillner, Andreas Metzger, et al. "Technical Research Priorities for Big Data." In The Elements of Big Data Value. Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-68176-0_5.

Full text
Abstract:
AbstractTo drive innovation and competitiveness, organisations need to foster the development and broad adoption of data technologies, value-adding use cases and sustainable business models. Enabling an effective data ecosystem requires overcoming several technical challenges associated with the cost and complexity of management, processing, analysis and utilisation of data. This chapter details a community-driven initiative to identify and characterise the key technical research priorities for research and development in data technologies. The chapter examines the systemic and structured methodology used to gather inputs from over 200 stakeholder organisations. The result of the process identified five key technical research priorities in the areas of data management, data processing, data analytics, data visualisation and user interactions, and data protection, together with 28 sub-level challenges. The process also highlighted the important role of data standardisation, data engineering and DevOps for Big Data.
APA, Harvard, Vancouver, ISO, and other styles
9

Azad, Nasreen. "DevOps Challenges and Risk Mitigation Strategies by DevOps Professionals Teams." In Lecture Notes in Business Information Processing. Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-53227-6_26.

Full text
Abstract:
AbstractDevOps is a team culture and organizational practice that eliminates inefficiencies and bottlenecks in the DevOps infrastructure. While many companies are adopting DevOps practices, it can still be risky. We conducted 26 interviews with DevOps professionals around the globe and found four major risks associated with DevOps practices: Organizational risks (Intra-organizational collaboration and communication, strategic planning), Social and cultural risks (Team Dynamics, Cultural shift), Technical risks (Integration, Build and test automation), Ethics and security breaches in DevOps environment (Ethical risks, Data collection ethics, Ethical decision making). Our research also identified several risk mitigation strategies namely continuous testing, using infrastructure as code, security audit and monitoring, disaster recovery planning, cross-functional training, proper documentation, continuous learning, continuous improvement etc. that companies can adopt for better performance and efficiency.
APA, Harvard, Vancouver, ISO, and other styles
10

Krishna Kaiser, Abhinav. "Adopting a Product-Led Approach." In Reinventing ITIL® and DevOps with Digital Transformation. Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9072-9_15.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "DevOps adoption"

1

Raudenbush, Katherine, Nikola Malinov, Jayanth V. Reddy, Chaoying Ding, Huayu Tian, and Marianthi Ierapetritou. "Towards the Development of Digital Twin for Pharmaceutical Manufacturing." In Foundations of Computer-Aided Process Design. PSE Press, 2024. http://dx.doi.org/10.69997/sct.135296.

Full text
Abstract:
Pharma 4.0 has continued to advance as the industry develops advances in process analytical technologies, automation, and digit-ization. Digital twins which transform on-line process measure-ments into meaningful outputs in real-time are being developed to seize the opportunity made possible with this shift. Digital twins can be used for improved process optimization on a range of scales, from determining optimal metabolite concentrations in upstream bioreactors to considering economic and environmental impacts of process decisions. In this paper, we explore the current uses of digital twins in solid-based pharmaceutical space and the bio-pharmaceutical manufacturing. Applications cover scale up of upstream processes, product quality control, and consideration of continuous systems. We also describe the intersection of digital twins in flow sheet modeling, sensitivity analysis and optimization, and design space evaluation. Finally, areas requiring further im-provement for industry adoption are addressed.
APA, Harvard, Vancouver, ISO, and other styles
2

Rupert, Angus, Braden McGrath, Joe McKay, Sergey Drakunov, and John Ramiccio. "A Simple Short-Term Solution to Helicopter Spatial Disorientation During Operations in Degraded Visual Environments." In Vertical Flight Society 70th Annual Forum & Technology Display. The Vertical Flight Society, 2014. http://dx.doi.org/10.4050/f-0070-2014-9485.

Full text
Abstract:
For the past 10 years, the number one operational helicopter problem reported by the military operating in desert environments is the inability to maintain control of the aircraft in degraded visual environments (DVE). A DVE mishap is a special subset of the Spatial Disorientation (SD) mishap. SD is defined as the inability of the pilot to correctly perceive the position, motion or attitude of the aircraft relative to the earth or other significant objects. The U.S. military establishment has been developing a three-pronged approach to reduce the problem of operating helicopters in DVE including; the development of active sensors capable of sufficient dust penetration to form an image of the terrain and obstacles, enhanced automation that improves pilot ability to maintain control, and improved man-machine interfaces that increase pilots awareness of spatial orientation. Rather than continuing down the traditional path of ever more complex advanced visual displays that have continuously added to workload and divided attention from the outside environment, it is now time to consider the adoption/addition of a non-visual display technology for veridical orientation information. Non-visual displays will permit the pilot to devote visual attention to either visual instruments or transition to search for outside visual cues while fully confident he/she is in full control of the aircraft despite being in a DVE environment. All animals in nature use this approach - multiple sensory systems to provide redundant, concurrent information that automatically maintains spatial orientation.
APA, Harvard, Vancouver, ISO, and other styles
3

Krey, Mike. "DevOps Adoption: Challenges & Barriers." In Hawaii International Conference on System Sciences. Hawaii International Conference on System Sciences, 2022. http://dx.doi.org/10.24251/hicss.2022.877.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Maroukian, Krikor, and Stephen R. Gulliver. "Leading DevOps Practice and Principle Adoption." In 9th International Conference on Information Technology Convergence and Services (ITCSE 2020). AIRCC Publishing Corporation, 2020. http://dx.doi.org/10.5121/csit.2020.100504.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Jones, Stephen, Joost Noppen, and Fiona Lettice. "Management challenges for DevOps adoption within UK SMEs." In ISSTA '16: International Symposium on Software Testing and Analysis. ACM, 2016. http://dx.doi.org/10.1145/2945408.2945410.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Rafi, Saima, Wu Yu, and Muhammad Azeem Akbar. "Towards a Hypothetical Framework to Secure DevOps Adoption." In EASE '20: Evaluation and Assessment in Software Engineering. ACM, 2020. http://dx.doi.org/10.1145/3383219.3383285.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Maroukian, Krikor, and Stephen R. Gulliver. "Synthesis of a Leadership Model for DevOps Adoption." In ESSE 2021: 2021 2nd European Symposium on Software Engineering. ACM, 2021. http://dx.doi.org/10.1145/3501774.3501783.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Toh, M. Zulfahmi, Shamsul Sahibuddin, and Rohani Abu Bakar. "A Review on DevOps Adoption in Continuous Delivery Process." In 2021 International Conference on Software Engineering & Computer Systems and 4th International Conference on Computational Science and Information Management (ICSECS-ICOCSIM). IEEE, 2021. http://dx.doi.org/10.1109/icsecs52883.2021.00025.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Offerman, Tyron, Robert Blinde, Christoph Johann Stettina, and Joost Visser. "A Study of Adoption and Effects of DevOps Practices." In 2022 IEEE 28th International Conference on Engineering, Technology and Innovation (ICE/ITMC) & 31st International Association For Management of Technology (IAMOT) Joint Conference. IEEE, 2022. http://dx.doi.org/10.1109/ice/itmc-iamot55089.2022.10033313.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Jayakody, J. A. V. M. K., and W. M. J. I. Wijayanayake. "Process Improvement Framework for DevOps Adoption in Software Development." In 2023 International Research Conference on Smart Computing and Systems Engineering (SCSE). IEEE, 2023. http://dx.doi.org/10.1109/scse59836.2023.10214992.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "DevOps adoption"

1

Luo, Jingshu. The diffusion of NAIC model laws. Center for Insurance Policy and Research, 2022. http://dx.doi.org/10.52227/25404.2022.

Full text
Abstract:
In the state-based insurance regulatory system, the National Association of Insurance Commissioners (NAIC) develops model laws that create a framework for uniform standards. This uniformity among states is beneficial to insurers, especially those operating in multiple states. Since the first NAIC meeting in 1871, the NAIC has issued over 200 model laws. Though NAIC model laws have existed for decades, little attention has been paid to understanding how they spread from the NAIC to states and from states to states. This spread is a policy diffusion process, which refers to the external factors that impact states’ policy adoption. In this project, we study the general pattern in the diffusion process and key factors that affect states’ decisions to implement NAIC model laws. We aim to answer the following questions: Do the NAIC or early-adopting states exert greater influence on leading states to adopt model laws? Are there common factors that may explain state legislatures’ adoption of model laws?
APA, Harvard, Vancouver, ISO, and other styles
2

Nimesh, Vikas, Bhaskar Natarjan, Saddam Hussain, and K. N. Hemanth Kumar. CATALYSING THE MARKET TRANSFORMATION OF ELECTRIC 2-WHEELER INSIGHTS FROM CONSUMERS AND STAKEHOLDERS. Alliance for an Energy Efficient Economy (AEEE), 2023. http://dx.doi.org/10.62576/aeee2w.

Full text
Abstract:
Electric two-wheelers (E2Ws) are becoming increasingly popular as an eco-friendly mode of transport. They provide a convenient and efficient option for short-distance travel, particularly in urban areas. However, the widespread adoption of E2Ws in India still faces several challenges. In order to address these issues, the Alliance for an Energy Efficient Economy (AEEE) and International Copper Association India (ICA India) have teamed up to identify the key barriers hindering the adoption of electric two-wheelers in the market. The joint research project aims to identify effective pathways for a market transformation for E2Ws in India and promote the widespread adoption of E2Ws as a sustainable and efficient mode of transport. The goal of the study is to facilitate the increased adoption of E2Ws in India by examining the perspectives of various stakeholders, including consumers, fleet operators, financial institutions, dealerships, and service centers. The study was conducted in three zones - North Zone (Delhi, Lucknow), West Zone (Mumbai, Jaipur, Ahmedabad, Rajkot), and South Zone (Bangalore, Coimbatore, Hyderabad, Chennai). The study collected 1159 responses from both E2W users and internal combustion engine (ICE) users across India, as well as E2W dealers, in order to gain a more comprehensive understanding of the E2W market across the country. The survey results revealed key insights about the prevalence of E2W users, their awareness of ICE options, and their willingness to adopt more eco-friendly modes of transport. The report covers key aspects of E2Ws, including purchase, charging, performance, aftersales, safety, retrofitting, etc. Chapter 1 introduces the E2W ecosystem and sets the background and need for the study. Chapter 2 details the scope and methodology adopted for the research. Various barriers and motivating factors and their role in attracting or deterring consumers from or towards EV adoption, like charging practices, usage behaviour, ownership cost, purchase experience, etc., were delved into. The chapter also details the respondents’ profiles and the surveying techniques incorporated for the study, i.e., face-toface interviews with E2W users and In-person qualitative discussions with the E2W dealers. It was found that the younger generations had an equal propensity towards both ICE and E2Ws. Also, the average income of EV owners was found to be higher than the average income of ICE two-wheelers. Chapter 3 discusses the findings and key insights from the consumer survey. It examines the key perceptions of customers regarding E2W and ICE vehicles and their purchase and usage practices. The chapter discusses important current and future triggers and barriers to EV adoption. Access to charging stations, Safety concerns, high upfront costs, long charging times, etc., were found to be the major deterrents towards EV adoption. Chapter 4 presents the key insights from the dealer consultation and discusses the various obstacles, including warranty and battery replacement costs, low margins, the lack of supplier credit facilities, battery backup, the high price of E2Ws, and low speed. These obstacles impede their ability to sell electric vehicles and compete with other types of vehicle dealers. Nonetheless, as the EV market grows and develops, manufacturers and dealers will be able to overcome these obstacles and establish a more sustainable and competitive EV industry. Chapter 4 presents the key insights from the dealer consultation and discusses the various obstacles dealers face, including warranty and battery replacement costs, low margins, the lack of supplier credit facilities, battery backup, the high price of E2Ws, and low speed. These obstacles impede their ability to sell electric vehicles and compete with other types of vehicle dealers. Nonetheless, as the EV market grows and develops, manufacturers and dealers will be able to overcome these obstacles and establish a more sustainable and competitive EV industry. Chapter 5 provides recommendations to address the different barriers to E2W adoption in India, like high upfront costs of E2W, charging stations, safety issues, battery issues, etc. The whitepaper provides recommendations to address the challenges and barriers hindering the adoption of E2Ws in India. These recommendations cover various topics such as consumer perceptions, demand incentives, and product-related issues like servicing, safety, and performance. To encourage ix the wider adoption of E2Ws, the whitepaper proposes several measures, including improving the availability of charging infrastructure, regular maintenance of charging points, and investment support to charging and swapping players. Additionally, partnering with financial institutions to offer affordable loans is recommended to make E2Ws more accessible to consumers. These measures are critical to overcoming the challenges faced by E2W users and promoting the adoption of ecofriendly transport options in India. To achieve the target of increasing energy efficiency and reducing carbon emissions by 33-35% by 2030, as set by the Indian government, it is crucial for the various stakeholders in the electric vehicle ecosystem to implement the strategies outlined in the whitepaper. The aim is to accelerate the adoption of E2Ws and support the government in achieving its goals.
APA, Harvard, Vancouver, ISO, and other styles
3

London, Jonathan D. Adoption, Adaption, and the Iterative Challenges of Scaling up in Vietnam: Policy Entrepreneurship and System Coherence in a Major Pedagogical Reform. Research on Improving Systems of Education (RISE), 2023. http://dx.doi.org/10.35489/bsg-rise-misc_2023/11.

Full text
Abstract:
Đặng Tự Ân played a pivotal role in the genesis, adoption, and diffusion of pedagogical and curricular reforms that are transforming teaching and learning in the Socialist Republic of Vietnam. His is a fascinating story of a career that began with the paralyzing disappointment of being assigned to study in a seemingly lowly teacher training college only to culminate, decades later, in his central role in the research, design, piloting, and scaling up of a reform that, despite numerous difficulties, would shape the most far-reaching and progressive curricular reforms in Vietnam’s long educational history. This essay uses the case of VNEN, a pedagogical and curricular reform adapted to Vietnam from the Colombian Escuela Nueva (EN) model, to advance our understanding of the challenges policy entrepreneurs and networks of policy stakeholders can encounter in efforts to institute pathbreaking reforms and of the formidable challenges they can encounter in bringing such reforms to scale. In contemporary research on the political economy of education and learning, the notion of an education system’s coherence for learning refers to the extent to which an education system develops relations of accountability that support improved learning outcomes across a range of relationships that define an education system and an array of policy design elements that education policies contain (Pritchett 2015, Kaffenberger and Spivack 2022). In the development literature, the notion of iterative adaptation speaks to a process wherein the performance of policies can improve rapidly through experimentation rather than mechanical transplantation of “best practices” (Andrews et al. 2013, Le 2018). From the standpoint of research on education systems and major reform efforts aimed at enhancing learning, the case of VNEN represents a particularly interesting instance of the innovation of pedagogical and curricular reforms that were, at their most successful moments, deeply coherent for learning, but which encountered problems at scale owing to a range of factors highlighted in this analysis. More broadly and however problematic at times, Vietnam’s VNEN experience contributed to the broad uptake and diffusion of new curricula and teaching practices. This raises questions about what we can learn from VNEN, including its successes and problems, that may have value for promoting continued improvement in Education systems performance around learning in Vietnam and other settings.
APA, Harvard, Vancouver, ISO, and other styles
4

Velasques de Paula Machado, Fabiana. To Redistribute or Not: A Politician`s Dilemma. Inter-American Development Bank, 2012. http://dx.doi.org/10.18235/0011413.

Full text
Abstract:
A prerequisite for the adoption of redistributive policies in a democracy is that there be elected representatives who are either committed to or who have an incentive to advocate for such policies. To evaluate the prospects of such an outcome, this paper develops a theory exploring two fundamental factors at play during elections - the critical political stage where citizens choose their representatives. The first is the lack of information about the policy inclinations of candidates. The second refers to two motivations compelling candidates into politics (and possibly at odds with each other): the opportunity to implement one's favored policies or to extract rents. Results indicate the existence of an equilibrium where high inequality and low redistribution can coexist. The theory's assumptions and outcomes are explored empirically using individual-level data collected in presidential election years in Brazil.
APA, Harvard, Vancouver, ISO, and other styles
5

Henriikka, Henriikka, Naudet Naudet, and Marin Dacos. Building a Global Research Initiative On Open Science. Ministère de l’enseignement supérieur et de la recherche, 2024. http://dx.doi.org/10.52949/54.

Full text
Abstract:
The Global Research Initiative on Open Science (GRIOS) represents a pioneering effort to systematically evaluate, promote, and implement Open Science practices worldwide. GRIOS will address the critical gaps in our understanding and application of Open Science. This initiative is a direct response to the growing recognition of Open Science's potential to democratise access to research findings, enhance the quality of scientific inquiry, and foster a more inclusive and collaborative research environment. GRIOS will catalyse the global adoption of Open Science by: - Conducting in-depth reviews of existing Open Science research to synthesise current knowledge and identify best practices and challenges. GRIOS will synergise with existing Open Science initiatives and research on open science to create a unique global understanding based on all the available knowledge. - Developing evidence-based recommendations to guide the implementation of Open Science practices and policies. - Creating a comprehensive research agenda to address knowledge gaps and promote further investigation into Open Science. - Establishing a global network of researchers and organisations committed to advancing Open Science, facilitating knowledge exchange, and fostering collaboration. A cornerstone of the GRIOS initiative is its commitment to inclusivity and diversity, ensuring that the full spectrum of the academic ecosystem is represented in its efforts, particularly emphasising the inclusion of knowledge and experience from the Global South and young academics. To achieve this, GRIOS governance reflects a broad range of perspectives and expertise to ensure that the policies, practices, and research agendas it develops are informed by a wide array of experiences and needs. This approach not only enriches the initiative's outputs with diverse insights but also fosters a more equitable and inclusive Open Science landscape. GRIOS represents a critical step forward in realising the full potential of Open Science. By systematically addressing the challenges and opportunities associated with Open Science,the initiative will play a pivotal role in shaping the future of research and its contribution to society. Stakeholders across the research ecosystem are invited to join this collaborative effort to advance Open Science and ensure that it serves the global public good. We urge research institutions, funders, policymakers, and practitioners to support and participate in the GRIOS initiative. Together, we can unlock the transformative power of Open Science and create a more open, inclusive, and impactful research landscape.
APA, Harvard, Vancouver, ISO, and other styles
6

Just, Richard E., Eithan Hochman, and Sinaia Netanyahu. Problems and Prospects in the Political Economy of Trans-Boundary Water Issues. United States Department of Agriculture, 2000. http://dx.doi.org/10.32747/2000.7573997.bard.

Full text
Abstract:
The objective of this research was to develop and apply a conceptual framework for evaluating the potential of trans-boundary bargaining with respect to water resource sharing. The research accomplished this objective by developing a framework for trans-boundary bargaining, identifying opportunities for application, and illustrating the potential benefits that can be gained thereby. Specifically, we have accomplished the following: - Developed a framework to measure the potential for improving economic efficiency considering issues of political feasibility and sustainability that are crucial in trans-boundary cooperation. - Used both cooperative and non-cooperative game theory to assess feasible coalitions among the parties involved and to model potential bargaining procedures. - Identified empirically alternative schemes of cooperation that both improve upon the economic efficiency of present water usage and appease all of the cooperating parties. - Estimated the potential short-run and long-run affects of water reallocation on the agricultural sector and used this information to understand potential strategies taken by the countries in bargaining processes. - Performed case studies in Israeli-Jordanian relations, the relationship of Israel to the Palestinian Authority, and cooperation on the Chesapeake Bay. - Published or have in process publication of a series of refereed journal articles. - Published a book which first develops the theoretical framework, then presents research results relating to the case studies, and finally draws implications for water cooperation issues generally. Background to the Topic The increase in water scarcity and decline in water quality that has resulted from increased agricultural, industrial, and urban demands raises questions regarding profitability of the agricultural sector under its present structure. The lack of efficient management has been underscored recently by consecutive years of drought in Israel and increased needs to clean up the Chesapeake Bay. Since agriculture in the Middle East (Chesapeake Bay) is both the main water user (polluter) and the low-value user (polluter), a reallocation of water use (pollution rights) away from agriculture is likely with further industrial and urban growth. Furthermore, the trans-boundary nature of water resources in the case of the Middle East and the Chesapeake Bay contributes to increased conflicts over the use of the resources and therefore requires a political economic approach. Major Conclusions, Solutions, Achievements and Implications Using game theory tools, we critically identify obstacles to cooperation. We identify potential gains from coordination on trans-boundary water policies and projects. We identify the conditions under which partial (versus grand) coalitions dominate in solving water quality disputes among riparian countries. We identify conditions under which linking water issues to unrelated disputes achieves gains in trans-boundary negotiations. We show that gains are likely only when unrelated issues satisfy certain characteristics. We find conditions for efficient water markets under price-determined and quantity-determined markets. We find water recycling and adoption of new technologies such as desalination can be part of the solution for alleviating water shortages locally and regionally but that timing is likely to be different than anticipated. These results have been disseminated through a wide variety of publications and oral presentations as well as through interaction with policymakers in both countries.
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography