IS Projects Research Articles

Identifying and Managing Stakeholders in Enterprise Information System Projects

This article focuses on how managers and sponsors of enterprise information system (EIS) projects can identify and manage stakeholders engaged in the project. This article argues that this activity should go beyond the traditional ideas about user participation and management involvement. Also suppliers, customers, government agencies, business partners and the general public can have a clear interest in the ways that the system will be designed and implemented. This article proposes to apply identification, analysis and intervention techniques from organization and management disciplines in the IS field to enhance the changes for the successfulness of enterprise information system implementations. Some of these techniques are combined in a coherent method that may help implementers of complex IS projects to identify and categorize stakeholders and to consider appropriate ways of involvement during the various stages of the project.

Achieving it consultant objectives through client project success

Improving project performance is an important objective in IS project management. In consultant-assisted IS projects, however, consulting organizations may have additional objectives, such as knowledge acquisition and future business growth. In this study, we examined the relationship between client and consultant objectives and the role of coordination in affecting the achievement of these objectives. A research model was developed and tested using 199 consultant-assisted projects. The results showed that the achievement of consultant objectives was dependent upon the achievement of client objectives and that coordination had a positive impact on both client and consultant objectives.

A particle swarm optimization‐driven cognitive map approach to analyzing information systems project risk

AbstractProject risks encompass both internal and external factors that are interrelated, influencing others in a causal way. It is very important to identify those factors and their causal relationships to reduce the project risk. In the past, most IT companies evaluate project risk by roughly measuring the related factors, but ignoring the important fact that there are complicated causal relationships among them. There is a strong need to develop more effective mechanisms to systematically judge all factors related to project risk and identify the causal relationships among those factors. To accomplish this research objective, our study adopts a cognitive map (CM)‐based mechanism called the MACOM (Multi‐Agents COgnitive Map), where CM is represented by a set of multi‐agents, each embedded with basic intelligence to determine its causal relationships with other agents. CM has proven especially useful in solving unstructured problems with many variables and causal relationships; however, simply applying CM to project risk management is not enough because most causal relationships are hard to identify and measure exactly. To overcome this problem, we have borrowed a multi‐agent metaphor in which CM is represented by a set of multi‐agents, and project risk is explained through the interaction of the multi‐agents. Such an approach presents a new computational capability for resolving complicated decision problems. Using the MACOM framework, we have proved that the task of resolving the IS project risk management could be systematically and intelligently solved, and in this way, IS project managers can be given robust decision support.

Offshore Information Systems Project Success: The Role of Social Embeddedness and Cultural Characteristics

Agency theory has served as a key basis for identifying drivers of offshore information system project success. Consequently, the role of relational factors in driving project success has been overlooked in this literature. In this paper, we address this gap by integrating the social embeddedness perspective and the culture literature to theorize how and why relational factors affect the success of offshore IS projects that are strategic in nature. We identify organizational and interpersonal cultural differences as critical success factors in this context. Using data from a longitudinal field study of 155 offshore IS projects managed by 22 project leaders, we found evidence of a relationship between hypothesized relational factors and two measures of offshore IS project success--namely, project cost overruns and client satisfaction-- over and above the effects of project characteristics and agency factors. Specifically, we found that information exchange, joint problem solving, and trust reduce project cost overruns and improve client satisfaction. We also found a relationship between cultural differences at the organizational and team level, and offshore IS project success. The model explained 40 percent and 41 percent of the variance in project cost overruns and client satisfaction, respectively, for projects with a client representative. For projects with no client representative, the model explained 35 percent and 37 percent of the variance in project cost overruns and client satisfaction, respectively. Collectively, the results have important theoretical and practical implications for how client-- vendor relationships should be managed when partnering with offshore firms and designing offshore IS project teams.

Selective Status Reporting in Information Systems Projects: A Dyadic-Level Investigation

This study investigates selective reporting behaviors that are pursued by project managers when communicating the status of their information system initiatives to their executives. To understand the types, motivations, impacts, and antecedents of such behaviors, a message-exchange perspective is adopted and the prior literature on IS project status reporting is reviewed. This study incorporates an empirical investigation that examined the influence of five dyadic factors on selective reporting using a survey of 561 project managers. The findings of the study reveal a positive effect of reporting quality on project performance and indicate that a specific type of selective reporting behavior (optimistic biasing) has a degrading effect on reporting quality. Moreover, the findings show that all five antecedents have a significant influence on the propensity of project managers to report selectively. Specifically, the project executive's power, the project manager's trust in the executive, and the executive's quality of communication impact selective reporting directly; the executive's familiarity with the IS development process and the executive's organizational affiliation vis-a-vis that of the project manager have an indirect influence (it is mediated through other factors). The effects of each of these factors on the two types of selective reporting (optimistic and pessimistic biasing) are examined, and the implications of these findings for both researchers and managers are discussed in this article.

