End-User System Development: Lessons from a Case Study of IT Usage in an Engineering Organization

Abstract

How much end-user computing is too much? Should end users develop systems? This case looks at a study of end user computing within the engineering organizations of an electric utility undergoing deregulation. The case was initiated when management perceived that too much engineering time was spent doing IS functions. The case found that there was significant effort being expended on system development, support, and ad hoc use. Reviews of a few key systems illustrate quality problems found with the end-user developed systems. Several issues were identified affecting system development including use of programming standards, documentation, infrastructure integration, and system support. Additionally, the issues of obsolescence, security, and procurement are discussed.