No abstract

The implementation of the Computer-Aided Despatch system at the London Ambulance Service has been one of the most notorious cases of failure within the information systems (IS) literature. What is less well known is that there followed, some time later, a much more successful implementation, described as a turnaround. This paper, based on a case study approach, describes the context and detail of that implementation. A framework from the literature, used in an analysis of the initial failure, is used to analyse and compare the similarities and differences in the development of the two systems. The framework provides four interacting elements and relationships for analysis. These elements are Supporters, Project Organisation, Information System, and the Environment in which they operate. The turnaround system was found to address directly almost all the issues identified as problematic in the failure. These included the approach taken by management to understand the needs of users, including issues unrelated to the system itself, their involvement in the development process, an improvement in the availability of resources (brought about in some part because of the previous failure), the ability to follow a relaxed timeline driven by users' acceptance levels, the preparation of infrastructure projects to develop confidence, participation and prototyping, thorough testing, phased and simple implementation, and trust building. Certain environmental factors could not be so directly addressed but nevertheless were overcome by attention to detail and internal needs. Conclusions indicate that the factors addressed are not new and are to be found in the success literature. What is unusual is that they were implemented in this case in such unlikely circumstances.

Perfection is achieved not when there is nothing more to be added but when there is nothing left to take away.<br>---Antoine de Saint-Exupery

No abstract

Changes in organizational structures, competitive environments, technologies and economies are altering the types and complexity of computer‐based information systems. For methodologies, tools and techniques to evolve to meet these changing needs, research to assess current system development practices would be expected. However, there is little evidence that the evaluation of methodologies and improvement of the systems development process are keeping pace with technological and organizational changes. This paper analyses existing research on system development methodologies and discusses the research needed to provide the information scholars and practitioners will need for the evaluation, selection and development of methodologies in a changing environment.

No abstract

Assumptions about an object under study can influence research in many ways. These preconceptions color the researcher’s perspective, and influence the research purpose, the research questions addressed, and the research methods used. This paper identifies and analyzes the following assumptions regarding information systems methodology (ISM) research: the positive impact of methodologies on the process and product of information system design; the irrationality of design practice; the existence of knowledge about good design practice; the ability to communicate design knowledge to practicing designers; and the ability to change the rationality of design practitioners. The impact of these assumptions on ISM research is examined for the purpose of highlighting limitations of past research and identifying more promising directions for the future.

Despite over a decade of study, little is really known about information systems development and the use of systems development methodologies. There has been little evaluation of methodologies in use or examination of the selection, development, adaptation or use of methodologies in practice. This paper discusses this lack of knowledge and its ramifications for research and practice.