Collaboration Change in Enterprise Software Development

Enterprise software development is a complex effort that may last years. Enterprise software is often developed by a systems integrator that makes modifications to a pre-made package or builds tailored software for the specific purpose. The development may include many developer organizations, the user organization, and their different departments and sub-units. Their collaboration evolves through project incidents, phases and even crises. The practices of project management, communication, contracts, and ultimately personal relationships change intentionally or unintentionally. These changes may cause uncertainties and discontinuities for the development. This study observes changes during enterprise software development and their influence on collaboration practices in different situations. During twenty years of development both internal and external crises and changes in the business environment triggered changes in collaboration. The collaboration practices are classified with four modes of collaboration (contract, cooperation, personified, and process) that illustrate emphasis in collaboration in different circumstances.

[1]  Yvonne Dittrich,et al.  ERP Customization as Software Engineering: Knowledge Sharing and Cooperation , 2009, IEEE Software.

[2]  K. Charmaz,et al.  Constructing Grounded Theory , 2014 .

[3]  A. Strauss,et al.  Basics of qualitative research: Grounded theory procedures and techniques. , 1993 .

[4]  Ben Light,et al.  A Critical Success Factors Model for ERP Implementation , 1999, IEEE Softw..

[5]  Jimmy C. Huang,et al.  Social Capital and Knowledge Integration in an ERP Project Team: The Importance of Bridging and Bonding , 2004 .

[6]  Torgeir Dingsøyr,et al.  Research challenges in large-scale agile software development , 2013, SOEN.

[7]  Niels Bjørn-Andersen,et al.  Exploring Value Cocreation in Relationships Between an ERP Vendor and its Partners: A Revelatory Case Study , 2012, MIS Q..

[8]  T. Davenport Putting the enterprise into the enterprise system. , 1998, Harvard business review.

[9]  Suprateek Sarker,et al.  Using a case study to test the role of three key social enablers in ERP implementation , 2000, Inf. Manag..

[10]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[11]  Cathy Urquhart,et al.  Putting the ‘theory’ back into grounded theory: guidelines for grounded theory studies in information systems , 2009, Inf. Syst. J..

[12]  Fergal McCaffery,et al.  A Process Framework for Global Software Engineering Teams , 2012, Inf. Softw. Technol..

[13]  Steven Sawyer,et al.  Packaged software: implications of the differences from custom approaches to software development , 2000, Eur. J. Inf. Syst..

[14]  A. Cockburn,et al.  Agile Software Development: The People Factor , 2001, Computer.

[15]  Henk Akkermans,et al.  Vicious and virtuous cycles in ERP implementation: a case study of interrelations between critical success factors , 2002, Eur. J. Inf. Syst..

[16]  Audris Mockus,et al.  An empirical study of global software development: distance and speed , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[17]  Joe Nandhakumar,et al.  The dynamics of contextual forces of ERP implementation , 2005, J. Strateg. Inf. Syst..

[18]  Jeanne W. Ross,et al.  Learning to Implement Enterprise Systems: An Exploratory Study of the Dialectics of Change , 2002, J. Manag. Inf. Syst..

[19]  Gary Klein,et al.  Controlling ERP consultants: Client and provider practices , 2013, J. Syst. Softw..

[20]  A. Pettigrew Longitudinal Field Research on Change: Theory and Practice , 1990 .

[22]  Patricia Lago,et al.  Organizational social structures for software engineering , 2013, CSUR.

[23]  Steve Sawyer,et al.  A market-based perspective on information systems development , 2001, CACM.