Information Systems Research current issue

Introduction to the Special Issue--Flexible and Distributed Information Systems Development: State of the Art and Research Challenges

Agerfalk, P. J., Fitzgerald, B., Slaughter, S. A. — 2009-09-20

No abstract available.

Agility from First Principles: Reconstructing the Concept of Agility in Information Systems Development

Conboy, K. — 2009-09-20

Awareness and use of agile methods has grown rapidly among the information systems development (ISD) community in recent years. Like most previous methods, the development and promotion of these methods have been almost entirely driven by practitioners and consultants, with little participation from the research community during the early stages of evolution. While these methods are now the focus of more and more research efforts, most studies are still based on XP, Scrum, and other industry-driven foundations, with little or no conceptual studies of ISD agility in existence. As a result, this study proposes that there are a number of significant conceptual shortcomings with agile methods and the associated literature in its current state, including a lack of clarity, theoretical glue, parsimony, limited applicability, and naivety regarding the evolution of the concept of agility in fields outside systems development. Furthermore, this has significant implications for practitioners, rendering agile method comparison and many other activities very difficult, especially in instances such as distributed development and large teams that are not conducive to many of the commercial agile methods. This study develops a definition and formative taxonomy of agility in an ISD context, based on a structured literature review of agility across a number of disciplines, including manufacturing and management where the concept originated, matured, and has been applied and tested thoroughly over time. The application of the texonomy in practice is then demonstrated through a series of thought trials conducted in a large multinational organization. The intention is that the definition and taxonomy can then be used as a starting point to study ISD method agility regardless of whether the method is XP or Scrum, agile or traditional, complete or fragmented, out-of-the-box or in-house, used as is or tailored to suit the project context.

Coevolving Systems and the Organization of Agile Software Development

Vidgen, R., Wang, X. — 2009-09-20

Despite the popularity of agile methods in software development and increasing adoption by organizations there is debate about what agility is and how it is achieved. The debate suffers from a lack of understanding of agile concepts and how agile software development is practiced. This paper develops a framework for the organization of agile software development that identifies enablers and inhibitors of agility and the emergent capabilities of agile teams. The work is grounded in complex adaptive systems (CAS) and draws on three principles of coevolving systems: match coevolutionary change rate, maximize self-organizing, and synchronize exploitation and exploration. These principles are used to study the processes of two software development teams, one a team using eXtreme Programming (XP) and the other a team using a more traditional, waterfall-based development cycle. From the cases a framework for the organization of agile software development is developed. Time pacing, self-management with discipline and routinization of exploration are among the agile enablers found in the cases studies while event pacing, centralized management, and lack of resources allocated to exploration are found to be inhibitors to agility. Emergent capabilities of agile teams that are identified from the research include coevolution of business value, sustainable working with rhythm, sharing and team learning, and collective mindfulness.

A Control Theory Perspective on Agile Methodology Use and Changing User Requirements

Maruping, L. M., Venkatesh, V., Agarwal, R. — 2009-09-20

In this paper, we draw on control theory to understand the conditions under which the use of agile practices is most effective in improving software project quality. Although agile development methodologies offer the potential of improving software development outcomes, limited research has examined how project managers can structure the software development environment to maximize the benefits of agile methodology use during a project. As a result, project managers have little guidance on how to manage teams who are using agile methodologies. Arguing that the most effective control modes are those that provide teams with autonomy in determining the methods for achieving project objectives, we propose hypotheses related to the interaction between control modes, agile methodology use, and requirements change. We test the model in a field study of 862 software developers in 110 teams. The model explains substantial variance in four objective measures of project quality—bug severity, component complexity, coordinative complexity, and dynamic complexity. Results largely support our hypotheses, highlighting the interplay between project control, agile methodology use, and requirements change. The findings contribute to extant literature by integrating control theory into the growing literature on agile methodology use and by identifying specific contingencies affecting the efficacy of different control modes. We discuss the theoretical and practical implications of our results.

Control of Flexible Software Development Under Uncertainty

Harris, M. L., Collins, R. W., Hevner, A. R. — 2009-09-20

When should software development teams have the flexibility to modify their directions and how do we balance that flexibility with controls essential to produce acceptable outcomes? We use dynamic capabilities theory and an extension of control theory to understand these questions. This work is examined in a case study. Our results demonstrate that flexibility may be needed when the starting conditions are uncertain and that effective control in these situations requires use of traditional controls plus a new type of control we term emergent outcome control.

