Antecedents for Successful Collaboration in Requirements Engineering

Purpose The main focus of the requirements engineering (RE) literature has been on the technical aspects related to the RE projects. Research has largely focused on the specific methods for collecting the requirements for an information system. Much less research has been conducted on the social and collaboration aspects of RE. To fill this gap, this paper aims to study the contribution of social factors, such as social ties, knowledge sharing and flexibility, for successful collaboration in RE teams. Design/methodology/approach The research followed the case study methodology. Data were collected from a successful RE and development project in a public sector company in Finland. The model for social collaboration by Kotlarsky and Oshri (2005) was applied as a starting point for analysis, but new concepts emerged during the coding process. Findings The results suggest that human-related aspects, such as flexibility, collective knowledge and transactive memory, were important for successful collaborative work in the RE team studied. The results show a clear connection between the collaboration factors in the RE process and the success of the end product. Originality/value The article fills a clear gap in the RE literature. It shows that human-related aspects are important in the RE process. This opens up new research avenues, such as investigating the effect of human-related factors on the whole lifecycle of a project.

[1]  M. Markus,et al.  Information technology and organizational change: causal structure in theory and research , 1988 .

[2]  Ilan Oshri,et al.  Social ties, knowledge sharing and successful collaboration in globally distributed system development projects , 2005, Eur. J. Inf. Syst..

[3]  Gary Klein,et al.  The relation of requirements uncertainty and stakeholder perception gaps to project management performance , 2009, J. Syst. Softw..

[4]  Hugh J. Watson,et al.  Determining Information Requirements for an EIS , 1993, MIS Q..

[5]  Elizabeth J. Davidson,et al.  Technology Frames and Framing: A Socio-Cognitive Investigation of Requirements Determination , 2002, MIS Q..

[6]  S. Berg Snowball Sampling—I , 2006 .

[7]  Wynne W. Chin,et al.  Managing Client Dialogues During Information Systems Design to Facilitate Client Learning , 2005, MIS Q..

[8]  L. Sproull,et al.  Coordinating Expertise in Software Development Teams , 2000 .

[9]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[10]  Theerasak Thanasankit,et al.  Requirements engineering—exploring the influence of power and Thai values , 2002, Eur. J. Inf. Syst..

[11]  Robert W. Zmud,et al.  A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques , 1992, MIS Q..

[12]  R. Stake The art of case study research , 1995 .

[13]  A. Michael Huberman,et al.  An expanded sourcebook qualitative data analysis , 1994 .

[14]  Iris Vessey,et al.  Learning to Specify Information Requirements: The Relationship between Application and Methodology , 1993, J. Manag. Inf. Syst..

[15]  Rajiv Sabherwal,et al.  Determinants of Commitment to Information Systems Development: A Longitudinal Investigation , 1996, MIS Q..

[16]  Peng Xu,et al.  Software Process Tailoring: An Empirical Investigation , 2007, J. Manag. Inf. Syst..

[17]  B MilesMatthew,et al.  Qualitative Data Analysis , 2009, Approaches and Processes of Social Science Research.

[18]  Richard L. Daft,et al.  Organizational information requirements, media richness and structural design , 1986 .

[19]  Beth A. Bechky Sharing Meaning Across Occupational Communities: The Transformation of Understanding on a Production Floor , 2003, Organ. Sci..

[20]  P. Ring,et al.  Relational Quality: Managing Trust in Corporate Alliances , 2001 .

[21]  Nicholas P. Vitalari,et al.  Differences Between Novice and Expert Systems Analysts: What Do We Know and What Do We Do? , 1998, J. Manag. Inf. Syst..

[22]  Gary Klein,et al.  The role of team problem solving competency in information system development projects , 2011 .

[23]  James C. Wetherbe Executive Information Requirements: Getting It Right , 1991, MIS Q..

[24]  Alan M. Davis,et al.  A Unified Model of Requirements Elicitation , 2004, J. Manag. Inf. Syst..

[25]  John Child,et al.  Trust—the fundamental bond in global collaboration , 2001 .

[26]  Jun Sun,et al.  Information requirement elicitation in mobile commerce , 2003, CACM.

[27]  Russell L. Ackoff,et al.  Management misinformation systems , 1967 .

[28]  Mark Keil,et al.  Understanding software project risk: a cluster analysis , 2004, Inf. Manag..

