2020 | Information Systems Journal | Citations: 62
Authors: Venkatesh, Viswanath; Thong, James Y. L.; Chan, Frank K. Y.; Hoehle, Hartmut; Spohrer, Kai
Abstract: Agile methods are widely used in the software industry as a way to more rapidly ...
Expand
Abstract: Agile methods are widely used in the software industry as a way to more rapidly develop and deliver new software. They define iterative work processes, advocate self-organization and openness for change, and prescribe how software developers interact with each other and external stakeholders. Despite their popularity, it is unclear how agile methods influence work exhaustion in software developers and how developer skills play into this effect. On the one hand, agile methods may reduce software developers' work exhaustion by levelling out their workload across the entire duration of a project. On the other hand, agile methods exert a high level of pressure on software developers to continuously deliver working software, create many intensive social interactions, and to frequently adapt to changes. In light of these effects, prior research could not explain why some software developers become less exhausted from using agile methods, whereas others perceive the exact opposite. Based on the job demand-control model, we develop a theoretical model connecting agile method use to individual developer skills and to two established determinants of employee exhaustion: role conflict and role ambiguity. We tested our research model in a field study among 1894 software developers in 217 project teams that used agile methods. The random coefficient modelling results show that agile method use facilitates the achievement of clear and unambiguous role perceptions and thereby reduces work exhaustion in developers, particularly if developers possess the organizational skills to effectively interact with others in their organization. We highlight implications for theory on the individual-level effects of software development methods and provide practical insights for software companies.
Collapse
Topics:
agile software development software developer system development method systems development project productivity
Methods:
design methodology field study theory development mediation analysis instrumental variables estimation
An Empirical Study Examining the Usage and Perceived Importance of XP Practices
2007 | Americas Conference on Information Systems | Citations: 0
Authors: Fruhling, Ann; Zhang, Jessica
Abstract: Extreme Programming (XP) is a well known agile software development methodology ...
Expand
Abstract: Extreme Programming (XP) is a well known agile software development methodology which is ideal for projects featured as highly unpredictable in tasks with limited resources. The continuous discussion on the usage and importance of each XP practice lead us to explore what are the most important XP practices to be applied in certain projects. This study examined the actual usage amount and perceived importance of each XP practice by means of a cross-sectional anonymous survey conducted in local organizations which have implemented XP in their projects. Results indicate that Continuous Integration and Collective Ownership as the most important. Collective Ownership, Continuous Integration, Pair Programming, Planning Game and Sustainable Pace are used the most. Both practitioners and researchers can build upon these findings.
Collapse