<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Comparing Methods for Large-Scale Agile Software Development: A Systematic Literature Review</title>
  </titleInfo>
  <name type="personal">
    <namePart>Henry Edison</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
    <role>
      <roleTerm type="text">author.</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Xiaofeng Wang</namePart>
    <role>
      <roleTerm type="text">author.</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Kieran Conboy</namePart>
    <role>
      <roleTerm type="text">author.</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <genre authority="">Review articles.</genre>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">xx</placeTerm>
    </place>
    <dateIssued encoding="marc">2021</dateIssued>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <internetMediaType>application/pdf</internetMediaType>
    <extent>1 online resource (1 article).</extent>
  </physicalDescription>
  <abstract>Following the highly pervasive and effective use of agile methods at the team level, many software organisations now wish to replicate this success at the organisational level, adopting large-scale agile methods such as SAFe, Scrum-at-Scale, and others. However, this has proven significantly challenging. An analysis of the extant literature reveals a disparate set of studies across each individual method, with no cross-method comparison based on empirical evidence. This systematic literature review compares the main large-scale agile methods, namely SAFe, LeSS, Scrum-at-Scale, DAD, and the Spotify model. It is the first study to analyse and compare each of the method’s principles, practices, tools, and metrics in a standardised manner. For each method, it presents not just the original method specifications but also all extensions and modifications to each method proposed by subsequent empirical research. It includes in this comparison not just commercial large-scale methods but also those that have been custom-built in organisations such as Nokia, Ericsson, and others. Based on the findings reported in this study, practitioners can make a more informed decision as to which commercial method or method component or, indeed, custom-built method is better suited to their needs. Our study reveals a number of theoretical and practical issues in the current literature, such as an emphasis on the practices of commercial frameworks at the expense of their underlying principles, or indeed any of the custom method. A set of challenges and success factors associated with the use of large-scale agile methods are identified. The study also identifies a number of research gaps to be addressed across methods.</abstract>
  <note type="statement of responsibility">Henry Edison; Xiaofeng Wang; Kieran Conboy.</note>
  <note>Publication type: Review article.</note>
  <note>Linked open-access copy: published version.</note>
  <note>Open access; no subscription required for the linked open-access version. Unrestricted online access star</note>
  <note xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://openalex.org/W3145402715">Creative Commons Attribution (licence family recorded by the source; version not supplied in metadata). https://openalex.org/W3145402715</note>
  <note>In English.</note>
  <subject>
    <topic>Scaled Agile Framework</topic>
  </subject>
  <subject>
    <topic>LESS</topic>
  </subject>
  <subject>
    <topic>DAD</topic>
  </subject>
  <subject>
    <topic>method comparison</topic>
  </subject>
  <subject>
    <topic>success factors</topic>
  </subject>
  <subject>
    <topic>research gaps</topic>
  </subject>
  <subject>
    <topic>B. Sc. Software Engineering</topic>
  </subject>
  <subject>
    <topic>UMUN open access collection</topic>
  </subject>
  <subject>
    <topic>agile software</topic>
  </subject>
  <relatedItem type="host">
    <titleInfo>
      <title>IEEE Transactions on Software Engineering</title>
    </titleInfo>
    <identifier type="issn">0098-5589</identifier>
    <part>
      <text>Vol. 48, no. 8, (2021), pages/article 2709-2731</text>
    </part>
  </relatedItem>
  <identifier type="uri">https://ieeexplore.ieee.org/ielx7/32/9857502/09387593.pdf</identifier>
  <location>
    <url displayLabel="Read open-access publication">https://ieeexplore.ieee.org/ielx7/32/9857502/09387593.pdf</url>
  </location>
  <accessCondition type="restrictionOnAccess">Open access; no subscription required for the linked open-access version.</accessCondition>
  <accessCondition type="useAndReproduction">Creative Commons Attribution (licence family recorded by the source; version not supplied in metadata).</accessCondition>
  <recordInfo>
    <recordContentSource authority="marcorg">local</recordContentSource>
    <recordCreationDate encoding="marc">261005</recordCreationDate>
    <recordChangeDate encoding="iso8601">20261005174821.0</recordChangeDate>
    <recordIdentifier source="local">UMUN-OA-20261005-SE-037</recordIdentifier>
    <languageOfCataloging>
      <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
    </languageOfCataloging>
  </recordInfo>
</mods>
