There is an emerging interest in using agile methodologies in Global Software Development(GSD)to get the mutual benefits of both methods.Scrum is currently admired by many development teams as an agile most known meth...There is an emerging interest in using agile methodologies in Global Software Development(GSD)to get the mutual benefits of both methods.Scrum is currently admired by many development teams as an agile most known meth-odology and considered adequate for collocated teams.At the same time,stake-holders in GSD are dispersed by geographical,temporal,and socio-cultural distances.Due to the controversial nature of Scrum and GSD,many significant challenges arise that might restrict the use of Scrum in GSD.We conducted a Sys-tematic Literature Review(SLR)by following Kitchenham guidelines to identify the challenges that limit the use of Scrum in GSD and to explore the mitigation strategies adopted by practitioners to resolve the challenges.To validate our reviewfindings,we conducted an industrial survey of 305 practitioners.The results of our study are consolidated into a research framework.The framework represents current best practices and recommendations to mitigate the identified distributed scrum challenges and is validated byfive experts of distributed Scrum.Results of the expert review were found supportive,reflecting that the framework will help the stakeholders deliver sustainable products by effectively mitigating the identified challenges.展开更多
Requirements elicitation is a fundamental phase of software development in which an analyst discovers the needs of different stakeholders and transforms them into requirements.This phase is cost-and time-intensive,and...Requirements elicitation is a fundamental phase of software development in which an analyst discovers the needs of different stakeholders and transforms them into requirements.This phase is cost-and time-intensive,and a project may fail if there are excessive costs and schedule overruns.COVID-19 has affected the software industry by reducing interactions between developers and customers.Such a lack of interaction is a key reason for the failure of software projects.Projects can also fail when customers do not know precisely what they want.Furthermore,selecting the unsuitable elicitation technique can also cause project failure.The present study,therefore,aimed to identify which requirements elicitation technique is the most cost-effective for large-scale projects when time to market is a critical issue or when the customer is not available.To that end,we conducted a systematic literature review on requirements elicitation techniques.Most primary studies identified introspection as the best technique,followed by survey and brainstorming.This finding suggests that introspection should be the first choice of elicitation technique,especially when the customer is not available or the project has strict time and cost constraints.Moreover,introspection should also be used as the starting point in the elicitation process of a large-scale project,and all known requirements should be elicited using this technique.展开更多
基金The authors extend their appreciation to the Deanship of Scientific Research at King Saud University for funding this work through research group no.RG-1441-490.
文摘There is an emerging interest in using agile methodologies in Global Software Development(GSD)to get the mutual benefits of both methods.Scrum is currently admired by many development teams as an agile most known meth-odology and considered adequate for collocated teams.At the same time,stake-holders in GSD are dispersed by geographical,temporal,and socio-cultural distances.Due to the controversial nature of Scrum and GSD,many significant challenges arise that might restrict the use of Scrum in GSD.We conducted a Sys-tematic Literature Review(SLR)by following Kitchenham guidelines to identify the challenges that limit the use of Scrum in GSD and to explore the mitigation strategies adopted by practitioners to resolve the challenges.To validate our reviewfindings,we conducted an industrial survey of 305 practitioners.The results of our study are consolidated into a research framework.The framework represents current best practices and recommendations to mitigate the identified distributed scrum challenges and is validated byfive experts of distributed Scrum.Results of the expert review were found supportive,reflecting that the framework will help the stakeholders deliver sustainable products by effectively mitigating the identified challenges.
基金funding this work through research group no.RG-1441-490.
文摘Requirements elicitation is a fundamental phase of software development in which an analyst discovers the needs of different stakeholders and transforms them into requirements.This phase is cost-and time-intensive,and a project may fail if there are excessive costs and schedule overruns.COVID-19 has affected the software industry by reducing interactions between developers and customers.Such a lack of interaction is a key reason for the failure of software projects.Projects can also fail when customers do not know precisely what they want.Furthermore,selecting the unsuitable elicitation technique can also cause project failure.The present study,therefore,aimed to identify which requirements elicitation technique is the most cost-effective for large-scale projects when time to market is a critical issue or when the customer is not available.To that end,we conducted a systematic literature review on requirements elicitation techniques.Most primary studies identified introspection as the best technique,followed by survey and brainstorming.This finding suggests that introspection should be the first choice of elicitation technique,especially when the customer is not available or the project has strict time and cost constraints.Moreover,introspection should also be used as the starting point in the elicitation process of a large-scale project,and all known requirements should be elicited using this technique.
