A paradox lens to systems development projects : the case of the agile software development

Iivari, Juhani (2021-07-28)
 
Avaa tiedosto
Lataukset: 

URL:
https://doi.org/10.17705/1CAIS.04901

Iivari, Juhani
Association for Information Systems
28.07.2021

Iivari, J. (2021). A Paradox Lens to Systems Development Projects: The Case of the Agile Software Development. Communications of the Association for Information Systems, 49, pp-pp. https://doi.org/10.17705/1CAIS.04901

https://rightsstatements.org/vocab/InC/1.0/
© 2021 by the Association for Information Systems. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and full citation on the first page. Copyright for components of this work owned by others than the Association for Information Systems must be honored. Abstracting with credit is permitted. To copy otherwise, to republish, to post on servers, or to redistribute to lists requires prior specific permission and/or fee. Request permission to publish from: AIS Administrative Office, P.O. Box 2712 Atlanta, GA, 30301-2712 Attn: Reprints are via e-mail from publications@aisnet.org.
https://rightsstatements.org/vocab/InC/1.0/
doi:https://doi.org/10.17705/1CAIS.04901
Näytä kaikki kuvailutiedot
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi-fe2021102552122
Tiivistelmä

Abstract

Research into organizations has concluded that organizational effectiveness is paradoxical (i.e., effective organizations must have simultaneously contradictory, even mutually exclusive, attributes). Although systems development projects constitute temporary organizations, researchers have largely omitted the paradox lens in their context. In this paper, I move toward rectifying the situation by focusing specifically on the agile software development (ASD) as a timely systems development approach in practice. I identify 11 interrelated and actable paradoxical tensions concerning the priority, structure, and execution of systems development projects. Each tension imposes competing demands on projects. To address them requires human ingenuity and judgement, though systems development methods and approaches can provide aid. I show that ASD comprises mechanisms for that purpose largely due to the reflective nature of the ASD process in which each retrospective assesses what went well in the previous sprint (iteration) and what could be improved in the next sprint. At the same time, ASD has built-in flexibility that makes it possible to adapt the method-in-use when deemed necessary or reasonable.

Kokoelmat