INDIVIDUAL PLAYERS IN A TEAM SPORT: STAKEHOLDER CHANGE IN COMMITMENT IN ISD PROJECTS

9th Americas Conference on Information Systems, AMCIS 2003

Volumn , Issue , 2003, Pages 1389-1393

  Valerdi, Ricardo ^a   Majchrzak, Ann ^b  

^a UNIVERSITY OF SOUTHERN CALIFORNIA   (United States)

^b UNIVERSITY OF SOUTHERN CALIFORNIA   (United States)

Author keywords

IS project management; project life cycle; stakeholder commitment

Indexed keywords

HUMAN RESOURCE MANAGEMENT; INFORMATION SYSTEMS; INFORMATION USE; PROJECT MANAGEMENT;

INFORMATION SYSTEM DEVELOPMENT; INFORMATION SYSTEMS DEVELOPMENT PROJECTS; IS PROJECT MANAGEMENT; MANAGEMENT ISSUES; PROJECT'S LIFE CYCLE; PROJECTS FAIL; RATE OF CHANGE; STAKEHOLDER COMMITMENT; TEAM SPORTS; TECHNICAL DIFFICULTIES;

LIFE CYCLE;

EID: 69549090729     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (20)

1. Beath, C., Orlikowski, W., The Contradictory Structure of Systems Development Methodologies: Deconstructing the IS-User Relationships in Information Engineering, Information Systems Research, Vol. 5, No. 4, 1994.
2. Boehm, B., Anchoring the Software Process, IEEE Software, July 1996, pp. 73.82.
3. Cooper, R., Zmud, R., Information Technology Implementation Research: A Technological Diffusion Approach, Management Science, Vol. 36, No. 2, February 1990.
4. Curtis, B., Krasner, H., Iscoe, N., A Field Study of the Software Design Process for Large Systems, Communications of the ACM, Vol. 31, No. 11, Nov. 1988, pp. 1268-1287.
5. nd Ed., Dorset House, 1999.
6. Enns, H., CIO lateral influence behaviors: Gaining peers' commitment to strategic information systems, MIS Quarterly, (27:1), Mar 2003.
7. Fairley, R., Risk Management for Software Projects, in Software Project Management: Readings and Cases, McGraw Hill, 1997.
8. George, J., The Origin of Software: Acquiring Systems at the End of the Century, in Framing the Domains of IT Management: Projecting the Future Through the Past, Pinnaflex, 2000.
9. Gersick, C., Time and Transition in Work Teams: Toward a New Model of Group Development, Academy of Management Journal, 31(1), pp. 9-41, 1988.
10. Ginzberg, M., Key Recurrent issues in the MIS implementation process, MIS Quarterly, (5:2), 1981.
11. Guinan, P., Cooprider, J., and Faraj, S., Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach, Information Systems Research, 9, 2 (June 1998), 101-125.
12. Keil, M., Pulling the plug: Software project management and the problem of escalation, MIS Quarterly, (19:4), 1995, pp. 421-448.
13. Keil, M., Managing MIS Implementation: Identifying and Removing Barriers to Use, Doctoral Dissertation, Harvard University, 1991.
14. Kirsch, L., Portfolios of Control Modes and IS Project Management, Information Systems Research, Vol. 8, No. 3, Sept 1997.
15. Markus, L., Tanis, C., The Enterprise System Experience – From Adoption to Success, in Framing the Domains of IT Management: Projecting the Future Through the Past, Pinnaflex, 2000.
16. Newman, M. & Sabherwal, R., Determinants of commitment to information systems development: A longitudinal investigation, MIS Quarterly, March 1996, p 23-55
17. Sabherwal, R., Robey, D., Reconciling Variance and Process Strategies for Studying Information System Development, Information Systems Research, 6:4, 1995.
18. Sabherwal, R., Overcoming the Problems of ISD by Building and Sustaining Commitment, Accounting, Management, and Information Technologies (5:3/4), 1995, pp. 283-309.
19. Staw, B., Knee-Deep in the Big Muddy: A Study of Escalating Commitment to a Chosen Course of Action, Organizational Behavior and Human Performance (16), 1976, pp. 27-44.
20. The Secret to Software Success http://www.cio.com/archive/070101/secret.html.