On Cross-Enterprise Collaboration
Globalization, specialization, and rapid innovation are changing several aspects of business operations. Many large organizations that were once self-sufficient and that could dictate processes to partners and suppliers are now finding this model difficult to sustain. In the emerging model of global service delivery several competing service providers must work collaboratively to develop business solutions, either hierarchically or as peers. Overall project failures, uncontrollable delays, and significant financial losses have been observed in many global service delivery projects, indicating the importance of finding new ways to better support cross-enterprise work. This paper puts forth directions to explore the management and coordination of complex end-to-end processes carried out collaboratively by several organizations.
Keywordscoordination collaboration work
Unable to display preview. Download preview PDF.
- 2.Chesbrough, H.: Open Services Innovation. Jossey-Bass, San Francisco (2011)Google Scholar
- 4.Hammer, M.: The Agenda. Crown Business, New York (2001)Google Scholar
- 5.IBM: The essential CIO: Insights from the global chief information officer study (May 2011)Google Scholar
- 11.Slowinski, G., Segal, M.: The Strongest Link. Amacom, New York (2003)Google Scholar
- 13.Tang, C.S., Zimmerman, J.D.: Managing new product development and supply chain risks: The Boeing 787 case. Supply Chain Forum 10(2), 74–86 (2009)Google Scholar
- 14.Tapscott, D., Williams, A.D.: Wikinomics: How Mass Collaboration Changes Everything. Portfolio Penguin, New York (2006), expanded edn.Google Scholar
- 16.Varshney, L.R., Oppenheim, D.V.: Coordinating global service delivery in the presence of uncertainty. In: Proceedings of the 12th International Research Symposium on Service Excellence in Management, QUIS12 (June 2011)Google Scholar
- 17.Wiredu, G.O.: A framework for the analysis of coordination in global software development. In: Proceedings of the 2006 International Workshop on Global Software Development for the Practitioner, pp. 38–44 (May 2006)Google Scholar