Metrics Based on a Risk-Driven Approach to Assess Communication, Cooperation and Coordination in Global Software Development Teams
DOI:
https://doi.org/10.19053/01211129.v29.n54.2020.11759Keywords:
communication, cooperation and coordination (3Cs), global software development (GSD), goal question metric (GQM) method, metrics in the GSD, risks in the GSDAbstract
The success of Global Software Development (GSD) depends largely on how geographically dispersed project management and teamwork efforts are communicated, cooperated and coordinated (3Cs). From a literature analysis, some works were found where risks and metrics for DGS projects are proposed, but it was evidenced that some risks are not described in detail, they are ambiguous and hard to understand, which makes it difficult to know which category they belong to. In addition, it is necessary to classify risks in a less-subjective way, which allows to improve their understanding and thus define and apply measurement tools to obtain the impact magnitude of mentioned risks, and generate some indicators for support decision-making in DGS teams. In this article, 37 risks for the communication, cooperation and coordination in the DGS are proposed, as a result of the comparison and integration of identified risks in the literature. A set of metrics defined with the application of the Goal Question Metric (GQM) paradigm is also presented, organized according to these questions: What does it measure? Where the attribute to be measured is established; How to measure it? Where the metric is formulated through the following elements: description, type, scale and calculation function. Through the focus group technique, its completeness, relevance, clarity, precision, and ease of use were evaluated. The proposed metrics could be useful for organizations, teams, projects, and consultants operating in DGS contexts.
Downloads
References
[2] L. Layman, L. Williams, D. Damian, and H. Bures, “Essential communication practices for Extreme Programming in a global software development team,” Information and Software Technology, vol. 48 (9), pp. 781-794, 2006. https://doi.org/10.1016/j.infsof.2006.01.004
[3] J. Campo, P. Francisco, A. Carlos, and C. Pardo, “Modelo de procesos en el desarrollo de software global,” Ingenium, vol. 9 (23), pp. 17-26, 2015.
[4] J. S. Persson, L. Mathiassen, J. Boeg, T. S. Madsen, and F. Steinson, “Managing risks in distributed software projects: An integrative framework,” IEEE Transactions on Engineering Management, vol. 56 (3), pp. 508-532, 2009. https://doi.org/10.1109/TEM.2009.2013827
[5] J. S. Persson, and L. Mathiassen, “A process for managing risk in Distributed teams,” IEEE Software, vol. 27 (1), pp. 20-29, 2011. https://doi.org/10.1109/MS.2009.157
[6] M. Tihinen, R. Kommeren, D. Systems, J. Rotherham, and P. M. Office, “Metrics and Measurements in Global Software Development,” International Journal on Advances in Software, vol. 5 (3), pp. 278-292, 2012.
[7] Q. Khan, and S. Ghayyur, “Software risks and mitigation in global software development,” Journal of Theoretical and Applied Information Technology, vol. 22 (1), pp. 58-69, 2010.
[8] H. Fuks, A. Raposo, M. Gerosa, and M. Pimental, "The 3C Collaboration Model," In Encyclopedia of E-Collaboration, 2008, pp. 637-644. https://doi.org/10.4018/978-1-59904-000-4.ch097
[9] R. Van Solingen (Revision), V. Basili (Original article, 1994), G. Caldiera (Original article, 1994), and H. D. Rombach (Original article, 1994), "Goal Question Metric (GQM) Approach," In Encyclopedia of Software Engineering, 2002. https://doi.org/10.1002/0471028959.sof142
[10] A. Mathrani, and S. Mathrani, “Test strategies in distributed software development environments,” Computers in Industry, vol. 64 (1), pp. 1-9, 2013. https://doi.org/10.1016/j.compind.2012.09.002
[11] I. Steinmacher, A. Paula, and C. Steinmacher, “Awareness Support in Global Software Development: A Systematic Review Based on the 3C Collaboration Model Conference,” In Collaboration and Technology. CRIWG 2010. Lecture Notes in Computer Science, 2010. https://doi.org/10.1007/978-3-642-15714-1_15
[12] M. Wanderley, J. Menezes, C. Gusmão, and F. Lima, “Proposal of Risk Management Metrics for Multiple Project Software Development,” Procedia Computer Science, vol. 64, pp. 1001-1009, 2015. https://doi.org/10.1016/j.procs.2015.08.619
[13] P. Björndal, K. Smiley, and P. Mohapatra, “Global Software Project Management: A Case Study BT - Software Engineering Approaches for Offshore and Outsourced Development,” In International Conference on Software Engineering Approaches for Offshore and Outsourced Development, 2010. https://doi.org/10.1007/978-3-642-13784-6_7
[14] J. Noll, and S. Beecham, “Measuring global distance: A survey of distance factors and interventions,” In Software Process Improvement and Capability Determination. SPICE 2016. Communications in Computer and Information Science, 2016. https://doi.org/10.1007/978-3-319-38980-6_17
[15] I. Nurdiani, R. Jabangwe, D. Šmite, and D. Damian, “Risk Identification and Risk Mitigation Instruments for Global Software Development: Systematic Review and Survey Results,” In IEEE Sixth International Conference on Global Software Engineering Workshop, 2011. https://doi.org/10.1109/ICGSE-W.2011.16
[16] A. A. Khan, Communication Risk Framework in Global Software Development: Empirical Study in GSD Industry. Saarbrücken, Germany: LAP LAMBERT Academic Publishing, 2014.
[17] A. Khan, S. Basri, and P. Dominic, “Communication risks in GSD during RCM: Results from SLR,” In International Conference on Computer and Information Sciences, 2014. https://doi.org/10.1109/ICCOINS.2014.6868448
[18] J. M. Verner, O. P. Brereton, B. A. Kitchenham, M. Turner, and M. Niazi, “Risks and risk mitigation in global software development: A tertiary study,” Information and Software Technology, vol. 56 (1), pp. 54-78, 2014. https://doi.org/10.1016/j.infsof.2013.06.005
[19] A. A. Khan, J. Keung, M. Niazi, S. Hussain, and A. Ahmad, “Systematic literature review and empirical investigation of barriers to process improvement in global software development: Client–vendor perspective,” Information and Software Technology, vol. 87, pp. 180-205, 2017. https://doi.org/10.1016/j.infsof.2017.03.006
[20] A. Iqbal, and S. S. Abbas, Communication Risks and Best practices in Global Software Development, Sweden: Blekinge Institute of Technology, 2011.
[21] R. Jabangwe, and I. Nurdiani, Global Software Development Challenges and Mitigation Strategies A Systematic Review and Survey Results, Sweden: Blekinge Institute of Technology, 2010.
[22] C. Vega Lebrun, L. S. Rivera Prieto, and A. Garcia Santillan, Mejores Prácticas Para El Establecimiento y Aseguramiento de la Calidad del Software, 2008.
[23] J. Kontio, J. Bragge, and L. Lehtola, “The Focus Group Method as an Empirical Tool in Software Engineering,” In Guide to Advanced Empirical Software Engineering, F. Shull, J. Singer, and D. I. K. Sjøberg, Eds. London: Springer London, 2008, pp. 93-116. https://doi.org/10.1007/978-1-84800-044-5_4
Downloads
Published
How to Cite
Issue
Section
License
All articles included in the Revista Facultad de Ingeniería are published under the Creative Commons (BY) license.
Authors must complete, sign, and submit the Review and Publication Authorization Form of the manuscript provided by the Journal; this form should contain all the originality and copyright information of the manuscript.
The authors who publish in this Journal accept the following conditions:
a. The authors retain the copyright and transfer the right of the first publication to the journal, with the work registered under the Creative Commons attribution license, which allows third parties to use what is published as long as they mention the authorship of the work and the first publication in this Journal.
b. Authors can make other independent and additional contractual agreements for the non-exclusive distribution of the version of the article published in this journal (eg, include it in an institutional repository or publish it in a book) provided they clearly indicate that the work It was first published in this Journal.
c. Authors are allowed and recommended to publish their work on the Internet (for example on institutional or personal pages) before and during the process.
review and publication, as it can lead to productive exchanges and a greater and faster dissemination of published work.
d. The Journal authorizes the total or partial reproduction of the content of the publication, as long as the source is cited, that is, the name of the Journal, name of the author (s), year, volume, publication number and pages of the article.
e. The ideas and statements issued by the authors are their responsibility and in no case bind the Journal.