[29]  Pierre N. Robillard,et al.  The role of knowledge in software development , 1999, CACM.

[30]  Anselm L. Strauss,et al.  Basics of qualitative research : techniques and procedures for developing grounded theory , 1998 .

[31]  Kalle Lyytinen,et al.  Attention Shaping and Software Risk - A Categorical Analysis of Four Classical Risk Management Approaches , 1998, Inf. Syst. Res..

[32]  K. Weick,et al.  Collective mind in organizations: Heedful interrelating on flight decks. , 1993 .

[33]  J. C. Henderson,et al.  Managing I/S Design Teams: A Control Theories Perspective , 1992 .

[34]  Randolph B. Cooper,et al.  Information Technology Development Creativity: A Case Study of Attempted Radical Change , 2000, MIS Q..

[35]  Itzhak Shemer,et al.  Systems analysis: a systemic analysis of a conceptual model , 1987, CACM.

[36]  Wanda J. Orlikowski,et al.  Research Commentary: Desperately Seeking the "IT" in IT Research - A Call to Theorizing the IT Artifact , 2001, Inf. Syst. Res..

[37]  Jan Pries-Heje,et al.  Aligning Software Processes with Strategy , 2006, MIS Q..

[38]  Robert P. Bostrom,et al.  Mis problems and failures: a socio-technical perspective , 1977 .

[39]  Robert E. Kraut,et al.  Coordination in software development , 1995, CACM.

[40]  Roderick M. Kramer,et al.  Swift trust and temporary groups. , 1996 .

[41]  D. Francis Review of Basics of Qualitative Research Techniques and Procedures for Developing Grounded Theory (2nd edition) , 1999 .

[42]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[43]  Anna Sidorova,et al.  Uncovering the Intellectual Core of the Information Systems Discipline , 2008, MIS Q..

[44]  Glenn J. Browne,et al.  The Impact of Analyst-Induced Misinformation on the Requirements Elicitation Process , 2012, MIS Q..

[45]  A. Strauss Basics Of Qualitative Research , 1992 .

[46]  Kristin Braa,et al.  Interpretation, intervention, and reduction in the organizational laboratory: a framework for in-context information system research , 1999 .

[47]  Suzanne Rivard,et al.  Toward an Assessment of Software Development Risk , 1993, J. Manag. Inf. Syst..

[48]  Frank J. Bernieri,et al.  Interactional Synchrony and Rapport: Measuring Synchrony in Displays Devoid of Sound and Facial Affect , 1994 .

[49]  P. Baumard Tacit Knowledge in Organizations , 1999 .

[50]  Minder Chen,et al.  Using Group Support Systems and Joint Application Development for Requirements Specification , 1993, J. Manag. Inf. Syst..

[51]  Kenneth R. Stern,et al.  Low vs. high-fidelity prototyping debate , 1996, INTR.

[52]  K. Eisenhardt Building theories from case study research , 1989, STUDI ORGANIZZATIVI.

[53]  Jean Hartley,et al.  Case study research , 2004 .

[54]  Glenn J. Browne,et al.  An Empirical Investigation of User Requirements Elicitation: Comparing the Effectiveness of Prompting Techniques , 2001, J. Manag. Inf. Syst..

[55]  J. Brown,et al.  Organizing Knowledge , 1998 .

[56]  P. Adler,et al.  Two Types of Bureaucracy: Enabling and Coercive , 1996 .

[57]  D. Wegner Transactive Memory: A Contemporary Analysis of the Group Mind , 1987 .

[58]  J ElamJoyce,et al.  Inside a software design team , 1993 .

[59]  Christine Nadel,et al.  Case Study Research Design And Methods , 2016 .

[60]  William R. King,et al.  Strategic Planning for Management Information Systems , 1978, MIS Q..

[61]  Iris Vessey,et al.  Requirements specification: learning object, process, and data methodologies , 1994, CACM.

[62]  Brian Corbitt,et al.  Exploring the cultural and social impacts on the requirements engineering processes ‐ highlighting some problems challenging virtual team relationships with clients , 2001 .

[63]  Michael J. Muller,et al.  Taxonomy of PD Practices: A Brief Practitioner's Guide , 1993, Commun. ACM.

[64]  Ephraim R. McLean,et al.  Expertise Integration and Creativity in Information Systems Development , 2005, J. Manag. Inf. Syst..

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

[66]  J. Gabarro The development of working relationships , 1990 .