Understanding Agile Software Development Team Adaptation Processes

Understanding Agile Software Development Team Adaptation Processes

Jan Terje Karlsen, Anders Aaraas Pedersen, Max Paul Trautwein, Hans Solli-Sæther
Copyright: © 2022 |Pages: 25
DOI: 10.4018/IJRCM.290059
OnDemand:
(Individual Articles)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

This study is about team adaptation from a continuous change perspective. The purpose was to investigate how agile software development teams in a Nordic financial institution adapt to task-based triggers. A single case study was conducted of three software development teams in a product unit reporting that they worked in agile ways. One of the main findings is that the agile software development teams sought to define tasks to be worked on individually. The adaptation triggers occurring during taskwork mainly prompt task-related interaction. In addition, the findings support that these adaptation triggers can either prompt small adjustments to taskwork or be more severe and move the focus to evaluation and planning activities before taskwork can be continued. We propose a model describing how agile software development teams adapt to task-based triggers based on the findings.
Article Preview
Top

Introduction

All information systems development has inherent risks. If those risks are not handled properly, the development may exceed its schedule or budget, or the resulting product will fail to meet the customers’ needs. Approaches to information system development intended to improve performance outcomes by promoting agility have become increasingly popular in the last few decades (Campanelli & Parreiras, 2015; Cockburn & Highsmith, 2001; Conforto et al., 2016; Dingsøyr et al., 2012; Tam et al., 2020). Such approaches often are referred to collectively as “agile software development,” which many link to a set of defined methods and practices emphasizing iterative problem-solving, close collaboration and frequent customer interaction (Dybå & Dingsøyr, 2008). Agile software development represents a shift in philosophy that departs from what is considered “traditional” (Nerur & Balijepally, 2007), spurred by the inadequacy of traditional, plan-driven approaches in handling the extensive rate of change in business and technology (Lee & Xia, 2010). The core of agile software development is agility, which most researchers agree concerns software development teams’ ability to handle change successfully in order to create business value (Conboy, 2009; Conforto et al., 2016; Lee & Xia, 2010; Serrador & Pinto, 2015).

Because agility in information system development involves successful adaptation to change, which is a crucial aspect of team effectiveness (Burke et al., 2006; Mathieu et al., 2008), the team processes involved in how software development teams adapt to change are important. Team processes refer to how team members work with each other in order to facilitate goal-oriented work (Marks et al., 2001). Team adaptation can be considered a process involving “adjustments to relevant team processes […] in response to the disruption or trigger giving rise to the need for adaptation” (Maynard et al., 2015, p. 656). Even though human aspects of information system development long have been acknowledged as imperative (Cockburn & Highsmith, 2001), relatively few studies on information system development have leveraged the knowledge gained from the social sciences to address such issues (Lenberg et al., 2015). A literature search revealed that only Kude et al. (2014) leveraged team adaptation theory to better understand agility in information system development. Because the team adaptation literature revolves around how teams adapt to changing demands (Maynard et al., 2015), it can contribute to understanding how software development teams handle change to create business value.

Complete Article List

Search this Journal:
Reset
Volume 13: 1 Issue (2025): Forthcoming, Available for Pre-Order
Volume 12: 1 Issue (2024): Forthcoming, Available for Pre-Order
Volume 11: 4 Issues (2022): 1 Released, 3 Forthcoming
Volume 10: 4 Issues (2021)
Volume 9: 4 Issues (2020)
Volume 8: 4 Issues (2019)
Volume 7: 4 Issues (2018)
Volume 6: 4 Issues (2017)
Volume 5: 4 Issues (2016)
Volume 4: 4 Issues (2015)
Volume 3: 4 Issues (2014)
Volume 2: 4 Issues (2013)
Volume 1: 4 Issues (2012)
View Complete Journal Contents Listing