Assessing moderating effect in meta-analysis: a re-analysis of top management support studies and suggestions for researchers

Meta-analysis has been increasingly used as a knowledge cumulation tool by IS researchers. In recent years many meta-analysts have conducted moderator analyses in an attempt to develop and test theories. These studies suffer from several methodological problems and, as a result, may have contributed to rather than resolved inconsistent research findings. For example, a previous meta-analysis reports that task interdependence moderates the effect of top management support to render it a non-critical component in systems implementation projects when task interdependence is low. We show that this conclusion is the result of uncorrected measurement error and an erroneous application of a fixed effects regression analysis. We discuss other pitfalls in the detection and confirmation of moderators including the use of the Q statistic and significance tests. Our recommended approach is to break the sample into subgroups and compare their credibility and confidence intervals. This approach is illustrated in a re-analysis of the top management support literature. Our results indicate that top management support is important in both high and low task interdependence groups and in fact may be equally important in both groups. Guidelines are developed to help IS researchers properly conduct moderator analyses in future meta-analytic studies.     

A model of information systems development project performance

abstract. Performance in information systems development (ISD) projects can be critical to business success. But, while project performance has been the subject of much debate, there has been little empirical research into its determinants. A survey of IS projects in the UK and New Zealand is analysed to test hypotheses concerning performance in terms of both project completion and budget (time-cost) variances. Subsequently, a secondary analysis of the findings is used to build a more complete empirical model of project performance. The paper helps to develop the theory of IS development project performance and also has significant implications for practice. Discussion of the findings highlights the importance of project team dynamics, risk management, senior management support for strategic projects and user participation in ensuring successful IS project performance.     

Towards an interpretative integrative framework to conceptualise social processes in large information systems implementations

This paper develops a new interpretative framework to study large information systems implementations. This framework is used to make explicit the various links between the implementation process, the wider organisation and external context. This framework is applied to a substantive case to integrate relevant organisational levels and distinct activity domains, as well as the interconnections between those levels and domains through time. More specifically, the paper extends a previous substantive case analysis with an interpretivist conceptualisation and theory triangulation in order to uncover the deeper structure and meanings embedded in a major information systems (IS) implementation process. The research scope of the IS implementation ranged from initial project formulation, to system development and management training, managing support from key stakeholders, and marginal system use. The substantive case, which has been published elsewhere [33], is based on a national information systems initiative to support the decentralisation and modernisation of management functions in health districts of the Ministry of Public Health in Ecuador. A key objective of this paper is to build a process theory of IS implementation, situated within the context of the substantive case study.     

The Use of a Formalised Risk Model in NHS Information System Development

Information systems (IS) and technology are used extensively throughout the National Health Service (NHS), and the 1998 national information strategy, ‘Information for Health’, sets out how the NHS will be developing and implementing IS to support patient care within the next decade. This new IS initiative is set against a mixed record of success of IS projects in the NHS, with a number of high-profile failures. This paper highlights the need to consider the ‘organisational issues’ involved in systems implementation to avoid failures. It goes on to advocate the use of a process-oriented and organisation studies-based model for risk analysis and management for use in NHS IS projects. Two famous NHS case studies are used to validate the model. It is concluded that there is a real need in the NHS for tools to better control the inherent risks involved in IS development and implementation. Ultimately, the success of IS projects in the NHS is crucial if they want to best utilise clinical and patient information, with the overall aim of improving the efficiency and standard of the nation’s health care.     

Pre-project partnering impact on an information system project,project team and project manager

Information system (IS) managers have long recognised the need to use project management approaches in the design and delivery of their system development projects. The result has been the widespread use of project teams headed by a project leader or manager. However, given the fact that there has been a low success rate for IS projects, there is a growing need to seek out new methods and controls for projects. One approach involves the practice of altering the project environment prior to the commencement of project tasks. To determine whether such pre-project activities may be effective, a model is proposed and tested relating the activities to the performance of the project manager and characteristics of an effective project team. Data from a sample of 186 project team members indicate that the pre-project activities lead to more effective teams and managers and eventually to project success. Thus, it is important that organisations begin work on projects at an earlier stage.     

Software process improvement with weak management support: an analysis of the dynamics of intra-organizational alliances in IS change initiatives

Software Process Improvement (SPI) projects are large-scale, complex organization-wide change initiatives. They require considerable investments in personnel, time and money and impact just about every aspect of software firms. The group charged with conducting an SPI project has, however, little formal authority to influence or force software professionals to engage in SPI work or to define and implement changes. The SPI literature suggests that successful SPI initiatives depend on strong commitment from top management. But what should the SPI group do if management support is weak? In this paper, we present an analysis of how an SPI group can use alliances to obtain influence and succeed when management support is weak. Our study is based on a 3-year longitudinal field study of SPI change initiatives at Denmark Electronics. Our findings show that a lack of top management support is not necessarily incompatible with success. This research opens an important new area of research on intra-organizational alliances and information system (IS) implementation. It has the potential to offer new theories and practical advice on how IS implementation projects can be more effectively managed.     