How Does Knowledge Integration Occur during Information Systems Projects - An Empirical Investigation of the Influence of Social Capital

IS Projects are characterized by their organizational scope. They need to integrate the specific knowledge held by an organization’s members to succeed. To do so, broad exchanges between people inside and outside the project team are required. Knowledge integration, i.e. sharing and creation of new knowledge, is part of any project. Knowledge integration follows several phases that are often long and complex, depending on the actors involved. As a consequence, knowledge integration can be affected by the social capital of the project members. An empirical investigation in two French SMEs aiming to improve their information systems shows that the three dimensions of social capital (structural, relational and cognitive) influence the knowledge integration process, even if no differentiated effect is observed through the different phases of the process. The distinction of three phases in integration, mobilizing different levels of knowledge, is confirmed, offering a promising understanding of the knowledge creation mechanisms in context of IS projects.

Explaining variations in client extra costs between software projects offshored to india

Gaining economic benefits from substantially lower labor costs has been reported as a major reason for offshoring labor-intensive information systems services to low-wage countries. However, if wage differences are so high, why is there such a high level of variation in the economic success between offshored IS projects? This study argues that offshore outsourcing involves a number of extra costs for the client organization that account for the economic failure of offshore projects. The objective is to disaggregate these extra costs into their constituent parts and to explain why they differ between offshored software projects. The focus is on software development and maintenance projects that are offshored to Indian vendors. A theoretical framework is developed a priori based on transaction cost economics (TCE) and the knowledge-based view of the firm, complemented by factors that acknowledge the specific offshore context. The framework is empirically explored using a multiple case study design including six offshored software projects in a large German financial service institution. The results of our analysis indicate that the client incurs post- contractual extra costs for four types of activities: (1) requirements specification and design, (2) knowledge transfer, (3) control, and (4) coordination. In projects that require a high level of client-specific knowledge about idiosyncratic business processes and software systems, these extra costs were found to be substantially higher than in projects where more general knowledge was needed. Notably, these costs most often arose independently from the threat of opportunistic behavior, challenging the predominant TCE logic of market failure. Rather, the client extra costs were particularly high in client-specific projects because the effort for managing the consequences of the knowledge asymmetries between client and vendor was particularly high in these projects. Prior experiences of the vendor with related client projects were found to reduce the level of extra costs but could not fully offset the increase in extra costs in highly client-specific projects. Moreover, cultural and geographic distance between client and vendor as well as personnel turnover were found to increase client extra costs. Slight evidence was found, however, that the cost-increasing impact of these factors was also leveraged in projects with a high level of required client-specific knowledge (moderator effect).

Some success factors for the communal management of knowledge

This paper explores the contribution of communal structures such as Communities of Practice (CoPs) on intraorganizational Knowledge Management (KM). First, we look at intraorganizational knowledge management and explore the role that information systems can play. We introduce the idea of “Systèmes d’Aide à la Gestion des Connaissances” SAGC (Systems to aid the Management of Knowledge) and then establish our theoretical foundations concerning communal KM, especially as it relates to the structural and functional characteristics of CoPs. The results of an exploratory qualitative survey involving Chief Knowledge Officers (CKOs) of large French businesses are presented which examine the contribution that communal structures such as CoPs can make to intraorganizational KM. The results highlight some of ‘success factors’ for the communal management of knowledge. Two types of factors in particular appear to encourage the sharing of knowledge: those related to (1) the characteristics of a CoP and (2) the organizational context. The work indicates that, perhaps contrary to what might be expected, many of the key success factors are the same ‘management’ issues that can be found in almost any IS projects while some of the issues that the literature indicates are important, appear to be less so in practice.

Reforming Public Healthcare in the Republic of Ireland with Information Systems

The need for reforming public healthcare towards greater efficiency and measurable returns on investment has been felt by governments in many countries. In Ireland, this led to the PPARS project, which sought to implement SAP across all public healthcare sites. This project, however, was unsuccessful and led to a parliamentary inquiry. To understand why the PPARS project failed, we carried out an extensive case study of the project and compared our findings to the implementation of JD Edwards in a multinational in the private sector. Our study reveals that despite specific circumstances in the public sector that contributed to the failure of the ERP project, the primary causes of failure result from a lack of understanding of what ERP involves and a failure to prepare adequately, which can be found in any organisation, public or private. This leads to significant lessons for ERP implementations and IS projects involving substantial change.

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.

