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

A reactive architecture for cloud-based system engineering

PhD ThesisSoftware system engineering is increasingly practised over globally distributed locations. Such a practise is termed as Global Software Development (GSD). GSD has become a business necessity mainly because of the scarcity of resources, cost, and the need to locate development closer to the customers. GSD is highly dependent on requirements management, but system requirements continuously change. Poorly managed change in requirements affects the overall cost, schedule and quality of GSD projects. It is particularly challenging to manage and trace such changes, and hence we require a rigorous requirement change management (RCM) process. RCM is not trivial in collocated software development; and with the presence of geographical, cultural, social and temporal factors, it makes RCM profoundly difficult for GSD. Existing RCM methods do not take into consideration these issues faced in GSD. Considering the state-of-the-art in RCM, design and analysis of architecture, and cloud accountability, this work contributes: 1. an alternative and novel mechanism for effective information and knowledge-sharing towards RCM and traceability. 2. a novel methodology for the design and analysis of small-to-medium size cloud-based systems, with a particular focus on the trade-off of quality attributes. 3. a dependable framework that facilitates the RCM and traceability method for cloud-based system engineering. 4. a novel methodology for assuring cloud accountability in terms of dependability. 5. a cloud-based framework to facilitate the cloud accountability methodology. The results show a traceable RCM linkage between system engineering processes and stakeholder requirements for cloud-based GSD projects, which is better than existing approaches. Also, the results show an improved dependability assurance of systems interfacing with the unpredictable cloud environment. We reach the conclusion that RCM with a clear focus on traceability, which is then facilitated by a dependable framework, improves the chance of developing a cloud-based GSD project successfully

Introducing Team Coordination Framework to Support Globally Distributed Teams for Pakistani Software Industry

Collaborative effort is required in DSD (Distributed Software Development) in order to develop software in manageable components. Immense effort is taking place due to the cultural, geographical and temporal distances among project teams in Pakistani Software Industry to this end. The purpose of this study is to propose a solution during DSD that will help the distributed teams in coordinating their activities. Our solution enhances the management associated activities and assists in optimal usage of team coordination in dispersed settings. The method that we used is single case study type, which involved distributed software business to assess the usefulness and efficiency related to Pakistan’s DSD industries, and has shown strong tendency of participants towards the effectiveness of proposed team coordination framework. Results indicate that the predictable solution will look up the group management, which is considered as a vigorous issue of Pakistani DSD industry. Furthermore, it will assist in resolving the problems of team coordination in distributed situation. One of the most significant current discussion about the proposed solution suggested that it helps in human communication methods team coordination in a distributed environment

Managing risks in virtual-agile it projects: The paradigm of responsiveness

Managing risks in IT projects has always been a critical area of study for many researchers and practitioners. Due to the rapid advances in information and communication technologies (ICTs), there is an increasing number of challenges and issues for the IT organisations. Virtual-Agile IT projects being virtually operated and based on Agile methodology principles are facilitating IT industry having their main application in the software development industry, where entities from diverse backgrounds have varied working practices, languages and culture, and works together for achieving common aims. There have been several benefits integrated with the application of Virtual-Agile IT projects but the intersection of these two unique working concepts (Virtual-Agile) gives rise to several risks and uncertainties which have now become a point of concern for these organisations. The need for minimising the possibility of such evolving risks and uncertainties became the foundation of conducting this study from a theoretical viewpoint, where the researcher aimed to propose a conceptual framework helping organisations meet their business objectives constructively. The study is exploratory in nature which discovers all those appropriate practices, strategies and guidelines which support reducing risk and uncertainties between the distributed stakeholders during the product development phase. The research methodology used is primarily dependent on qualitative methods combined with the grounded theory methodology to gather rich and rigorous information from experienced and professional personnel from different geographical regions. Depending upon the procedures of grounded theory methodology, the data were collected and analysed simultaneously under the principles of constant comparison and theoretical sampling. The procedures helped to determine thought-provoking results and highlighted various dimensions of the phenomenon under investigation. Responsiveness which emerged as the central phenomenon to overcome risks and uncertainties in Virtual-Agile IT project environments proposes for a proactive system which could be able to deal with project uncertainties, thus reducing the likelihood of potential risks, and enhancing opportunities for the organisations. Responsiveness, which is an ability of the system to perceive, reflect and adapt changes in the project environments is dependent upon efficiently management of three major components, i.e. technology, timeliness and communication. Technology which is the most critical element when operating in virtual environments requires standardization and should be extensively used to develop strong networks and integration between various locations around the world. Timeliness is elementary and a pre-requisite for completion of on-going multiple projects in IT organisations Communication which is the utmost component, is required at various levels for evolving synchronisation in the overall system, such as when developing correlation and satisfaction among distributed stakeholders, estimating the level of required competency and ensuring an efficient knowledge transfer process. Responsiveness, which is required throughout the development cycle, also further influences formal risk management practices undertaken at various levels of the project. Risk management planning and implementation of the response strategies are dependent upon Responsiveness i.e. how well, timely and using technical resources the entities communicate for determining a solution to a problem. The paradigm developed, thus reflects industrial practices undertaken in the software development industry to meet project objectives and would support organisations and their prominent stakeholders to overcome risks and uncertainties in the future Virtual-Agile IT projects

