A method of requirements change management for global software development

Ali, Naveed; Lai, Richard

doi:10.1016/j.infsof.2015.09.005

Cited by 33 publications

(32 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Firms need to manage requirements in offshore software development projects (Yadav, 2011;Ali & Lai, 2016), but few studies have examined the impact of requirements change on a project's success or failure (Yadav et al, 2013). Yadav et al (2009) report that team members who experienced requirements changes in offshore RA also experienced greater control, computer-mediated communication, and process facilitation by vendor site-coordinators.…”

Section: Requirements Changes In Offshore Projectsmentioning

confidence: 99%

“…Yadav et al (2009) report that team members who experienced requirements changes in offshore RA also experienced greater control, computer-mediated communication, and process facilitation by vendor site-coordinators. Ali and Lai (2016) propose a three-stage requirementsmanagement process for globally distributed software projects using a case study of an online shopping system to minimize risks in a globally distributed environment. Choudhury & Sabherwal (2003) Knowledge of the systems development process is a key antecedent of formal modes of control.…”

Section: Requirements Changes In Offshore Projectsmentioning

confidence: 99%

“…Yadav et al (2013) One needs to manage changes in requirements at the right time to minimize risks in a globally distributed software project. Ali & Lai (2016) …”

mentioning

confidence: 99%

See 2 more Smart Citations

Considerations for Effective Requirements Analysis in Offshore Software Development Projects: Lessons from Multi-Method Research

Yadav¹,

Adya²,

Nath³

et al. 2016

CAIS

View full text Add to dashboard Cite

Abstract:Offshore software development using geographically distributed teams is an accepted practice in software development today. However, software development companies have largely only offshored the software development lifecycle's coding and testing phases. However, lately, offshoring the requirements analysis (RA) phase has become increasingly viable for several reasons including the software industry's maturation and improved communication technologies. However, successfully evaluating this highly interactive phase between geographically dispersed client and provider teams requires special considerations. In this paper, we present practical insights garnered from conducting experiments and surveys of IS professionals from the Indian software industry and from extensively examining the literature. Our findings confirm that, subject to certain best practices, one can effectively conduct RA in software projects offshore. We present these practices as lessons learned and provide related recommendations for industry and academia.

show abstract

Section: Requirements Changes In Offshore Projectsmentioning

confidence: 99%

Section: Requirements Changes In Offshore Projectsmentioning

confidence: 99%

See 1 more Smart Citation

Considerations for Effective Requirements Analysis in Offshore Software Development Projects: Lessons from Multi-Method Research

Yadav¹,

Adya²,

Nath³

et al. 2016

CAIS

View full text Add to dashboard Cite

show abstract

“…However, GSD has introduced issues for stakeholders that are not present in software projects developed in the same location (collocated projects) . Because of development teams being in different geographical locations, differences in cultures and time zones adversely impact communication and coordination processes . Consequently, the frequency of communication, coordination, and trust between the development teams decreases .…”

Section: Introductionmentioning

confidence: 99%

A method of requirements elicitation and analysis for Global Software Development

Ali¹,

Lai

2016

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

To perform requirements elicitation and analysis, effective communication and collaboration between stakeholders are necessary. Global Software Development (GSD), where software teams are located in different parts of the world, has become increasingly popular. However, geographical distance, cultural diversity, differences in time zones, and language barriers create difficulties for GSD stakeholders in engaging in effective communication. Taking into consideration the factors involved in GSD, previous research showed that the ways by which requirements are gathered and analyzed for collocated software development cannot be used effectively for GSD. Thus, in this paper, we present a method of requirements elicitation and analysis for GSD. The method consists of 4 stages: (1) data collection; (2) educating stakeholders about GSD issues; (3) post-education assessment; and (4) requirements elicitation and analysis.Past researchers used student groups in a university environment to play the roles of stakeholders in experiments in GSD studies. Likewise, we preliminarily validate our method by applying it to a case study of an online shopping system, where the roles of client, requirements engineer, project analyst, and designers were played by a group of students.

show abstract

“…The results show that there is a lack of management in these firms and they are not fully aware of the success factors required for growth in the GSD environment. The results of this study provide guidelines for success in GSD [12][13][14] . Managerial studies are available with emphasis on the state-of-the-art regarding GSD.…”

mentioning

confidence: 99%