Towards an integrated measurement of IS project performance: The project performance scorecard

Determining the contribution of information system (IS) projects is a difficult endeavour. This research presents a framework for evaluating and measuring IS project performance that seek to address this problem while moving away from the reliance on the traditional assessment method (time, cost, specifications). When IS projects fail or succeed is difficult to determine what conditions enabled the outcome. However, if we are to develop a higher level of IS project management competence we need frameworks that can help in assessing IS project outcomes while critically reflecting and learning from IS project management practices. The Project Performance Scorecard (PPS) recommended here is one framework that can help to advance our understanding IS project management and evaluation approaches. This framework integrates concepts from existing models of IS success, the Balanced Scorecard and project management practices. A case study approach is used to illustrate the use of the PPS, and offers insights into how it can be useful in assessing the performance of IS projects.

RefModPM: A Conceptual Reference Model for Project Management Information Systems

Project management information systems have changed considerably in the last decade. Today they go far beyond traditional scheduling as well as resource management. These systems have become comprehensive information systems (IS) that support the entire life cycle of projects, project programmes and project portfolios. In this context, project-oriented organizations face a new challenge: the design, implementation and operation of such information systems has become increasingly complex, since numerous processes have to be considered, diverse stakeholder interests taken into account and corresponding software systems selected. The reference model for project management IS (RefMod^PM) presented here addresses these challenges and aims to support corresponding implementation projects. This article introduces RefMod^PM by discussing its construction process and evaluation, as well as providing an overview of its architecture and presenting one part of the reference model in detail.     

Building Effective Project Teams

Most IS managers know that managing a project to its successful completion is not an easy task. Conflicts among team members often delay a project's schedule and can ruin the team's morale. Although most managers usually follow the traditional, authoritative style of management to control their team members, this style is no longer considered as effective as the more contemporary, collaborative approach. This article describes how IS managers can manage their projects more effectively by creating collaborative project teams.     

A process model for successful CRM system development

According to industry analysts, almost two-thirds of customer relationship management system development projects fail. Information systems developers and researchers ultimately want to lower these failure rates and support successful development. Most IS research has focused on identifying the factors, or ingredients, correlated with IS development success. We propose a process model as a recipe for successful IS development. Adopting a process theory approach permits examining the sequence of and interplay between specific factors involved in the process. Two case studies - one success, one failure - illustrate how these factors influence customer relationship management (CRM) system development and, ultimately, determine whether a project succeeds or fails.     

Establishing a Project Management Methodology

The systems development process has become increasingly complex as a result of advances in computer technology and the ever-broadening scope of systems development efforts. Given this environment, a sound project management methodology is essential to maintaining control and ensuring that projects are completed on time and within budget. To help IS managers review and evaluate their systems development process, this article discusses the basic elements of effective project management.     

Building Effective Project Teams

Most IS managers know that managing a project to its successful completion is not an easy task. Conflicts among team members often delay a project's schedule and can ruin the team's morale. Although most managers usually follow the traditional, authoritative style of management to control their team members, this style is no longer considered as effective as the more contemporary, collaborative approach. This article describes how IS managers can manage their projects more effectively by creating collaborative project teams.     

Identification and classification of ERP critical failure factors in Iranian industries

Implementation of Enterprise Resource Planning systems (ERPs) is a complex and costly process, which usually results in serious failures. The majority of previous studies and research projects have been conducted in identifying ERP Critical Success Factors (CSFs) rather than Critical Failure Factors (CFFs). On the other hand, most studies have been devoted to developed countries, while in developing countries, many companies have moved towards using such systems. The majority of IT/IS management standards and guidelines have been developed by technologically-leading countries. But developing countries, which mostly confront with especial challenges, have a different condition from the implicit assumptions of leading countries. Iran is one of these countries that many of its ERP implementation projects led to failure. There is no comprehensive study that identifies ERP CFFs in Iranian industries. The main purpose of this study is to identify such factors and classify them to help other industries, consultants and implementers to prevent failures in the implementation of ERP projects. So, at first, with the semi structured interviews and literature reviews, 47 failure factors were identified. After that a questionnaire developed and sent to ERP project team members in Iranian industries that failed in their ERP projects. Robust Exploratory Factor Analysis (EFA) has been used for data analysis, which finally classified critical failure factors in seven groups named as vendor and consultant, human resources, managerial, project management, processes, organizational and technical. The results of this study have provided a very useful reference for scholars and managers to identify the relevant issues of ERP projects failure in developing countries.     

Establishing a Project Management Methodology

