Start Date
11-12-2016 12:00 AM
Description
In this paper we critically examine the underlying assumptions in existing studies of large-scale agile software development. We use Alvesson and Sandberg’s problematization methodology and find that existing studies of large-scale agile share a number of underlying assumptions relevant to small rather than large-scale projects. Empirically, we draw on a case study of a large-scale agile project lasting nearly four years and involving more than 120 participants. Interestingly, the findings of the study contradict many of the assumptions in the literature review. For example, work across boundaries becomes at least as important as work within teams. We contribute by developing an alternative set of assumptions better suited to the characteristics of large-scale agile software development. Based on this, we re-conceptualize agile in the large, emphasizing both the complex knowledge boundaries within the project itself, as well as the interactive complexity and tight coupling with technologies and processes outside the project.
Recommended Citation
Rolland, Knut H.; Fitzgerald, Brian; Dingsoyr, Torgeir; and Stol, Klaas-Jan, "Problematizing Agile in the Large: Alternative Assumptions for Large-Scale Agile Development" (2016). ICIS 2016 Proceedings. 7.
https://aisel.aisnet.org/icis2016/ManagingIS/Presentations/7
Problematizing Agile in the Large: Alternative Assumptions for Large-Scale Agile Development
In this paper we critically examine the underlying assumptions in existing studies of large-scale agile software development. We use Alvesson and Sandberg’s problematization methodology and find that existing studies of large-scale agile share a number of underlying assumptions relevant to small rather than large-scale projects. Empirically, we draw on a case study of a large-scale agile project lasting nearly four years and involving more than 120 participants. Interestingly, the findings of the study contradict many of the assumptions in the literature review. For example, work across boundaries becomes at least as important as work within teams. We contribute by developing an alternative set of assumptions better suited to the characteristics of large-scale agile software development. Based on this, we re-conceptualize agile in the large, emphasizing both the complex knowledge boundaries within the project itself, as well as the interactive complexity and tight coupling with technologies and processes outside the project.