Abstract

. This study explores Global Virtual Software Teams’ development practices and try to demystify some of the misconceptions about global software development practices based on findings from the global virtual software teams’ experiment that was carried out at DePaul University from 2011 – 2018. The moments of translation from the perspective of actor-network theory (ANT) was employed in the data analysis, to examine how development approach was selected by the global virtual teams. One of the key findings from our research is that the success of a global software development project does not have a strong dependency on the development approach. While we agree that it is one of the key influencing factors, there are other equally strong factors for global virtual software team’s success.

Highlights

  • Companies employ project management approach in the development and implementation of software in their environments

  • The waterfall software development approach and traditional project management have been the dominant approaches used for software development for many years among collocated teams and global teams alike

  • The choice is left to the teams, and sometimes the dominant software development practice in the organizations will be adopted by the global teams

Read more

Summary

Introduction

Companies employ project management approach in the development and implementation of software in their environments. Companies change from the traditional waterfall to what is considered a more dynamic approach, agile practices for various reasons. Agile practices seem to provide more transparency than waterfall approach, which assist some organizations. Perhaps the most important benefit of agile practice is the ability to get a working software product or features to market faster than waterfall approach. Despite the numerous benefits and advantages of agile approach for software development, its adoption has been challenging (Boehm & Turner, 2005; Nerur, Mahapatra, & Mangalaraj, 2005). Researchers note that organizations that have stable requirements can develop successful projects by using waterfall (McHugh, McCaffery, & Casey, 2012). In attempts to find a more suitable approach, some organizations have resulted to hybrid agile, such as Scrum-Fall, a combination of waterfall and Scrum development methods (Binder, Aillaud, & Schilli, 2014; Rahmanian, 2014; Adelakun, Garcia, Tabaka, & Ismail, 2017)

Methods
Discussion
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.