Information systems development project performance in the 21st century
暂无分享,去创建一个
[1] Donald E. Conlon,et al. Too Close to Quit: The Role of Project Completion in Maintaining Commitment1 , 1998 .
[2] Barry M. Staw,et al. Behavior in escalation situations: Antecedents, prototypes, and solutions. , 1987 .
[3] A. Pettigrew. Longitudinal Field Research on Change: Theory and Practice , 1990 .
[4] Mark Keil,et al. Pulling the Plug: Software Project Management and the Problem of Project Escalation , 1995, MIS Q..
[5] A. Tversky,et al. The framing of decisions and the psychology of choice. , 1981, Science.
[6] Cheng-Suang Heng,et al. De-escalation of commitment in software projects: Who matters? What matters? , 2003, Inf. Manag..
[7] W. R. King,et al. Decision Processes for Developing Strategic Applications of Information Systems: A Contingency Approach* , 1992 .
[8] M. Tushman,et al. Organizational Evolution: A Metamorphosis Model of Convergence and Reorientation , 1985 .
[9] Donal Flynn,et al. Escalation and de-escalation of commitment to information systems projects: Insights from a project evaluation model , 2006, Eur. J. Oper. Res..
[10] Laurie J. Kirsch,et al. Deploying Common Systems Globally: The Dynamics of Control , 2004, Inf. Syst. Res..
[11] David Bicknell,et al. Crash: Learning From The World's Worst Computer Disasters , 1997 .
[12] Mark Keil,et al. Why software projects escalate: the importance of project management constructs , 2003, IEEE Trans. Engineering Management.
[13] L. Festinger,et al. A Theory of Cognitive Dissonance , 2017 .
[14] Matthew Hinton,et al. Customer relationship management systems: implementation risks and relationship dynamics , 2002 .
[15] Mark Keil,et al. Information Technology Project Escalation: A Process Model , 2008, Decis. Sci..
[16] M. Tushman,et al. Technological Discontinuities and Dominant Designs: A Cyclical Model of Technological Change , 1990 .
[17] Mark Keil,et al. Turning Around Troubled Software Projects: An Exploratory Study of the Deescalation of Commitment to Failing Courses of Action , 1999, J. Manag. Inf. Syst..
[18] Daniel Robey,et al. A Dual-Motor, Constructive Process Model of Organizational Transition , 2004 .
[19] Elli Georgiadou,et al. Software Process and Product Improvement: A Historical Perspective , 2003 .
[20] Stuart E. Madnick,et al. Software Project Dynamics: An Integrated Approach , 1991 .
[21] Glen Whyte,et al. ESCALATING COMMITMENT IN GROUP DECISION MAKING. , 2007 .
[22] J. Brockner. The Escalation of Commitment to a Failing Course of Action: Toward Theoretical Progress , 1992 .
[23] Richard Heeks,et al. Development Informatics Working Paper Series Failure, Success and Improvisation of Information Systems Projects in Developing Countries A. Introduction: Defining and Measuring Success and Failure.....................................2 C. Explaining Developing Country Information Systems Success and F , 2022 .
[24] S. Goldfinch,et al. Pessimism, Computer Failure, and Information Systems Development in the Public Sector , 2007 .
[25] Lynn A. Isabella. Evolving Interpretations as a Change Unfolds: How Managers Construe Key Organizational Events , 1990 .
[26] Elaine Romanelli,et al. Convergence and Upheaval: Managing the Unsteady Pace of Organizational Evolution , 1986 .
[27] Richard Heeks. Reinventing Government in the Information Age: International Practice in IT-Enabled Public Sector Reform , 2002 .
[28] Shan Ling Pan,et al. Escalation and de‐escalation of commitment: a commitment transformation analysis of an e‐government project , 2006, Inf. Syst. J..
[29] Barry M. Staw,et al. Expo 86: An Escalation Prototype. , 1986 .
[30] Magnus Mähring. IT project governance , 2002 .
[31] R. Calantone,et al. Escalation of commitment during new product development , 2002 .
[32] The Challenges of Complex IT Projects , 2004 .
[33] Deborah G. . Ancona. Outward Bound: Strategic for Team Survival in an Organization , 1990 .
[34] Rajiv Sabherwal,et al. Determinants of Commitment to Information Systems Development: A Longitudinal Investigation , 1996, MIS Q..
[35] Joan CheneyMann,et al. Preventing Runaway IT Projects: Protecting Auditors from Entrapment , 2003, AMCIS.
[36] I. Royer. Why bad projects are so hard to kill. , 2003, Harvard business review.
[37] Tom DeMarco,et al. Controlling Software Projects , 1982 .
[38] Barry M. Staw,et al. ORGANIZATIONAL ESCALATION AND EXIT: LESSONS FROM THE SHOREHAM NUCLEAR POWER PLANT , 1993 .
[39] H. Klein,et al. Information systems development as social action: Theoretical perspective and practice , 1991 .
[40] Charalambos L. Iacovou. The IPACS project: when IT hits the fan , 1999, J. Inf. Technol..
[41] James M. Utterback,et al. Radical Innovation and Corporate Regeneration , 1994 .
[42] Laurie J. Kirsch,et al. Portfolios of Control Modes and IS Project Management , 1997, Inf. Syst. Res..
[43] Kimberly D. Elsbach,et al. Acquiring Organizational Legitimacy Through Illegitimate Actions: A Marriage of Institutional and Impression Management Theories , 1992 .
[44] M. Tushman,et al. Technological Discontinuities and Organizational Environments , 1986 .
[45] Richard Heeks,et al. e-Government as a Carrier of Context , 2005, Journal of Public Policy.
[46] Charles J. Capps,et al. Information Technology Customer Service: ―Best Practices‖ Processes For Operations , 2011 .
[47] Mark Keil,et al. Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models , 2000, MIS Q..
[48] Richard Heeks. e-Government as a Carrier of Context , 2005, Journal of Public Policy.
[49] L. Willcocks. Managing information systems in UK public administration: Issues and prospects , 1994 .
[50] Cynthia Mathis Beath,et al. Linking Information Technology and Corporate Strategy: an Organizational View , 1986, ICIS.
[51] Robert W. Zmud,et al. Management of Large Software Development Efforts , 1980, MIS Q..
[52] Laurie J. Kirsch,et al. Requirements determination for common systems: turning a global vision into a local reality , 2006, J. Strateg. Inf. Syst..
[53] J. Utterback. One Point of View: Radical Innovation and Corporate Regeneration , 1994 .
[54] Ramiro Montealegre,et al. De-escalating Information Technology Projects: Lessons from the Denver International Airport , 2000, MIS Q..
[55] William J. Abernathy,et al. Patterns of Industrial Innovation , 1978 .
[56] Charles J. Capps,et al. Runaway Information Technology Projects: A Punctuated Equilibrium Analysis , 2010, Int. J. Inf. Technol. Proj. Manag..
[57] H. Russell Johnston,et al. Developing Capabilities to Use Information Strategically , 1988, MIS Q..
[58] Ashley A. Bush,et al. A Comparison of Transaction Cost, Agency, and Knowledge-Based Predictors of IT Outsourcing Decisions: A U.S.-Japan Cross-Cultural Field Study , 2007, J. Manag. Inf. Syst..
[59] Barry M. Staw,et al. Organizational decision making: The escalation of commitment: An update and appraisal , 1996 .
[60] Glen Whyte,et al. Escalating Commitment to a Course of Action: A Reinterpretation , 1986 .
[61] Darren Dalcher,et al. Introduction: Avoiding IS/IT Implementation Failure , 2003, Technol. Anal. Strateg. Manag..
[62] R. I. Sutton. The Process of Organizational Death: Disbanding and Reconnecting , 1987 .
[63] C. Gersick. REVOLUTIONARY CHANGE THEORIES: A MULTILEVEL EXPLORATION OF THE PUNCTUATED EQUILIBRIUM PARADIGM , 1991 .
[64] S. Gould,et al. Punctuated equilibria: an alternative to phyletic gradualism , 1972 .
[65] Richard Heeks. Reinventing Government in the Information Age , 1999 .
[66] Wanda J. Orlikowski,et al. CASE Tools as Organizational Change: Investigating Incremental and Radical Changes in Systems Development , 1993, MIS Q..