Innovative practices for knowledge sharing in large-scale DevOps

<?xml version="1.0" encoding="UTF-8"?><modsCollection xmlns="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-8.xsd">
<mods version="3.8">
<titleInfo>
<title>Innovative practices for knowledge sharing in large-scale DevOps</title>
</titleInfo>
<name type="personal" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20220007726">
<namePart>Hemon, Aymeric</namePart>
<nameIdentifier>MAPA20220007726</nameIdentifier>
</name>
<name type="corporate" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20220007719">
<namePart>IEEE Computer Society</namePart>
<nameIdentifier>MAPA20220007719</nameIdentifier>
</name>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">periodical</genre>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">usa</placeTerm>
</place>
<dateIssued encoding="marc">2019</dateIssued>
<issuance>serial</issuance>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<physicalDescription>
<form authority="marcform">print</form>
</physicalDescription>
<abstract displayLabel="Summary">Agile development methods and DevOps require adaptation during implementation to meet the needs of a constantly changing software development environment. The emergence of knowledge-sharing practices for large-scale DevOps has not been the subject of much research. Our in-depth case study, comprising 106 interviews at a large multinational company operating in a DevOps at scale environment, identified a number of innovative practices which had emerged, principally to resolve knowledge-sharing challenges. These practices seem to be more likely to emerge in large-scale DevOps environments. While similar results might have been achieved due to the large-scale nature of the projects, it is difficult to determine definitively whether the main causal factor is project size or DevOps. We believe that self-organization and continuous improvement over a long period of time are also critical influencing factors</abstract>
<note type="statement of responsibility">Aymeric Hemon...[et al.]</note>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20220007597">
<topic>Metodologías DevOps</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20090042933">
<topic>Arquitectura de software</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20210030703">
<topic>Metodología Agile</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080572778">
<topic>Mejora continua</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20210010491">
<topic>Compartir datos</topic>
</subject>
<classification authority="">936</classification>
<relatedItem type="host">
<titleInfo>
<title> IEEE Software.-  New York : IEEE Computer Society</title>
</titleInfo>
<part>
<text>vol. 37, nº 3, 2019 ; p. 30-37</text>
</part>
</relatedItem>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">220829</recordCreationDate>
<recordChangeDate encoding="iso8601">20220912142920.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20220022606</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>