Using Shared Leadership to Foster Knowledge Sharing in Information Systems Development Projects

Information systems development (ISD) projects are enormously complex, requiring input from heterogeneous team members with a varied array of knowledge and skills. Because expertise in an ISD project is broad and complex, this expertise is not possessed by an individual developer but distributed among team members who are selected for their expertise in the relevant domains. In addition to working cooperatively and integrating tasks, team members must exchange knowledge in order to complete the assigned project. This enormous dependence on knowledge sharing creates extensive burdens for coordination and communication on both project managers and relevant domain experts throughout all stages of the ISD project. This paper conceptualizes the benefits of a combination of vertical and shared leadership in ISD project teams, as proposed by Pearce and maps this structure to related early work on the dynamics and productivity of programming teams (most notably, Weinberg's Egoless Programming Team Structure).

[1]  E. Jantsch The design of inquiring systems,: by C. West Churchman New York, Basic Books, 1972. , 1972 .

[2]  C. Churchman,et al.  The design of inquiring systems: basic concepts of systems and organization , 1971 .

[3]  Adenubi Jo The criteria for success in endodontics. , 1978 .

[4]  Marilyn Mantei,et al.  The effect of programming team structures on programming tasks , 1981, CACM.

[5]  Patricia J. Guinan,et al.  Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach , 1998, Inf. Syst. Res..

[6]  Gerald M. Weinberg,et al.  Psychology of computer programming , 1971 .

[7]  Varun Grover,et al.  Special Section: Toward a Theory of Business Process Change Management , 1995, J. Manag. Inf. Syst..

[8]  H. Rittel,et al.  Dilemmas in a general theory of planning , 1973 .

[9]  Ephraim R. McLean,et al.  The DeLone and McLean Model of Information Systems Success: A Ten-Year Update , 2003, J. Manag. Inf. Syst..

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

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

[12]  Ephraim R. McLean,et al.  Information Systems Success: The Quest for the Independent Variables , 1992, J. Manag. Inf. Syst..

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

[14]  Peter B. Seddon A Respecification and Extension of the DeLone and McLean Model of IS Success , 1997, Inf. Syst. Res..

[15]  Herbert A. Simon,et al.  Technology and Environment , 1973 .

[16]  F. W. McFarlan,et al.  Portfolio approach to information systems , 1989 .

[17]  Jaak Jurison,et al.  Software Project Management: The Manager's View , 1999, Commun. Assoc. Inf. Syst..

[18]  G. Morgan,et al.  Images of Organization: The Executive Edition , 1998 .