Agility in Software Development and Project Value: An Empirical Investigation

Agility in Software Development and Project Value: An Empirical Investigation

VenuGopal Balijepally (Oakland University, Rochester, MI, USA), Gerald DeHondt (Ball State University, Muncie, IN, USA), Vijayan Sugumaran (Department of Decision and Information Sciences, Oakland University, Rochester, MI, USA, & Department of Global Service Management, Sogang University, Seoul, Korea) and Sridhar Nerur (University of Texas at Arlington, Arlington, TX, USA)
Copyright: © 2017 |Pages: 20
DOI: 10.4018/JDM.2017100103
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.
Article Preview

Agile Software Development

Ambler (Ambler, 2012) defines agile development as “an iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner by self-organizing teams within an effective governance framework, with ‘just enough’ ceremony that produces high quality solutions in a cost effective and timely manner which meets the changing needs of its stakeholders.” In this research we adopt this definition which is quite consistent with the principles and values enunciated in the agile manifesto (AgileAlliance, 2001).

Complete Article List

Search this Journal:
Reset
Open Access Articles
Volume 28: 4 Issues (2017)
Volume 27: 4 Issues (2016)
Volume 26: 4 Issues (2015)
Volume 25: 4 Issues (2014)
Volume 24: 4 Issues (2013)
Volume 23: 4 Issues (2012)
Volume 22: 4 Issues (2011)
Volume 21: 4 Issues (2010)
Volume 20: 4 Issues (2009)
Volume 19: 4 Issues (2008)
Volume 18: 4 Issues (2007)
Volume 17: 4 Issues (2006)
Volume 16: 4 Issues (2005)
Volume 15: 4 Issues (2004)
Volume 14: 4 Issues (2003)
Volume 13: 4 Issues (2002)
Volume 12: 4 Issues (2001)
Volume 11: 4 Issues (2000)
Volume 10: 4 Issues (1999)
Volume 9: 4 Issues (1998)
Volume 8: 4 Issues (1997)
Volume 7: 4 Issues (1996)
Volume 6: 4 Issues (1995)
Volume 5: 4 Issues (1994)
Volume 4: 4 Issues (1993)
Volume 3: 4 Issues (1992)
Volume 2: 4 Issues (1991)
Volume 1: 2 Issues (1990)
View Complete Journal Contents Listing