Responding to Change: Agile-in-the-large, Approaches and Their Consequences (original) (raw)
Related papers
Agility in Information Systems Development: A Three-Tiered Framework
The Agile Manifesto was put forward in 2001, and several method instantiations, such as XP, SCRUM and Crystal exist. Each adheres to some principles of the Agile Manifesto and disregards others. This paper proposes that these Agile Manifesto principles are insufficiently grounded in theory, and are largely naive to the concept of agility outside the field of software development. This research aims to develop a broad, three-tiered framework of ISD agility based on a thorough review of agility across many disciplines. The framework identifies the sources of agility, a classification of agile activities, and the resources utilized by such activities. Full Text at Springer, may require registration or fee
Its time to act: understanding and assessing agility in information systems development
2014
This paper focuses on addressing the question of how agile are agile methods. To do this I synthesize seven general features of agility, drawing on management and sociology disciplines, into a framework, to act as a ‘gold standard’ by which to compare agile methods. I found that agile methods did not entirely measure up to this framework and that they were lacking in terms of (i) survival, (ii) prospering or thriving on change, and (iii) being able to regulate and leverage emotions in action responses to change. This paper offers: (i) a framework for assessing agility in software development, (ii) the elucidation of a knowledge gap in agile methods with respect to emotion, and, (iii) a conceptualization that reveals the need to incorporate emotional regulation and leverage into assessments of agility.
Agile versus Agility: A Multi-Theory Perspective
Agile development principles have been shown to work only for small-sized software projects. When software projects, especially those that have a distributed element, are scaled up, agile manifesto-based principles may not lead to agility in development. Further, agile manifesto-based principles do not seem to have strong theoretical support in general. This paper distinguishes "agility principles" from "agile principles" and attempts to provide best practice recommendations that are based on theories popular in Information Systems, and reference-discipline fields.
2010
Abstract 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.
Towards Pertinent Characteristics of Agility and Agile Practices for Software Processes
CLEI Electronic Journal
Context: It is believed that agility in software processes can bring benefits to software development and lead to an economy of efforts when accommodating changes is needed. Objective: Assess pertinence and relevance of agility characteristics and agile practices for software processes. Method: From 18 agility characteristics and 17 agile practices applicable to software processes revealed through systematic literature reviews performed in 2010, a survey was conducted to assess their pertinence and relevance. Results: 16 agility characteristics and 15 agile practices were considered pertinent to insert agility in software processes. Conclusion: Results should be used sparingly. It would be interesting to replicate the study in other contexts, with different subjects, and compare them, to increase the generalization of their results.
Business agility and diffusion of information technology
European Journal of Information Systems, 2006
While agility has recently attracted considerable attention in studies of systems development and management of information technology (IT), there is limited recognition within the information systems discipline of the important impact agility has already had on organizational studies in general. The extensive literature on agile development approaches has, for example, few or no links to the considerable literature on organizational agility that has developed since the Agility Forum was founded at Lehigh University in 1991 (Dove, 2001). The purpose of this special issue is to bridge this gap and to create a strong foundation for continued studies of the relationship between business agility and the diffusion of IT into organizational contexts. We believe this to be a timely purpose as organizations rebalance their IT infrastructure and portfolio of IT innovations in preparation for the future.
Designing for Agility as an Organizational Capability: Learning from a Software Development Firm
The purpose of this paper is to investigate the nature of agility in an organizational setting-- how a software development firm (SDF) developed, maintained and enhanced agility as it changed from a developer of experimental prototypes to a product-based provider. Qualitative approach based on extensive interviews and on-site observations at two points in time separated by a five-year interval. Agility mechanisms tend to be dynamic and evolve over time. At time 1, SDF achieved agility by adopting a formal platform-based product design and an informal, organic organizational structure. By time 2, SDF had adopted a modular-based product design and a more formal structure. Implications include: (1) interdisciplinary-based framework to understand agility in the workplace; (2) multiple forms of agility and the dynamics among them; (3) re-conceptualization of agility as a new organizational capability; and, (4) causal relationship between agility and other organizational learning mechanis...
Toward a conceptual framework of agile methods: a study of agility in different disciplines
European Software Engineering Conference, 2004
Since the software crisis of the 1960's, numerous methodologies have been developed to impose a disciplined process upon software development. It is now widely accepted that these methodologies are unsuccessful and unpopular due to their increasingly bureaucratic nature. Many researchers and practitioners are calling for these heavyweight methodologies to be replaced by agile methods. The Agile Manifesto was put forward
Exploring the sources of enterprise agility in software organizations
2009
Organizations involved in the design, development and sustainment of software systems have to manage the tension between creating new products and services, while at the same time maintaining their existing portfolio. This paper explores the sources of enterprise agility in software firms, wherein agility is defined as the ability of the organization to sense changes in its environment (both internal and external), and effectively respond to these changes. Using engaged scholarship as the overarching paradigm, we report on the findings of a process study that uses semi-structured interviews, observation, and archival firm & project information for data gathering, and grounded theory methods and comparative case analysis for data analysis and theory generation. The analysis highlights the importance of the four organizational enablers of: stakeholder alignment, employee empowerment, group & organizational learning, and governance mechanisms, as necessary but not sufficient precursors to obtaining enterprise agility. Furthermore, we provide illustrative case examples of the three mechanisms: Continuous Improvement, Creating Systems of Innovation, and Leveraging Globally available Capabilities, that software organizations use to gain enterprise agility.
Toward Agile: An Integrated Analysis of Quantitative and Qualitative Field Data
Management Information Systems Quarterly, 2010
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 anec-Lee & Xia/Software Development Agility omy, 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.