The Role of Social Agile Practices for Direct and Indirect Communication in Information Systems Development Teams

Methods for Agile information systems development (ISD) are widely accepted in industry. One key difference in comparison to traditional, plan-driven ISD approaches is that Agile ISD teams rely heavily on direct, informal face-to-face communication instead of indirect and formal documents, models, and plans. While the importance of communication in Agile ISD is generally acknowledged, empirical studies investigating this phenomenon are scarce. We empirically open up the “black box” of the Agile ISD process to enhance the knowledge about the communication mechanisms of Agile ISD teams. We conducted a case study at two medium-sized ISD companies. As our primary data collection technique, we carried out semi-structured interviews, which we complemented with observations and, in one case, a survey. Our study’s main contribution is a set of so-called social Agile practices that positively impact the direct communication of team members. Our data suggests including the Agile practices co-located office space, daily stand-up meeting, iteration planning meeting, pair programming, sprint retrospective, and sprint review in this set. Furthermore, we investigate the role of more formal, indirect communication in Agile ISD projects. We highlight areas in which formal documents remain important so that a trade-off between indirect and direct communication is necessary

Non-Technical Individual Skills are Weakly Connected to the Maturity of Agile Practices

Context: Existing knowledge in agile software development suggests that individual competency (e.g. skills) is a critical success factor for agile projects. While assuming that technical skills are important for every kind of software development project, many researchers suggest that non-technical individual skills are especially important in agile software development. Objective: In this paper, we investigate whether non-technical individual skills can predict the use of agile practices. Method: Through creating a set of multiple linear regression models using a total of 113 participants from agile teams in six software development organizations from The Netherlands and Brazil, we analyzed the predictive power of non-technical individual skills in relation to agile practices. Results: The results show that there is surprisingly low power in using non-technical individual skills to predict (i.e. explain variance in) the mature use of agile practices in software development. Conclusions: Therefore, we conclude that looking at non-technical individual skills is not the optimal level of analysis when trying to understand, and explain, the mature use of agile practices in the software development context. We argue that it is more important to focus on the non-technical skills as a team-level capacity instead of assuring that all individuals possess such skills when understanding the use of the agile practices.Comment: 18 pages, 1 figur

Flexible Global Software Development (GSD): Antecedents of Success in Requirements Analysis

Globalization of software development has resulted in a rapid shift away from the traditional collocated, on-site development model, to the offshoring model. Emerging trends indicate an increasing interest in offshoring even in early phases like requirements analysis. Additionally, the flexibility offered by the agile development approach makes it attractive for adaptation in globally distributed software work. A question of significance then is what impacts the success of offshoring earlier phases, like requirements analysis, in a flexible and globally distributed environment? This article incorporates the stance of control theory to posit a research model that examines antecedent factors such as requirements change, facilitation by vendor and client site-coordinators, control, and computer-mediated communication. The impact of these factors on success of requirements analysis projects in a “flexible” global setting is tested using two quasi-experiments involving students from Management Development Institute, India and Marquette University, USA. Results indicate that formal modes of control significantly influence project success during requirements analysis. Further, facilitation by both client and vendor site coordinators positively impacts requirements analysis success

Control, Process Facilitation, and Requirements Change in Offshore Requirements Analysis: The Provider Perspective

Process, technology, and project factors have been increasingly driving organizations to offshore early software development phases, such as requirements analysis. This emerging trend necessitates greater control and process facilitation between client and vendor sites. The effectiveness of control and facilitation has, however, not been examined within the context of requirements analysis and change. In this study, we examine the role of control and facilitation in managing changing requirements and on success of requirements gathering in the Indian offshore software development environment. Firms found that control by client-site coordinators had a positive impact on requirements analysis success while vender site-coordinators did not have similar influence. Process facilitation by client site-coordinators affected requirements phase success indirectly through control. The study concludes with recommendations for research and practice

Agile Requirements Engineering: A systematic literature review

