No abstract

Abstract

This paper contributes to the field by applying the Soft Systems Methodology (SSM) for building a model,which improves the understanding of the role of project set-up and communication in the transitionphase of projects involving global virtual teams.Although research has highlighted the importance of knowledge transfer in offshore outsourced projects, the literature says little about real-world knowledgetransfer problems experienced by project managers and provides little guidance for developing solutions. In this paper, we investigate knowledge transfer problems in the transition phase of offshore outsourcedsoftware projects and how set-up of the phaseinfluences unstructured knowledge transfer. Using the SSM, we identify relevant constructs and relationships and build a conceptual model. This highlights the importance of an appropriate communication inception as a basis for relationship building and defines a new construct, 'knowledge discourse', whichsignifies the importance of two-way interaction for the transfer of unstructured knowledge.Posted at the Zurich Open Repository and Archive, University of Zurich ZORA URL: https://doi.org/10.5167/uzh-72301 Accepted Version Originally published at: Wende, Erik; Schwabe, Gerhard; Philip, Tom; King, Gregory (2013). Why they do not understand -a model of knowledge discourse in the transition phase of globally distributed projects. In: Hawaii International Conference on System Sciences-46, Maui, Hawaii, 7 January 2013 -10 January 2013. Why They do not Understand -a Model of Knowledge Discourse in the Transition Phase of Globally Distributed Projects

Purpose This paper aims to explore the concept of early warning signs (EWSs) in offshore-outsourced software development (OOSD) projects at the team level. It also aims to identify the EWSs of failure in the onshore-offshore project context and understand how they are perceived by responsible managers. Design/methodology/approach A grounded theory approach is followed by gathering data from 19 failed OOSD projects using project managers from client and vendor sides as the key informants. Findings This study identified 13 EWSs of failure in five categories of trust and team cohesion, common project execution structures, awareness of shared work context, collaboration between teams and onshore-offshore team coordination capabilities. EWSs were found to comprise two components: early warning issues and early signals of failures. Research limitations/implications India-based vendors’ data in the study formed the primary weakness of the work regarding generalizability, even though it brought homogeneity to data. Lack of triangulation of failure data through client or vendor peers proved impossible in this research as failure remains a very sensitive topic. Dual composition of EWSs could be applied to institutionalize an early warning tool in projects. Originality/value The paper develops an exploratory model of EWSs of failure and project failure in the OOSD project context. The two-component framework of EWSs allows project managers to eliminate false positives while identifying EWSs. It contributes to the information system failure, risk management and information technology offshoring research streams.

Offshore-outsourced software development (OOSD) projects involvemultifaceted risks throughout the project execution, as they are handed over tothird-party organizations and thus are exposed to more risks than in domesticoutsourcing or captive offshoring. We concentrate on failed OOSD projects inthis paper and analyze the unique aspects of such projects at the team level thatlead to failures. Using the grounded theory approach, we conducted semistructuredinterviews with 19 project managers involved in OOSD projectfailures from the vendor and client sides, who are based in India or Switzerland.We developed a set of propositions regarding multiple teams in the OOSDproject context to explain failures. Integration of inter-organizational offshoreand onshore teams from the vendor and client sides was found to beindispensable in avoiding project failures. Six categories of unique aspects thatlead to OOSD project failures were identified and discussed in this exploratorywork. Abstract. Offshore-outsourced software development (OOSD) projects involve multifaceted risks throughout the project execution, as they are handed over to third-party organizations and thus are exposed to more risks than in domestic outsourcing or captive offshoring. We concentrate on failed OOSD projects in this paper and analyze the unique aspects of such projects at the team level that lead to failures. Using the grounded theory approach, we conducted semistructured interviews with 19 project managers involved in OOSD project failures from the vendor and client sides, who are based in India or Switzerland. We developed a set of propositions regarding multiple teams in the OOSD project context to explain failures. Integration of inter-organizational offshore and onshore teams from the vendor and client sides was found to be indispensable in avoiding project failures. Six categories of unique aspects that lead to OOSD project failures were identified and discussed in this exploratory work.