Cost estimation for cross-organizational ERP projects: research perspectives

There are many methods for estimating size, effort, schedule and other cost aspects of IS projects, but only one specifically developed for Enterprise Resource Planning (ERP) (Stensrud, Info Soft Technol 43(7):413–423, 2001) and none for simultaneous, interdependent ERP projects in a cross-organizational context. The objective of this paper is to sketch the problem domain of cross-organizational ERP cost estimation, to survey available solutions, and to propose a research program to improve those solutions. In it, we: (i) explain why knowledge in the cost estimation of cross-organizational ERP is fragmented, (ii) assess the need to integrate research perspectives, and (iii) propose research directions that an integrated view of estimating cross-organizational ERP project cost should include.

User Participation in Contemporary IS Development: an IS management perspective

User participation in IS development has become an established practice perceived to improve both the development process and its outcomes. Recently, however, Markus and Mao (2004) have highlighted the need to revisit user participation in light of the changing IS development environment. A survey of New Zealand organisations with 200 or more full-time employees was undertaken in order to obtain an updated assessment of the actual practice of user participation in IS development projects. The results suggest that user participation continues to be a dominant aspect of IS development. The paper provides empirical data on the common reasons for having users participate and the form and types of user activities in development. The responding organisations perceived user participation to be beneficial to IS development in their recent IS projects, and many intended continuing or increasing their current levels of user participation in the future.

Agile development in a bureaucratic arena—A case study experience

The evolving nature of development approaches towards Agile development is viewed with some success. However, evidence suggests that not all development environments have evolved with the same alacrity, thus an organization's inherent culture may not match the development approach adopted effecting failure. This paper concerns an innovative, real-world Government IS project that is currently being implemented in the UK that reflects such a situation. The paper looks at the tension that transpired between the bureaucratic project arena and the Agile development approach. It examines stakeholders’ behaviour and attitudes borne from a bureaucratic and hierarchical society that were problematic for Agile development. It further explores the issues of conflict and trust that prevented key stakeholders from building and fostering a collaborative and co-operative collective with the Developers that had significant impact. The case study provides evidential insights into the phenomenon of stakeholder control over critical decision-making activities that prevailed over organizational driven strategies that has implications for practice.

IS projects and implementation

PurposeThe purpose of this paper is to participate in the discussion related to why IS projects, both in Western and in Eastern European countries, e.g. Poland, often fail. One major reason is claimed to be poor implementation, and the article asks whether the stakeholders involved overlook the challenge of and the need for knowledge in change management (CM) when implementing complex IT systems.Design/methodology/approachThe research is based on observations of what is reflected in the CM, the project management (PM) and the IS literature. A basic assumption for the approach is that what PM and IS textbooks focus on strongly influences the views and practice of practitioners. A content analysis method was applied to examine empirically 22 textbooks to evaluate whether the IT/PM literature emphasizes relevant essential recommendations developed in the CM literature for handling changes. A mini‐case was used to illustrate how implementation is done in practice.FindingsThe research reveals that in particular the PM authors give little priority to implementation and to essentials developed in the CM discipline. Further, the authors apply rather rational perspectives when discussing implementation. This implies focus on deterministic N‐stage models and overlooking vital organizational processes. The research also reveals that IS success depends to a large extent on how well the interfaces between the project development and the implementation processes are coordinated. The stakeholders often split the project development and implementation into two projects and postpone implementation until the development is completed. This may lead to coordination problems and to ineffective implementation.Research limitations/implicationsThe main limitation of this research is the assumption that what is written in the IT/PM books influences what the practitioners do. This may be an area for further research.Practical implicationsThe authors of IS/PM textbooks and the practitioners should pay more attention to implementation. The textbooks may benefit from borrowing essentials from the CM literature. Further, the stakeholders should start the implementation processes early and ensure effective coordination between project development and the implementation processes.Originality/valueThe main value of the paper is related to the contribution to the discussion related to why IS projects, both in Western and in Eastern European countries, often fail.

Cross-functional interface and disruption in CRM projects: Is marketing from Venus and information systems from Mars?

