Investigating an ‘Agile-Rigid’ Approach in Globally Distributed Requirements Analysis

The global software development environment brings with itself abundant business opportunities as well as challenges in terms of coordination, communication and control. Recent years have also witnessed the growth of the agile movement. To address the global software development challenges there is a need to combine the flexibility offered by the growing agile development approaches with the rigidity offered by the traditional plan-based approaches. This paper reports an exploratory quasi-experimental study, which investigates the performance of requirements analysis projects in an ‘agile-rigid’ distributed environment. The study yields several interesting conclusions that can assist organizations in managing their global software projects more effectively. Our experiment indicates that project monitoring and control, project communication, and process facilitation between peer teams significantly influence the success of such projects. Creation of an agile-rigid environment can help organizations mitigate various risks inherent in globally distributed software development

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

An Evolutionary Perspective on Control in IS Development Projects

Projects in the field of Information Systems Development (ISD) are particularly prone to failure because they are complex in many respects. To increase success of ISD projects, researchers and practitioners usually recommend the implementation of control. The traditional view on control involves two parties: a controller executing control and one or more controllees being controlled. To better understand why control effectiveness has not significantly improved over the last decades, this paper gives a chronological overview of existing literature on ISD project control. We find that so far, research has been strongly focusing on controller related aspects such as the creation of control portfolios. This, however, neglects that the effectiveness of control is highly dependent on the controllees’ perception and willingness to actively commit to implemented controls. We argue that a more holistic understanding of the controllee perspective on control is needed and discuss implications for theory and practic

Considerations for Effective Requirements Analysis in Offshore Software Development Projects: Lessons from Multi-method Research

Offshore software development using geographically distributed teams is an accepted practice in software development today. However, software development companies have largely only offshored the software development lifecycle’s coding and testing phases. However, lately, offshoring the requirements analysis (RA) phase has become increasingly viable for several reasons including the software industry’s maturation and improved communication technologies. However, successfully evaluating this highly interactive phase between geographically dispersed client and provider teams requires special considerations. In this paper, we present practical insights garnered from conducting experiments and surveys of IS professionals from the Indian software industry and from extensively examining the literature. Our findings confirm that, subject to certain best practices, one can effectively conduct RA in software projects offshore. We present these practices as lessons learned and provide related recommendations for industry and academia

Enterprise Agility: Why Is Transformation so Hard?

Enterprise agility requires capabilities to transform, sense and seize new business opportunities more quickly than competitors. However, acquiring those capabilities, such as continuous delivery and scaling agility to product programmes, portfolios and business models, is challenging in many organisations. This paper introduces definitions of enterprise agility involving business management and cultural lenses for analysing large-scale agile transformation. The case organisation, in the higher education domain, leverages collaborative discovery sprints and an experimental programme to enable a bottom-up approach to transformation. Meanwhile the prevalence of bureaucracy and organisational silos are often contradictory to agile principles and values. The case study results identify transformation challenges based on observations from a five-month research period. Initial findings indicate that increased focus on organisational culture and leveraging of both bottom-up innovation and supportive top-down leadership activities, could enhance the likelihood of a successful transformation

Coordination in Distributed Agile Software Development: A Systematic Review

In order to decrease the consumer return transaction cost, e-commerce platform Alibaba invited an insurance company to develop a new type of insurance to compensate consumers for returns, which is called return-freight insurance. The new insurance has resulted in online return\u27s explosive growth. However, some online retailers still choose to offer complimentary return-freight insurance to signal their products\u27 quality. Using signaling theory, we build a conceptual economic model to explore what kind of online retailer should adopt this strategy under incomplete information. Based on the fact that each product\u27s return probability, profit, and insurance compensation are different, our main results show the separating equilibria, where only high-quality online retailers will offer complimentary return-freight insurance. Interestingly, return-freight insurance profit and compensation play different roles in the signal effect. The insurance premium plays a deep role while the compensation plays at the surface, because consumers could only observe the compensation when purchasing

Software Engineers' Information Seeking Behavior in Change Impact Analysis - An Interview Study

Software engineers working in large projects must navigate complex information landscapes. Change Impact Analysis (CIA) is a task that relies on engineers' successful information seeking in databases storing, e.g., source code, requirements, design descriptions, and test case specifications. Several previous approaches to support information seeking are task-specific, thus understanding engineers' seeking behavior in specific tasks is fundamental. We present an industrial case study on how engineers seek information in CIA, with a particular focus on traceability and development artifacts that are not source code. We show that engineers have different information seeking behavior, and that some do not consider traceability particularly useful when conducting CIA. Furthermore, we observe a tendency for engineers to prefer less rigid types of support rather than formal approaches, i.e., engineers value support that allows flexibility in how to practically conduct CIA. Finally, due to diverse information seeking behavior, we argue that future CIA support should embrace individual preferences to identify change impact by empowering several seeking alternatives, including searching, browsing, and tracing.Comment: Accepted for publication in the proceedings of the 25th International Conference on Program Comprehensio

A measurement model to analyze the effect of agile enterprise architecture on geographically distributed agile development.

Abstract Efficient and effective communication (active communication) among stakeholders is thought to be central to agile development. However, in geographically distributed agile development (GDAD) environments, it can be difficult to achieve active communication among distributed teams due to challenges such as differences in proximity and time. To date, there is little empirical evidence about how active communication can be established to enhance GDAD performance. To address this knowledge gap, we develop and evaluate a measurement model to quantitatively analyze the impact of agile enterprise architecture (AEA) on GDAD communication and GDAD performance. The measurement model was developed and evaluated through developing the AEA driven GDAD model and associated measurement model based on the extensive literature review, model pre-testing, pilot testing, item screening, and empirical evaluation through a web-based quantitative questionnaire that contained 26 different weighted questions related to the model constructs (AEA, GDAD active communication, and GDAD performance). The measurement model evaluation resulted in validated research model and 26 measures: 7 formative items for AEA, 5 reflective items for communication efficiency, 4 reflective items for communication effectiveness, 2 reflective items for each on-time and on-budget completion, and 3 reflective items for each software functionality and quality. The results indicate the appropriateness and applicability of the proposed measurement model to quantitatively analyze the impact of AEA on GDAD communication and performance