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

Customising software products in distributed software development a model for allocating customisation requirements across organisational boundaries

Requirements engineering plays a vital role in the software development process. While it is difficult to manage those requirements locally, it is even more difficult to communicate those requirements over organisational boundaries and to convey them to multiple distribution customers. This paper discusses the requirements of multiple distribution customers empirically in the context of customised software products. The main purpose is to understand the challenges of communicating and allocating customisation requirements across distributed organisational boundaries. We conducted an empirical survey with 19 practitioners, which confirmed that communicating customisation requirements in a DSD context is a significant challenge. We therefore propose a model for allocating customisation requirements between a local, customer-based agile team and a distributed development team that uses a traditional development approach. Our conjecture is that the model would reduce the challenge of communicating requirements across organisational boundaries, address customers’ requirements and provide a focus for future empirical studies

Agile Methodology In Offshore Outsourcing

Firms have to be cognizant of appropriate methods to deploy when managing offshore outsourcing.  As industry continues to deploy agile methodology, such methodology may not be the best approach in offshore outsourcing.  Managers may benefit from more disciplined application development methodologies.  The case study examines risk factors of offshore outsourcing of software projects and the appropriateness of agile methodologies in these projects. The findings contribute important insight into the benefits and limitations of agile methods in offshore outsourcing

Model of Critical Factors for Outsourcing Agile Development

Companies are beginning to combine outsourcing with Agile software engineering techniques with the goal of receiving the benefits of both – faster time to market, greater quality, and smaller costs. Since Agile was originally developed to work principally with small collocated teams, scalability of Agile to the enterprise, and simultaneous use of Agile and outsourcing are questions concerning applicability of Agile techniques to global business environments. This paper first summarizes current experience studies and research in Agile, enterprise Agile and Agile outsourcing, to identify factors likely to affect success on Agile projects. It then extends a model originally developed by Chow and Cao (2007) to account for these factors. Finally it outlines an experiment whose goal is to determine which of these factors drives successful projects that use both Agile and outsourcing

Scrum master activities : process tailoring in large enterprise projects

This paper explores practitioner descriptions of agile method tailoring in large-scale offshore or outsourced enterprise projects. Specifically, tailoring of the scrum master role is investigated. The scrum master acts as a facilitator for software development teams, nurturing adherence to agile practices and removing impediments for team members. But in large projects, scrum masters often work together in geographically distributed teams. Scrum masters use sprint planning to avoid development tasks that overlap team boundaries, coordinate status and effort across teams, and integrate code bases. The study comprises 8 international companies in London, Bangalore and Delhi. Interviews with 46 practitioners were conducted between February 2010 and May 2012. A grounded theory research method was used to identify that the scrum master role comprises six activities: process anchor, stand-up facilitator, impediment remover, sprint planner, scrum of scrums facilitator, and integration anchor. This systematic description of activities in scrum master teams extends our understanding of practitioner perspectives on agile process tailoring in large enterprises. Understanding these activities will help coaches guide large scale agile teams