IRMA-International.org: Creator of Knowledge
Information Resources Management Association
Advancing the Concepts & Practices of Information Resources Management in Modern Organizations

Ineffective Decision Making in Adopting an Agile Software Development Methodology

Ineffective Decision Making in Adopting an Agile Software Development Methodology
View Sample PDF
Author(s): John McAvoy (University of College Cork, Ireland)and Tom Butler (University of College Cork, Ireland)
Copyright: 2008
Pages: 8
Source title: Encyclopedia of Decision Making and Decision Support Technologies
Source Author(s)/Editor(s): Frederic Adam (University College Cork, Ireland)and Patrick Humphreys (London School of Economics, UK)
DOI: 10.4018/978-1-59904-843-7.ch053

Purchase

View Ineffective Decision Making in Adopting an Agile Software Development Methodology on the publisher's website for pricing and purchasing information.

Abstract

Agile software development (ASD) is now widely used in the software development industry; accordingly, it has been the focus of research with studies featuring in a variety of journals—notable examples are special issues of IEEE Computer (Volume 36, Issue 6) and IEEE Software (Volume 20, Issue 3). The decision by organisations and project teams to adopt an agile methodology is of particular interest to researchers, with the main aim of such studies being to produce a tool or system to assist in that decision. Examples of this research stream are to be found in research by Boehm and Turner (2003, 2004), McAvoy and Sammon (2006), and Pikkarainen and Passoja (2005). Decision making in these treats it as occurring over a short time frame, ending with a specific decision. In Mintzberg, Raisinghani, and Théorêt (1976), decision making is seen to be bounded by the identification of a need for action and ends with a commitment to take specific action. Despite Mintzberg et al.’s (1976) bounding of decision making, commitment to a particular decision can not be assumed to last. The implementation of a decision is longitudinal— that is, its lifecycle is from the commitment to action through to the completion of the action or actions. Throughout the implementation of a decision, many more related decisions are made: for example, decisions based on such considerations as: Do we continue to adopt? Do we need to alter the original decision? Do we need to reassess the actions decided upon? The decision to adopt a software development methodology aligns more with a longitudinal view of decision making than with conceptualizations of decision making as a once off phenomenon. Robin and Finley (1998) argue that the operationalisation of a decision is more significant than the method adopted to arrive at the initial decision. Thus, it may be deduced that in investigating the adoption of an ASD, there needs be a consideration of decision making beyond that of a single meeting or decision point, and the focus broadened to include the impact of time on how decisions are made and actions taken. It is clear from the studies quoted that over the lifecycle of a decision various factors can impact on outcomes associated with decision taking. For example, the group that makes or applies the decision can have a major impact on resulting outcomes, which can be negative—McGrath (1984) for example, discusses many of the decision-related factors that group interaction can influence.

Related Content

Yu Bin, Xiao Zeyu, Dai Yinglong. © 2024. 34 pages.
Liyin Wang, Yuting Cheng, Xueqing Fan, Anna Wang, Hansen Zhao. © 2024. 21 pages.
Tao Zhang, Zaifa Xue, Zesheng Huo. © 2024. 32 pages.
Dharmesh Dhabliya, Vivek Veeraiah, Sukhvinder Singh Dari, Jambi Ratna Raja Kumar, Ritika Dhabliya, Sabyasachi Pramanik, Ankur Gupta. © 2024. 22 pages.
Yi Xu. © 2024. 37 pages.
Chunmao Jiang. © 2024. 22 pages.
Hatice Kübra Özensel, Burak Efe. © 2024. 23 pages.
Body Bottom