It project governance implementation as institutionalization process: Evidence from the financial services industry
The implementation of IT project governance (ITPG) is a response to the increased regulatory pressure and the high failure rate of IT projects. Although ITPG is common, there is little research on this phenomenon, and very little is known about the forces that drive ITPG or the process by which such governance is implemented in organizations. This paper presents a process theory of ITPG implementation developed from case studies of five large companies in the financial services industry, using the grounded theory method. The model proposes three phases of ITPG implementation: standardization, centralization, and professionalization, and key drivers of each phase. The paper also shows how the proposed process theory is consistent with and can be integrated with institutional theory to demonstrate ITPG as an institutional process.
- [Show abstract] [Hide abstract] ABSTRACT: Financial Regulation presents an important restatement of the purposes and objectives of financial regulation. The authors provide details and data on the scale, nature and costs of regulatory problems around the world, and look at what sort of countries and sectors require special attention and policies. Key topics covered include: - The need to recast the form of regulation - Incentive structures for financial regulation - Proportionality - New techniques for risk management - Regulation in emerging countries - Crisis management - Prospects for financial regulation in the future.0Comments 155Citations
- [Show abstract] [Hide abstract] ABSTRACT: A widely accepted and usable taxonomy is a fundamental element in the development of a scientific body of knowledge. However, the creation of good empirical taxonomies of implementation processes is complicated by the need to consider the dynamics of the implementation process. This paper addresses this difficulty by using an optimal matching procedure to measure the pairwise distances among event sequences occurring in 53 computer-based information system (IS) implementation projects. Cluster analysis based on these inter-sequence distances is used to generate.the empirical taxonomy of implementation processes. The resulting taxonomy includes six distinct archetypical processes. One of the process types is labeled textbook life cycle (type 4) due to its close resemblance to the detailed, rational approach commonly prescribed in IS textbooks. The logical minimalist process (type 1) follows some of the basic steps of the textbook approach, but is characterized by little project definition and infrequent assignment of personnel. Whereas both textbook life cycle and logical minimalist approaches use external vendors and consultants to some extent, external dependence is much greater in traditional off-the-shelf (type 2) and outsourced cooperative (type 5) processes. The traditional off-the-shelf process simply involves purchasing the system from an external vendor, with little system construction or assignment of personnel. In contrast, the outsourced cooperative process consists of joint system development by internally assigned personnel and external vendors. The remaining two process types-problem-driven minimalist (type 3) and in-house trial and error (type 6)-are both considerably influenced by performance problems. The problem-driven minimalist process is initiated by such problems, with little project definition, and results in a reassignment of organizational roles. The in-house trial-and-error process begins like textbook life cycle, with a clear project definition, but involves frequent system modifications to respond to the performance problems encountered during the project. The paper demonstrates how an empirical taxonomy that incorporates the dynamics of event sequences may be developed. The archetypes comprising the taxonomy are related to other implementation process models available in the literature. Some limitations of the study are acknowledged and its implications for future research and practice are discussed.0Comments 112Citations
- [Show abstract] [Hide abstract] ABSTRACT: Miller, Cardinal, and Glick (1997) challenged the conclusions in Golden (1992b), which examined the use of retrospective data in strategic management research. Further, the authors suggest that my findings have led many other researchers to avoid the use of retrospective data. The present note suggests recent researchers have not entirely avoided retrospective data but have perhaps added precautions when using such data. I also suggest that Miller and colleagues did not fully represent important aspects of my research and inappropriately compare my study with others.0Comments 62Citations