Risks and risk mitigation in global software development: A tertiary study

Verner, June M.; Brereton, O. P.; Kitchenham, Barbara; Turner, Mark; Niazi, Mahmood

doi:10.1016/j.infsof.2013.06.005

Cited by 127 publications

(155 citation statements)

References 42 publications

Supporting

Mentioning

148

Contrasting

Unclassified

Order By: Relevance

“…Another systematic literature review was done by Verner et al, who reported the risks of GSD collaboration with some mitigation recommendations structured into 12 areas starting from vendor selection and requirements engineering and finishing with coordination and control areas [7].Šmite et al conducted a systematic literature review of GSD experiences and came up with seven most commonly discussed practices that are aimed at overcoming GSD problems [8]. Mettovaara et al performed interviews at Nokia and Philips and identified 10 common problems and 11 success factors based on the experiences in interorganizational collaborations in the two studied companies [25].…”

Section: Related Workmentioning

confidence: 99%

“…We have decided to analyze four key SLRs related to setting up GSD collaborations as a starting point [5][6][7][8]. These SLRs aggregate already existing knowledge with respect to topics such as risks, mitigation solutions, and strategies.…”

Section: Related Workmentioning

confidence: 99%

“…Based on the inputs from the industrial partner, we have identified and focused on three possible scenarios for launching GSD collaboration named O↵shore outsourcing, O↵shore insourcing and Innovative o↵shoring [5,7,19,29]. O↵shore outsourcing refers to consuming of resources and development services from an external 3rd party that is located in a di↵erent country, often representing client-subcontractor relationships [5].…”

Section: Strategymentioning

confidence: 99%

“…The following recommended steps that organizations should follow at the beginning of setting up global collaborations are the investigation of the foreign legal system regarding contract and IP laws; the selection of a suitable vendor with desired expertise, e cient capabilities and su cient technological infrastructure; and the planning of financial budget for collaboration including possible risks and therefore hidden costs [7]. One of the main motivations for performing GSD collaborations by the company could be cost savings, therefore financial planning should be considered early on [7].…”

Section: Strategymentioning

confidence: 99%

“…One of the main motivations for performing GSD collaborations by the company could be cost savings, therefore financial planning should be considered early on [7].…”

Section: Strategymentioning

confidence: 99%

See 4 more Smart Citations

A Canvas for Establishing Global Software Development Collaborations

Smirnova

Münch

Stupperich

2014

Communications in Computer and Information Science

View full text Add to dashboard Cite

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Strategymentioning

confidence: 99%

Section: Strategymentioning

confidence: 99%

“…One of the main motivations for performing GSD collaborations by the company could be cost savings, therefore financial planning should be considered early on [7].…”

Section: Strategymentioning

confidence: 99%

See 3 more Smart Citations

A Canvas for Establishing Global Software Development Collaborations

Smirnova

Münch

Stupperich

2014

Communications in Computer and Information Science

View full text Add to dashboard Cite

A conceptual framework of challenges and solutions for managing global software maintenance

Ulziit¹,

Warraich²,

Gencel

et al. 2015

J Software Evolu Process

View full text Add to dashboard Cite

Context: Software maintenance process in globally distributed settings brings significant management challenges to software organizations. Objectives: Investigate the factors specific to managing software maintenance process in globally distributed settings and best practices in software organizations.Method: A systematic literature review and interviews with industry practitioners were conducted. For analysis and synthesis, the grounded theory method was used. Results:We identified a number of management challenges and mitigation strategies and then classified them under people, process, product, and technology factors. Overall, a structure of challenges and solutions, the conceptual framework, has been developed that may be used to understand and classify global maintenance challenges.Conclusions: Distributed software maintenance process has specific management challenges in relation to process, people, product, and technology. Therefore, companies performing maintenance in distributed settings should consider these factors, which are not present in the general global software development literature, although many lessons apply to both.

show abstract

Software integration in global software development: Challenges for GSD vendors

Ilyas

Khan

2017

J Softw Evol Proc

View full text Add to dashboard Cite

Context The advances in information and communication technologies have revolutionized the software development environment from local to global software development (GSD). This revolution also created challenges for vendor organizations. Vendors face challenges in integrating the components developed independently by GSD teams into a final working product. Objective The objectives of the current study is to find out those critical barriers/challenges that hinder the integration process at any stage in the GSD environment for different types and size of projects. Methodology For achieving the objectives we initially conducted a comprehensive systematic literature review (SLR). We searched 6 digital libraries and also followed the snowballing technique. The data was extracted from a total of 88 finally selected papers. Findings of the SLR study were then empirically validated through a questionnaire survey in GSD industry. A total of 96 experts from 22 different countries participated in the survey. Results We have found a total of 16 barriers/challenges among which ten barriers are ranked as critical barriers/challenges. Some of the top ranked barriers are “lack of communication,” “lack of proper documentation,” “lack of compatibility,” and “architecture mismatch.” The findings of our industrial survey are mostly coherent with the SLR findings. However, there is a difference in ranks of the various barriers/challenges across the 2 data sets (SLR and industrial survey). The identified challenges need to be properly addressed by software vendors to reduce the complexity of the integration process in GSD projects. Conclusion We found that the severity of these barriers increases in large size projects. On the other hand, bespoke products are more affected by “lack of communication,” while off‐the‐shelf–based projects face integration problems due to “lack of compatibility,” “architecture mismatch,” and “wrong off the shelf product selection and customization”.

show abstract

Risks and risk mitigation in global software development: A tertiary study

Cited by 127 publications

References 42 publications

A Canvas for Establishing Global Software Development Collaborations

A Canvas for Establishing Global Software Development Collaborations

A conceptual framework of challenges and solutions for managing global software maintenance

Software integration in global software development: Challenges for GSD vendors

Contact Info

Product

Resources

About