Yes / Information systems (IS) project failure has been a recurring problem for decades. The purpose of this paper is twofold: first, to examine the key factors that influence project failure and an analysis of the major areas that can have a significant impact on success; and second, to explore some of the key aspects that have an impact on project management performance from the practitioner perspective and discusses the problems faced by organizations in the closer integration of change and project management. Design/methodology/approach: This study critically reviews the IS failure literature developing a synthesized view of the key issues and common reasons for projects to fail. The approach taken in this study is one that focuses on a number of key questions that pull together the relevant themes in this genre of research whilst highlighting many of the implications for practitioners and organizations alike. Findings: Key questions remain on the underlying causes of instances of poor project management as an IS failure factor. The literature has omitted to develop a deeper analysis of the associations between failure factors and the potential causal relationships between these factors. The realization of project benefits relies on the success of both change and project management yet the formal integration of these two disciplines is constrained by separate standards bodies and an immature body of research. Research limitations/implications: This study is limited by its theoretical nature lacking an empirical element to provide a deeper analysis of IS failure factors and their interrelationships. This specific area is a recommendation for future research, where causal relationships between failure factors could be developed via a mathematic-based method such as interpretive structural modeling. Practical implications: With failure rates of IS projects still unacceptably high after decades of attempts to significantly change outcomes, a deeper analysis of this topic is required. The research gaps and recommendations for practitioners highlighted in this study have the potential to provide valuable contributions to this topic of research. Originality/value: The intent of this study is to present a new perspective of this genre of IS research that develops the main arguments and gaps in the literature from the practitioner viewpoint.

Software development is notorious for failure, typically defined as over budget, late delivery and/or poor quality of new information systems (IS) on project completion. The consequences of such failure can be enormous, particularly financially. As such, there is consensus by practitioners and academics alike that this practice is unacceptable. Yet with a variety of accepted development methods and tools available for use by software developers and project managers, there is still no significant reduction in the size or frequency of failure reported. In an attempt to understand the conflicts which arise in the development environment in which developers and project managers must operate, the research area is the role and value of ethics in the development of managed software projects. A definition of ethics in this context was provided by the IEEE/ACM Code of Ethics. Research was additionally conducted to understand how other professions and business areas define and enforce ethics in their respective working environments. These were (UK) Law, Finance, Retail and, law practice in the European Union. Interpretive research was then conducted to enable software development practices to be understood from the view of developers and project managers in industry. Unethical practices were then identified in a large IT company based in west London via a single, six month in-depth case study, with the data collected analysed via a series of repertory grids. Analysis and triangulation of the data collected via interviews, document analysis and observations led to an improved understanding of the causes of the unethical practices found. Conclusions and recommendations are then provided relating to implications for (a) the company participating in the research, (b) the application of the IEEE/ACM Code in industry (c) theory for ethicists.

Yes / This research critically analyzes the Interpretive Ranking Process (IRP) using an illustrative empirically derived IS project failure related case study to articulate a deeper understanding of the method. The findings emphasize the suitability of the method for a number of practical applications, but also highlight the limitations for larger matrix sized problems. The IRP process to derive the dominance between IS project failure factors is judged to be methodical and systematic, enabling the development of clear dominating interactions.