User Leadership in the Systems Development Life Cycle: A Contingency Model

The development of an information system requires four main activities that must be carried out during the systems development life cycle (sdlc): feasibility study /analysis, design, technical construction, and implementation. This paper ex- amines the conditions under which information systems (is) specialists and users should assume responsibility and decision-making authority during the sdlc. A contingency model is presented that recommends the type of responsibility and authority roles that users should assume during the sdlc to minimize the risk and uncertainty inherent in developing computer-based systems. The contingency model developed in this paper builds upon the situational charac- teristics of information system complexity, is department experience, and user past experience in system development. According to the model, certain system factors and systems development experiences require that the user become involved by exercising heavy responsibility and authority roles, while other situational factors suggest light user leadership. The concept of sdlc leadership as responsibility and authority is developed and its meaning for users during each state of the sdlc is discussed.

[1]  John T. Glennon MIS Systems: The Role of Authority and Responsibility , 1978, MIS Q..

[2]  Peter G. W. Keen Adaptive design for decision support systems , 1980 .

[3]  John G. Burch,et al.  Information systems: theory and practice , 1974 .

[4]  Richard J. Schonberger,et al.  MIS Design: A Contingency Approach , 1980, MIS Q..

[5]  Henry C. Lucas,et al.  Analysis, Design, and Implementation of Information Systems , 1983 .

[6]  James C. Wetherbe,et al.  Heuristic Development: A Redesign of Systems Design , 1979, MIS Q..

[7]  Hugh J. Watson,et al.  A Contingency Model for User Involvement in DSS Development , 1984, MIS Q..

[8]  Ephraim R. McLean End Users as Application Developers , 1979, MIS Q..

[9]  Justus D. Naumann,et al.  Prototyping: the new paradigm for systems development , 1982 .

[10]  Lucas Hc The evolution of an information system: from key-man to every person. , 1978 .

[11]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[12]  Robert P. Bostrom,et al.  MIS Problems and failures: a sociotechnical perspective part I: the cause , 1977 .

[13]  Anders Edstrom,et al.  User Influence and the Success of MIS Projects: A Contingency Approach , 1977 .

[14]  Rudy Hirschheim,et al.  Assessing participative systems design: Some conclusions from an exploratory study , 1983, Inf. Manag..

[15]  Anders Edstrom,et al.  Successful Information System Development Projects , 1977 .

[16]  H. Albert Napier,et al.  An experiment in applying the adaptive design approach to DSS development , 1984, Inf. Manag..

[17]  Ashok Shenolikar An approach to structured MIS development , 1981 .

[18]  Daniel Robey,et al.  User Involvement in Information System Development: A Conflict Model and Empirical Test , 1982 .

[19]  Niv Ahituv,et al.  Principles of information systems for management , 1982 .

[20]  William R. King,et al.  Systems analysis and project management , 1983 .