Nowadays, Agile Software Development (ASD) is used to cope with increasing complexity in system development. Hybrid development models, with the integration of User-Centered Design (UCD), are applied with the aim to deliver competitive products with a suitable User Experience (UX). Therefore, stakeholder and user involvement during Requirements Engineering (RE) are essential in order to establish a collaborative environment with constant feedback loops. The aim of this study is to capture the current state of the art of the literature related to Agile RE with focus on stakeholder and user involvement. In particular, we investigate what approaches exist to involve stakeholder in the process, which methodologies are commonly used to present the user perspective and how requirements management is been carried out. We conduct a Systematic Literature Review (SLR) with an extensive quality assessment of the included studies. We identified 27 relevant papers. After analyzing them in detail, we derive deep insights to the following aspects of Agile RE: stakeholder and user involvement, data gathering, user perspective, integrated methodologies, shared understanding, artifacts, documentation and Non-Functional Requirements (NFR). Agile RE is a complex research field with cross-functional influences. This study will contribute to the software development body of knowledge by assessing the involvement of stakeholder and user in Agile RE, providing methodologies that make ASD more human-centric and giving an overview of requirements management in ASD.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED

IT-Enabled Service Innovation—A Field Study of Agile Approaches to Value Co-Creation

Service organizations need to respond rapidly to both changes in the market and customer expectations. One way of accomplishing this is through service innovation enacted to achieve competitive advantage. This study applies a service-dominant logic (SDL) lens to describe how a service organization may achieve service innovation through value co-creation that is facilitated by agile distributed methods. Literature on value co-creation is somewhat limited; although a few studies have provided guidance on what is needed to achieve value co-creation, no study has yet presented how this might be achieved. Therefore, using a single-site case study in the context of a large service organization, this study examines how value is co-created and the role that agile distributed methods play in this process. This research seeks to contribute to practice by providing service organizations with recommendations for achieving value co-creation. It contributes to theory by advancing our understanding of value co-creation processes; moreover, by using the context of an SDL, it presents a framework that maps elements of service innovation to agile distributed practices

Too Drained from Being Agile? The Self-Regulatory Effects of the Use of Agile ISD Practices and their Consequences on Turnover Intention

While much is known about the beneficial effects of agile information systems development (ISD), scholars have largely neglected to address its potential downsides. Specifically, research on this topic has thus far overlooked the ambivalent implications of the specific demands placed on developers working in agile ISD teams, including potentially depleting effects. Drawing on ego depletion theory and the associated literature, we provide a more balanced view and introduce self-regulatory resource depletion triggered by using agile ISD practices—encompassing software development (SD) and project management (PM) practices—as a theoretical perspective on why agile developers experience different levels of work-related fatigue that lead to stronger or weaker turnover intentions. Furthermore, we propose that due to the specific way in which agile ISD methods organize ISD project work, developers’ perceived workload influences the intensity by which agile ISD practices affect self-regulatory resources and developers’ feelings of fatigue. We examined our research model using a multimethod approach including quantitative and qualitative data. We found that the use of agile SD practices enhances developers’ self-regulatory resources and reduces fatigue and turnover intention. Our results also show that perceived workload strengthens the energizing effects of the use of agile SD practices and reveals a depleting effect of the use of agile PM practices, with countervailing implications for turnover intention. This study contributes to agile ISD literature by drawing a more nuanced and balanced picture with both resource-enhancing and resource-draining effects of the use of agile ISD practices. Finally, we give managerial advice regarding factors to consider when designing and managing agile ISD projects

When Agile Means Staying: A Moderated Mediated Model

The design of software development methods focuses on improving task processes, including accommodating changing user requirements and accelerating product delivery. However, there is limited research on how the use of different software development methods impacts IT professionals’ perceptions of organizational mobility. Drawing on concepts from the agile development literature and job characteristics theory, we formulate a moderated mediation model explicating the mechanism and the condition under which agile development use exerts an influence on IT professionals’ intention to stay with their current employer. Specifically, we examine job satisfaction as mediating the effect of using agile development on the intention to stay as well as how the strength of the mediated relationship differs across firms. We test our hypotheses using a sample of 32,389 software developers. We find that job satisfaction fully mediates the effect of using agile development on the intention to stay. The strength of the mediation effect is significantly different for large and small firms