Preview

Bmw - a Case Study

Best Essays
Open Document
Open Document
720 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Bmw - a Case Study
References
Angle, H. L. and J. L. Perry (1981). "An Empirical Assessment of Organizational Commitment and
Organizational Effectiveness." Administrative Science Quarterly 26 : 1-13.
Arkes, H. R. and C. Blumer (1985). "The Psychology of Sunk Cost." Organizational Behavior and Human
Decision Processes 35 : 124-140.
Basili, V. R., G. Caldiera, et al. (1992). "A Reference Architecture for the Component Factory." ACM
Transactions on Software Engineering and Methodology 1 (1): 53-80.
Bowen, M. G. (1987). "The Escalation Phenomenon Reconsidered: Decision Dilemmas or Decision Errors?"
Academy of Management Review 12 (1): 52-66.
Brockner, J. (1992). "The Escalation of Commitment to a Falling Course of Action: Toward Theoretical
Progress." Academy of Management Review 17 (1): 39-61.
Brockner, J., S. Nathanson, et al. (1984). "The Role of Modeling Processes in the "Knee Deep in the Big
Muddy" Phenomenon." Organizational Behavior and Human Performance 33 : 77-99.
Brooks, F. P. (1987). "No Silver Bullet: Essence and Accidents of Software Engineering." Computer 20 (4): 10-
19.
Ewusi-Mensah, K. and Z. H. Prazasnyski (1994). "Factors contributing to the abandonment of information systems development projects." Journal of Information Technology 9 : 185-201.
Fox, F. V. and B. M. Staw (1979). "The Trapped Administrator: Effects of Job Insecurity and Policy Resistance upon Commitment to a Course of Action." Administrative Science Quarterly 24 (September): 449-471.
Garland, H. (1990). "Throwing Good Money After Bad: The Effect of Sunk Cost on the Decision to Escalate
Commitment to an Ongoing Project." Journal of Applied Psychology 75 (6): 728-731.
Hall, R. H. (1991). Organizations — Structures, Processes, & Outcomes. Englewood Cliffs, New Jersey,
Prentice Hall, Inc.
Jones, C. (1995). "Risk of Software System Failiure or Disaster." American Programmer 8 (3): 2-9.
Keil, M. (1995a). "Identifying and Preventing Runaway Systems Project." American Programmer 8 (3):



References: Angle, H. L. and J. L. Perry (1981). "An Empirical Assessment of Organizational Commitment and Organizational Effectiveness." Administrative Science Quarterly 26 : 1-13. Arkes, H. R. and C. Blumer (1985). "The Psychology of Sunk Cost." Organizational Behavior and Human Decision Processes 35 : 124-140. Basili, V. R., G. Caldiera, et al. (1992). "A Reference Architecture for the Component Factory." ACM Transactions on Software Engineering and Methodology 1 (1): 53-80. Bowen, M. G. (1987). "The Escalation Phenomenon Reconsidered: Decision Dilemmas or Decision Errors?" Academy of Management Review 12 (1): 52-66. Brockner, J. (1992). "The Escalation of Commitment to a Falling Course of Action: Toward Theoretical Progress." Academy of Management Review 17 (1): 39-61. Brockner, J., S. Nathanson, et al. (1984). "The Role of Modeling Processes in the "Knee Deep in the Big Muddy" Phenomenon." Organizational Behavior and Human Performance 33 : 77-99. Brooks, F. P. (1987). "No Silver Bullet: Essence and Accidents of Software Engineering." Computer 20 (4): 10- 19. Ewusi-Mensah, K. and Z. H. Prazasnyski (1994). "Factors contributing to the abandonment of information systems development projects." Journal of Information Technology 9 : 185-201. Fox, F. V. and B. M. Staw (1979). "The Trapped Administrator: Effects of Job Insecurity and Policy Resistance upon Commitment to a Course of Action." Administrative Science Quarterly 24 (September): 449-471. Garland, H. (1990). "Throwing Good Money After Bad: The Effect of Sunk Cost on the Decision to Escalate Commitment to an Ongoing Project." Journal of Applied Psychology 75 (6): 728-731. Hall, R. H. (1991). Organizations — Structures, Processes, & Outcomes. Englewood Cliffs, New Jersey, Prentice Hall, Inc. Jones, C. (1995). "Risk of Software System Failiure or Disaster." American Programmer 8 (3): 2-9. Keil, M. (1995a). "Identifying and Preventing Runaway Systems Project." American Programmer 8 (3): 16-22. Keil, M. (1995b). Pulling the Plug: Software Project Management and the Problem of Project Escalation. Kiesler, C. A. (1971). The Psychology of Commitment: Experiments Linking Behavior to Belief. New York, Academic Press. Markus, M. L. and M. Keil (1994). "If We Build It, They Will Come: Designing Information Systems That People Want to Use." Sloan Management Review 34 (34): 11-25. Nathanson, S., J. Brockner, et al. (1982). "Toward the Reduction of Entrapment." Journal of Applied Social Psychology 12 (3): 193-208. Patton, M. Q. (1990). Qualitative evaluation and research methods, SAGE Publications, Inc. Sabherwal, R., M. K. Sein, et al. (1994). Why Organizations Increase Commitment to Failing Information Systems Projects? Miami, FL, Dept Sauer, C. (1993). Why Information Systems Fail: A Case Study Approach, Alfred Waller. Schneider, G. P. (1993). Escalation Behavior in Information Systems Development: Alternative Motivations, Experience, and the Sunk Cost Effect Staw, B. M. (1981). "The Escalation of Commitment To a Course of Action." Academy of Management Review 6 (4): 577-587. Staw, B. M. (1982). Counterforces to Change. Change in Organizations. P. S. G. Associates. San Francisco, CA, Jossey-Bass: 87-121. Staw, B. M. and F. V. Fox (1977). "Escalation: The Determinants of Commitment to a Chosen Course of Action." Human Relations 30 (5): 431-450. Staw, B. M. and J. Ross (1987a). Behavior in Escalation Situations: Antecedents, Prototypes, and Solutions. Staw, B. M. and J. Ross (1987b). "Knowing when to pull the plug." Harvard Business Review 65 (2): 68-74. Teger, A. I. (1980). Too Much Invested To Quit. New York, Pergamon Press. Willcocks, L. (1991). "informatization in public administration and services in the United Kingdom: toward a management era?" Informatization and the Public Sector 1 (3): 189-211

You May Also Find These Documents Helpful