Strategies to Control Internal Factors Affecting Information Systems Projects in Puerto Rico

Many project managers and business leaders lack effective strategies to control internal factors that affect information systems (IS) projects, which may impede leadership\u27s ability to respond to market changes. The purpose of this multiple case study was to explore strategies used by 6 purposefully selected project managers who successfully implemented information system development (ISD) projects by controlling the internal factors that affected different ISD project phases in Puerto Rico\u27s telecommunication service industry. The framework that guided this study was coordination theory. The data collection process included semistructured interviews and project documentation including business requirements, project charters, project plans, and lessons learned which also served as resources for member checking and validation to strengthen the trustworthiness of the study. Analysis of the data occurred following Yin\u27s 5 analytical steps of validating, coding, interpreting, summarizing, and generating themes. The 5 themes that emerged were top management support, clear requirements, communication, project plan, and lessons learned. Each theme corresponded to a phase of the project life cycle. Top management support and clear requirements were the top critical factors (TCF) in the initiating and planning phases. Communication and project plan were the TCF in the executing, monitoring, and controlling phases. Lessons learned were the TCF in the closing phase of the project. Implications for social change include helping IS project managers successfully implement IS projects, providing innovative services to customers, and improving an organization\u27s position so it can provide jobs and economic stability in the region in which it operates

Understanding Agile Software Development Assimilation Beyond Acceptance

Agile software development methods represent a departure from the heavily regimented and document-driven procedures of traditional, waterfall approaches. Despite the highly touted benefits of employing agile ISD methods and the growth of agile adoption rates over the past two decades, it is not clear why some organizations fail to routinize agile methods, while others do so and realize their promised benefits. Motivated by the need to understand the factors that influence agile routinization, this study empirically examines the deep contextual factors that impact the extent to which agile methods are proliferated throughout an organization. Findings indicate that project success from initial agile use does not translate to routine agile use. Instead, findings from the study suggest that organizational factors of organizational culture and structure play a pivotal role in the routinization of agile methods

WeDRisk :an approach to managing web and distributed software development risks

PhD ThesisWeb and distributed software developments are risky and face speci c challenges like time zone and cultural di erences. These challenges have resulted in new risks and risk management needs. In this thesis, a systematic review of existing software risk management approaches was conducted to investigate their ability to satisfy the risk management needs of web and distributed developments. The review identi es a number of weaknesses in existing approaches. Examples are the lack of consideration for web and distributed factors and lack of preparation for atypical risks. A new approach called WeDRisk is introduced to manage the risks from project, process and product perspectives. The WeDRisk approach addresses the weaknesses of existing approaches to risk management, which are less able to deal with the speci c challenges of web and distributed develop- ment. A key part of the approach is exibility to deal with the rapid evolution which is typical of such developments. This exibility is achieved by customiz- ing the risk management and providing a method for coping with atypical risks. WeDRisk also provides an improved risk estimation equation to consider web and distributed factors. The novel aspects of the WeDRisk approach were subjected to a series of evaluation cycles, including peer review, two controlled experiments, expert evaluation and a case study. In addition to a number of improvement sug- gestions, the evaluation results illustrate how WeDRisk is useful, understandable, exible, easy to use, and able to satisfy many web and distributed development risk management needs.Industrial Research Centre and Libyan government-Higher Ed- ucation for the scholarship