Boundaries between Participants in Outsourced Requirements Construction

The concept of the boundary is a powerful analytic tool for analyzing the challenges in collaboration between participants in outsourced requirements construction. Through an ethnographic study in a requirements construction project, where participants came from the client and vendor organizations, and represented varying expertises and organizational positions, we found professional boundaries between users and external software developers, and between external software experts and in-house information system (IS) experts. The authority boundary between the client’s manager and operatives was evident. Findings were discussed within the knowledge areas that are needed in the professional IS development. In order to help IS experts, participatory design (PD) practitioners and IS researchers in their attempts to develop the user-designer and client-vendor relationships, PD for outsourced IS development should be developed and further researched.

[1]  Robert J. Anderson,et al.  Representations and Requirements: The Value of Ethnography in System Design , 1994, Hum. Comput. Interact..

[2]  Michèle Lamont,et al.  Money, Morals and Manners: The Culture of the French and American Upper- Middle Class. , 1992 .

[3]  M. Hammersley,et al.  Ethnography and participant observation. , 1994 .

[4]  Karen Holtzblatt,et al.  Contextual design , 1997, INTR.

[5]  Bandula Jayatilaka,et al.  Information systems outsourcing: a survey and analysis of the literature , 2004, DATB.

[6]  Rudy Hirschheim,et al.  Towards a distinctive body of knowledge for Information Systems experts: coding ISD process knowledge in two IS journals , 2004, Inf. Syst. J..

[7]  Ian Sommerville,et al.  Ethnographically informed analysis for software engineers , 2000, Int. J. Hum. Comput. Stud..

[8]  Timo Saarinen,et al.  The Missing Concepts of User Participations: An Empirical Assessment of User Participation and Information System Success , 1991, Scand. J. Inf. Syst..

[9]  Venkataraman Ramesh,et al.  Research in software engineering: an analysis of the literature , 2002, Inf. Softw. Technol..

[10]  Jonathan Grudin,et al.  Interface: an evolving concept , 1993, CACM.

[11]  Jens Dibbern,et al.  Explaining Variations in Client Extra Costs Between Software Projects Offshored to India , 2008, MIS Q..

[12]  R. Kling Computerization and Controversy , 1997 .

[13]  Helena Karasti,et al.  Bridging Work Practice and System Design: Integrating Systemic Analysis, Appreciative Intervention and Practitioner Participation , 2001, Computer Supported Cooperative Work (CSCW).

[14]  Paul R. Carlile,et al.  A Pragmatic View of Knowledge and Boundaries: Boundary Objects in New Product Development , 2002, Organ. Sci..

[15]  Emmanuelle Vaast,et al.  The Emergence of Boundary Spanning Competence in Practice: Implications for Implementation and Use of Information Systems , 2005, MIS Q..

[16]  M. Lamont,et al.  Boundary Processes: Recent Theoretical Developments and New Contributions , 2007 .

[17]  Netta Iivari,et al.  Mediation between Design and Use: Revisiting Five Empirical Studies , 2009 .

[18]  Alan H. Bond,et al.  Readings in Distributed Artificial Intelligence , 1988 .

[19]  Marina Jirotka Analysing the Workplace and User Requirements: Challenges for the Development of Methods for Requirements Engineering , 2000 .

[20]  Wanda J. Orlikowski,et al.  Knowing in practice: Enacting a collective capability in distributed organizing , 2002, STUDI ORGANIZZATIVI.

[21]  Rajiv Sabherwal,et al.  The evolution of coordination in outsourced software development projects: a comparison of client and vendor perspectives , 2003, Inf. Organ..

[22]  Donal James Flynn,et al.  Information Systems Requirements Determination and Analysis , 2003 .

[23]  M. Lamont,et al.  The Study of Boundaries in the Social Sciences , 2002 .

[24]  Jonathan Grudin,et al.  Interactive systems: bridging the gaps between developers and users , 1991, Computer.

[25]  Tom Rodden,et al.  Moving out from the control room: ethnography in system design , 1994, CSCW '94.

[26]  Florence Millerand,et al.  Who are the users? Who are the developers? Webs of users and developers in the development process of a technical standard , 2010, Inf. Syst. J..

[27]  P. Bourdieu,et al.  实践与反思 : 反思社会学导引 = An invitation to reflexive sociology , 1994 .

[28]  K. Lyytinen,et al.  Research on information systems development in Scandinavia—unity in plurality , 1998 .

[29]  Douglas Schuler,et al.  Participatory Design: Principles and Practices , 1993 .

[30]  Netta Iivari,et al.  Bridge Builders in IT Artifact Development , 2007, ECIS.

[31]  Susan Leigh Star,et al.  Infrastructure and Ethnographic Practice , 2002, Scand. J. Inf. Syst..

[32]  Bruce I. Blum,et al.  Beyond programming - to a new era of design , 1996 .

[33]  Austin Henderson,et al.  Interaction Analysis: Foundations and Practice , 1995 .

[34]  Rudy Hirschheim,et al.  A Dynamic Framework for Classifying Information Systems Development Methodologies and Approaches , 2000, J. Manag. Inf. Syst..

[35]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[36]  Pamela J. Hinds,et al.  Workplace Studies: Recovering Work Practice and Informing System Design, Paul Luff, Jon Hindmarsh and Christian C. Heath (eds.) , 2000, Computer Supported Cooperative Work (CSCW).

[37]  Lucy A. Suchman,et al.  Making work visible , 1995, CACM.

[38]  Andrew Clement,et al.  Computing at Work: Empowering Action by Low-Level Users , 1996, Computerization and Controversy, 2nd Ed..

[39]  Terry Trickett,et al.  Design at Work , 1992 .

[40]  Trevor Pinch,et al.  How users matter : The co-construction of users and technologies , 2003 .

[41]  Morten Kyng,et al.  Making representations work , 1995, CACM.

[42]  P. Atkinson Handbook of ethnography , 2001 .

[43]  N. Denzin,et al.  Handbook of Qualitative Research , 1994 .

[44]  Hilda Tellioglu,et al.  Cooperative work across cultural boundaries in systems design , 1999, Scand. J. Inf. Syst..

[45]  Susan Leigh Star,et al.  Institutional Ecology, `Translations' and Boundary Objects: Amateurs and Professionals in Berkeley's Museum of Vertebrate Zoology, 1907-39 , 1989 .

[46]  M. Lynne Markus,et al.  Participation in Development and Implementation - Updating An Old, Tired Concept for Today's IS Contexts , 2004, J. Assoc. Inf. Syst..

[47]  Kalle Lyytinen,et al.  Boundary Objects in Design: An Ecological View of Design Artifacts , 2007, J. Assoc. Inf. Syst..

[48]  Andrew Clement,et al.  Computing at work: empowering action by “low-level users” , 1994, CACM.

[49]  Amrit Tiwana,et al.  Beyond the black box: knowledge overlaps in software outsourcing , 2004, IEEE Software.

[50]  Susan Leigh Star,et al.  The Structure of Ill-Structured Solutions: Boundary Objects and Heterogeneous Distributed Problem Solving , 1989, Distributed Artificial Intelligence.