Because of the inherently cross-functional nature of customer relationship management, the use of cross-functional teams in CRM project implementations is virtually mandatory to achieve critical marketing and sales objectives. This study examines the effects of functional membership as well as team and individual performance evaluations on project members' perceptions of disruption and cooperation during CRM project implementations. The results show that IS project members are more likely to perceive internal volatility and manifest interfunctional conflict and less likely to perceive interfunctional cooperation than project members from either sales/marketing or general management. We also find that team performance evaluations are negatively associated with disruption and positively associated with cooperation, while individual evaluations are negatively associated with internal volatility.

Standard method use in contemporary IS development: an empirical investigation

PurposeThe purpose of this research is to obtain an updated assessment of the use of standard methods in IS development practice in New Zealand, and to compare these practices to those reported elsewhere.Design/methodology/approachA web‐based survey of IS development practices in New Zealand organisations with 200 or more full‐time employees was conducted. The results of the survey were compared to prior studies from other national contexts.FindingsThe results suggest that levels of standard method use continue to be high in New Zealand organisations, although methods are often used in a pragmatic or ad hoc way. Further, the type of method used maps to a shift from bespoke development to system acquisition or outsourcing. Organisations that reported using standard methods perceived them to be beneficial to IS development in their recent IS projects, and generally disagreed with most of the published limitations of standard methods.Research limitations/implicationsAs the intent was to consider only New Zealand organisations, the results of the survey cannot be generalised further afield. More comparative research is needed to establish whether the trends identified here occur at a wider regional or international level.Practical implicationsA significant proportion of organisations anticipated extending their use of standard methods. Growth in packaged software acquisition and outsourced development suggests an increasing need for deployment management as well as development management, possibly reflecting the increased visibility of standard project management methods.Originality/valueThe relevance of traditional standard methods of IS development has been questioned in a changing and more dynamic IS development environment. This study provides an updated assessment of standard method use in New Zealand organisations that will be of interest to researchers and practitioners monitoring IS development and acquisition elsewhere.

Mediators between coordination and IS project performance

Successful IS projects result from coordination among team members and stakeholders. We examined the effects of horizontal and vertical coordination on project performance. A total of 169 responses from IS project managers listed in the Project Management Institute of the USA were solicited, obtained, and analyzed. The results indicated that horizontal coordination can enhance the level of leadership empowerment and knowledge transfer, and help to clarify the mission and objectives among team members, while vertical coordination can enhance knowledge transfer. The results further suggested that project performance was improved by empowering team members, promoting knowledge transfer among team members and specifying clear mission and project objectives.

Exploiting organizational knowledge in developing IS project cost and schedule estimates: An empirical study

Project management is vital to the effective application of organizational resources to competing demands within and across projects. The effective application of project management, however, is predicated upon accurate estimates of the project budget and schedule. This study assesses primary and supporting activities that exploit knowledge within an organization's memory to develop project schedule durations and budgets. The study further assesses the subsequent impact of predictability on project success. Two hundred and sixteen survey responses from IT professionals with project management responsibilities were analyzed. Results found use of the primary activities of using parametric estimating techniques (use of formal models), bottom-up estimating techniques (formulating estimates at the task level), and the support activities of team reliance, realistic targets, and professional experience all impact the predictability of estimates for project cost and duration. Predictability in turn was found to directly impact project success with regards to meeting cost and duration objectives. While use of analogous estimating techniques (using similar previous projects) was not found to be useful for project managers with more experience, it was used by project managers with less experience in determining predictability.

Is Project Management: Size, Practices and the Project Management Office

This research is an investigation into IS project management practices related to projects of varying size across diverse industries. Survey data on a broad range of project management issues was collected from 129 IS project managers. The relationships between project size with 13 project management practices and 3 project performance measures were analyzed. The influence of a project management office (PMO) on the use of standardized project management practices and project performance was empirically tested. Our findings suggest that IS project size influences budget and project quality and the PMO is empirically linked to project budget.

Prediction of IS Project Escalation Based on Software Development Risk Management

Information system project failure is described as a common phenomenon. Escalation occurs when there are continued commitments for a troubled project and has been observed as one pattern of failure. The main purpose of this research was to investigate whether software development risks were the factors to discriminate between escalated projects and non-escalated projects. Thirty critical risks were selected and classified into nine risk categories under three dimensions such as product, people, and process. Probability and loss in each nine risk category were measured on the basis of 247 survey cases from IS professionals. The results show that the risk probability in the people dimension and the process dimension with management aspects was more important to predict escalation than the risk loss in those dimensions and the risk impact in the product dimension with technical aspects. The results imply that managerial factors are more critical than technical factors in predicting IS development project escalation. Additionally, it was noticed that the CMM level of an organisation was very significant to predict successful projects.