Innovative practices for knowledge sharing in large-scale DevOps

<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd">
  <record>
    <leader>00000cab a22000004b 4500</leader>
    <controlfield tag="001">MAP20220022606</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20220912142920.0</controlfield>
    <controlfield tag="008">220829e20190201usa|| p      |0|||b|eng d</controlfield>
    <datafield tag="040" ind1=" " ind2=" ">
      <subfield code="a">MAP</subfield>
      <subfield code="b">spa</subfield>
      <subfield code="d">MAP</subfield>
    </datafield>
    <datafield tag="084" ind1=" " ind2=" ">
      <subfield code="a">936</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="0">
      <subfield code="a">Innovative practices for knowledge sharing in large-scale DevOps</subfield>
      <subfield code="c">Aymeric Hemon...[et al.]</subfield>
    </datafield>
    <datafield tag="520" ind1=" " ind2=" ">
      <subfield code="a">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</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20220007597</subfield>
      <subfield code="a">Metodologías DevOps</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20090042933</subfield>
      <subfield code="a">Arquitectura de software</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20210030703</subfield>
      <subfield code="a">Metodología Agile</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080572778</subfield>
      <subfield code="a">Mejora continua</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20210010491</subfield>
      <subfield code="a">Compartir datos</subfield>
    </datafield>
    <datafield tag="700" ind1="1" ind2=" ">
      <subfield code="0">MAPA20220007726</subfield>
      <subfield code="a">Hemon, Aymeric</subfield>
    </datafield>
    <datafield tag="710" ind1="2" ind2=" ">
      <subfield code="0">MAPA20220007719</subfield>
      <subfield code="a">IEEE Computer Society</subfield>
    </datafield>
    <datafield tag="773" ind1="0" ind2=" ">
      <subfield code="t"> IEEE Software.-  New York : IEEE Computer Society</subfield>
      <subfield code="g">vol. 37, nº 3, 2019 ; p. 30-37</subfield>
    </datafield>
  </record>
</collection>