Agile Software Development Approaches Research Articles

Toward Agile: An Integrated Analysis of Quantitative and Qualitative Field Data on Software Development Agility

As business and technology environments change at an unprecedented rate, software development agility to respond to changing user requirements has become increasingly critical for software development performance. Agile software development approaches, which emphasize sense-and-respond, self-organization, cross-functional teams, and continuous adaptation, have been adopted by an increasing number of organizations to improve their software development agility. However, the agile development literature is largely anecdotal and prescriptive, lacking empirical evidence and theoretical foundation to support the principles and practices of agile development. Little research has empirically examined the software development agility construct in terms of its dimensions, determinants, and effects on software development performance. As a result, there is a lack of understanding about how organizations can effectively implement an agile development approach. Using an integrated research approach that combines quantitative and qualitative data analyses, this research opens the black box of agile development by empirically examining the relationships among two dimensions of software development agility (software team response extensiveness and software team response efficiency), two antecedents that can be controlled (team autonomy and team diversity), and three aspects of software development performance (on-time completion, on-budget completion, and software functionality). Our PLS results of survey responses of 399 software project managers suggest that the relationships among these variables are more complex than what has been perceived by the literature. The results suggest a tradeoff relationship between response extensiveness and response efficiency. These two agility dimensions impact software development performance differently: response efficiency positively affects all of on-time completion, on-budget completion, and software functionality, whereas response extensiveness positively affects only software functionality. The results also suggest that team autonomy has a positive effect on response efficiency and a negative effect on response extensiveness, and that team diversity has a positive effect on response extensiveness. We conducted 10 post hoc case studies to qualitatively cross-validate our PLS results and provide rich, additional insights regarding the complex, dynamic interplays between autonomy, diversity, agility, and performance. The qualitative analysis also provides explanations for both supported and unsupported hypotheses. We discuss these qualitative analysis results and conclude with the theoretical and practical implications of our research findings for agile development approaches.

COMPARING TRADITIONAL AND AGILE DEVELOPMENT APPROACHES: THE CASE OF EXTREME PROGRAMMING

Some adherents of agile development feel their approach goes against the predominant tenets of existing traditional approaches to software development, and thus can invoke fear and anxiety in practitioners. One way to understand if and how agile methods differ from existing approaches is to explore one agile approach in depth and, if possible, its philosophical underpinnings to see in what way it presents a new and different view of the software development process. This paper works to understand some of the philosophical underpinnings of Extreme Programming (XP), an agile software development approach. The study uses a qualitative data analysis approach to address the following research questions: 1) what philosophy underlies XP, and 2) does XP's philosophy differ from the dominant software development paradigm? The paper finds that Extreme Programming reflects many pragmatic philosophical viewpoints and that many of its tenets conflict with the rationalistic approach that underlies traditional software development discourse.

Agile software development: the business of innovation

The rise and fall of the dotcom-driven Internet economy shouldn't distract us from seeing that the business environment continues to change at a dramatically increasing pace. To thrive in this turbulent environment, we must confront the business need for relentless innovation and forge the future workforce culture. Agile software development approaches, such as extreme programming, Crystal methods, lean development, Scrum, adaptive software development (ASD) and others, view change from a perspective that mirrors today's turbulent business and technology environment.