Conceptualizing a tool based DevOps maturity model

<?xml version="1.0" encoding="UTF-8"?><modsCollection xmlns="" xmlns:xsi="" xsi:schemaLocation="">
<mods version="3.8">
<title>Conceptualizing a tool based DevOps maturity model</title>
<name type="personal" usage="primary" xmlns:xlink="" xlink:href="MAPA20220007733">
<namePart>Nandhakumar Sidharrth, Janardhan </namePart>
<name type="corporate" xmlns:xlink="" xlink:href="MAPA20220007740">
<namePart>University of South-Eastern Norway</namePart>
<namePart>Department of Economics, Marketing and Law</namePart>
<placeTerm type="code" authority="marccountry">nor</placeTerm>
<placeTerm type="text">Hønefoss, Norway</placeTerm>
<publisher>University of South-Eastern Norway, Department of Economics, Marketing and Law</publisher>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
<form authority="marcform">print</form>
<extent>71 p.</extent>
<abstract displayLabel="Summary">With the fast transition in technology, creative organizations are fuelling the customer experience with exceptional end-to-end services at extremely high speeds due to their capacity to adapt to client requests more quickly. To stay competitive, an increasing number of IT companies are investing more heavily in learning and expanding their capabilities in order to deliver the best possible service to their clients. DevOps is one such approach of implementing a set of principles in both development and information technology operations with the goal of reducing application and software system development lifecycles while maintaining consistently high-quality software. Numerous effective DevOps implementation attempts have already been made in the prior literature, but many organizations have still not been able to achieve the full benefits of DevOps adoption in their day-to-day development and operations within the organizations. This is primarily due to a lack of understanding of the current level of maturity the organization is starting the adoption at. As a result, this study aims to clarify the necessity of maturity models and also create a framework for implementing them. A semi systematic analysis of the literature and qualitative interviews with experts were used to develop the DevOps maturity model which justifies the necessity to add tool capability while measuring the maturity of an organisation, which was then validated by expert judgments.</abstract>
<note type="statement of responsibility">Janardhan Nandhakumar Sidharrth</note>
<note>Master's Thesis Study programme: Management Information System, Spring 2022</note>
<subject xmlns:xlink="" xlink:href="MAPA20220007597">
<topic>Metodologías DevOps</topic>
<subject xmlns:xlink="" xlink:href="MAPA20100030493">
<topic>Business intelligence</topic>
<subject xmlns:xlink="" xlink:href="MAPA20150006509">
<topic>Experiencia del cliente</topic>
<subject xmlns:xlink="" xlink:href="MAPA20080623791">
<topic>Tecnología de la información</topic>
<subject xmlns:xlink="" xlink:href="MAPA20080568009">
<subject xmlns:xlink="" xlink:href="MAPA20080664510">
<topic>Trabajos de investigación</topic>
<classification authority="">922.111.2</classification>
<relatedItem type="series" xmlns:xlink="" xlink:href="MAPA20160014013">
<title>Trabajos Fin de Master</title>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">160905</recordCreationDate>
<recordChangeDate encoding="iso8601">20220912134337.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20220022613</recordIdentifier>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>