The systems development process has become increasingly complex as a result of advances in computer technology and the ever-broadening scope of systems development efforts. Given this environment, a sound project management methodology is essential to maintaining control and ensuring that projects are completed on time and within budget. To help IS managers review and evaluate their systems development process, this article discusses the basic elements of effective project management.     

Team performance and information system implementation

Although the Earned Value Method (EVM), a multi-dimensional project control system, has been widely used since 1960, there has been little research focused specifically on its application in IS implementation. The management of IS projects—including the accurate forecasting of project duration—is complicated by the strong impact of the learning curve on the effectiveness of EVM. This study makes new contributions by advancing formulas for the accurate prediction of project duration, and by developing a decision support model in which the learning curve is fully integrated with EVM, and performance changes due to learning are isolated from other factors affecting project duration. The study makes three contributions to the understanding and use of EVM in IS implementation: (1) It provides an extended version of EVM, (2) it provides an illustration of the application of EVM to a real project situation based on empirical data from an ERP implementation project, and (3) it provides a theoretical basis for empirical studies of IS project control techniques. The decision support model can be used to determine both the learning curve coefficient and the project completion date during the early stages of a project, and it thus offers a significant practical contribution to the management of IS projects.

Organisational champions of IT innovation

This paper reports on an investigation of the characteristics of 10 organisational champions of information technology (IT) innovation in The Netherlands. The institutions at which they work are in the financial, transport, government and software sectors. Much of the research in this area has focused considerable attention on the individual personality traits of champions. This research project was positioned to contribute to the literature by broadening the focus of attention beyond individual-level characteristics. Since IT innovations occur within an organisational context, there is also a need to explore the role of organisation-level characteristics. This study explored both the individual- and the organisation-level characteristics exhibited by those promoting IT innovations in their firms. The results of this study show that these organisational champions fall somewhere in between the classic IT champion and the project manager. While personal leadership characteristics are not as much in evidence, organisational characteristics are emphasised more. They use their political skills to obtain resources and organisational acceptance of the IT innovations as they are shepherding the innovation through the organisational bureaucracy. However, these champions seem to place as much emphasis on creativity as classic IT champions. When necessary, they break rules, give veiled threats and find ways to get around the organisational bureaucracy. They seek creative outlets for themselves and those they manage. These findings suggests that a promising way to reduce the rate of information system (IS) project failures is to learn not only from IS projects undertaken by IT champions but also from innovation undertaken by other champions — business champions and champions of other technologies.     

Social ties,knowledge sharing and successful collaboration in globally distributed system development projects

Traditionally, the main focus of the information system (IS) literature has been on technical aspects related to system development projects. Furthermore, research in the IS field has mainly focused on co-located project teams. In this respect, social aspects involved in IS projects were neglected or scarcely reported. To fill this gap, this paper studies the contribution of social ties and knowledge sharing to successful collaboration in distributed IS development teams. Data were drawn from two successful globally distributed system development projects at SAP and LeCroy. Data collected were codified using Atlas.ti software. The results suggest that human-related issues, such as rapport and transactive memory, were important for collaborative work in the teams studied. The paper concludes by discussing the implications for theory and suggesting a practical guide to enhance collaborative work in globally distributed teams.     

Undersizing software systems: third versus fourth generation software development

A critical component of information systems (IS) project management is completing projects on time; however, most software development efforts have completion time overruns. This study examines the prior research in IS project management for assessing the completion time for new software development projects and discusses a project management phenomenon where the expected time for project completion is undersized. At one firm two groups of software development projects are examined: (1) Cobol projects (third generation) and (2) Natural (fourth generation). It was found that both the Cobol and Natural projects experienced similar overruns. Undersizing is posited as the explanation.     

Blending bureaucratic and collaborative management styles to achieve control ambidexterity in IS projects

Managing information systems (IS) projects requires what we refer to as ‘control ambidexterity’, which is the use of different types of control to meet conflicting demands. This leads to the use of contrasting styles of IS project management and creates tensions in managerial practice, neither of which are well understood. We address this theoretical gap in our understanding based on an exploratory case study of an IS implementation project in the financial services industry. Adopting the lens of management styles as a meta-theoretical perspective, we sought to address two research questions: (1) Which management style(s) do IS project managers draw upon in practice and why? (2) What kinds of tensions result for IS project managers and team members from drawing upon contrasting management styles in combination – and how do IS project managers and team members deal with these tensions? Two contrasting styles of management emerged from our data – bureaucratic and collaborative – that are drawn upon by IS project managers to achieve control ambidexterity. Furthermore, drawing upon these two different styles in combination within the confines of a single project creates tensions. We explore these tensions and present an illustrative example of how IS project managers can deal with these tensions successfully in practice. Specifically, we find that they can be dealt with effectively by a tandem of two project managers who share responsibility for managing the IS project. The findings of this study have important implications for our understanding of control ambidexterity in IS projects.