Crossing Spatial and Temporal Boundaries in Globally Distributed Projects: A Relational Model of Coordination Delay

Cummings, J. N., Espinosa, J. A., Pickering, C. K. — 2009-09-20

In globally distributed projects, members have to deal with spatial boundaries (different cities) and temporal boundaries (different work hours) because other members are often in cities within and across time zones. For pairs of members with spatial boundaries and no temporal boundaries (those in different cities with overlapping work hours), synchronous communication technologies such as the telephone, instant messaging (IM), and Web conferencing provide a means for real-time interaction. However, for pairs of members with spatial and temporal boundaries (those in different cities with nonoverlapping work hours), asynchronous communication technologies, such as e-mail, provide a way to interact intermittently. Using survey data from 675 project members (representing 5,674 pairs of members) across 108 projects in a multinational semiconductor firm, we develop and empirically test a relational model of coordination delay. In our model, the likelihood of delay for pairs of members is a function of the spatial and temporal boundaries that separate them, as well as the communication technologies they use to coordinate their work. As expected, greater use of synchronous web conferencing reduces coordination delay for pairs of members in different cities with overlapping work hours relative to pairs of members with nonoverlapping work hours. Unexpectedly, greater use of asynchronous e-mail does not reduce coordination delay for pairs of members in different cities with nonoverlapping work hours, but rather reduces coordination delay for those with overlapping work hours. We discuss the implications of our findings that temporal boundaries are more difficult to cross with communication technologies than spatial boundaries.

Exploring Agility in Distributed Information Systems Development Teams: An Interpretive Study in an Offshoring Context

Sarker, S., Sarker, S. — 2009-09-20

Agility is increasingly being seen as an essential element underlying the effectiveness of globally distributed information systems development (ISD) teams today. However, for a variety of reasons, such teams are often unable develop and enact agility in dealing with changing situations. This paper seeks to provide a deeper understanding of agility through an intensive study of the distributed ISD experience in TECHCOM, an organization widely recognized for its excellence in IT development and use. The study reveals that agility should be viewed as a multifaceted concept having three dimensions: resource, process, and linkage. Resource agility is based on the distributed development team's access to necessary human and technological resources. Process agility pertains to the agility that originates in the team's systems development method guiding the project, its environmental scanning, and sense-making routines to anticipate possible crises, and its work practices enabling collaboration across time zones. Linkage agility arises from the nature of interactional relationships within the distributed team and with relevant project stakeholders, and is composed of cultural and communicative elements. The paper highlights some of the difficulties in developing agility in distributed ISD settings, provides actionable tactics, and suggests contingencies wherein different facets of agility may become more (or less) critical.

Research Commentary--Weighing the Benefits and Costs of Flexibility in Making Software: Toward a Contingency Theory of the Determinants of Development Process Design

Austin, R. D., Devin, L. — 2009-09-20

In recent years, flexibility has emerged as a divisive issue in discussions about the appropriate design of processes for making software. Partisans in both research and practice argue for and against plan-based (allegedly inflexible) and agile (allegedly too flexible) approaches. The stakes in this debate are high; questions raised about plan-based approaches undermine longstanding claims that those approaches, when realized, represent maturity of practice. In this commentary, we call for research programs that will move beyond partisan disagreement to a more nuanced discussion, one that takes into account both benefits and costs of flexibility. Key to such programs will be the development of a robust contingency framework for deciding when (in what conditions) plan-based and agile methods should be used. We develop a basic contingency framework in this paper, one that models the benefit/cost economics described in narratives about the transition from craft to industrial production of physical products. We use this framework to demonstrate the power of even a simple model to help us accomplish three objectives: (1) to refocus discussions about the appropriate design of software development processes, concentrating on when to use particular approaches and how they might be usefully combined; (2) to suggest and guide a trajectory of research that can support and enrich this discussion; and (3) to suggest a technology-based explanation for the emergence of agile development at this point in history. Although we are not the first to argue in favor of a contingency perspective, we show that there remain many opportunities for information systems (IS) research to have a major impact on practice in this area.

About Our Authors

2009-09-20

No abstract available.