Rescuing troubled software projects by team transformation: A case study with an ERP project

IEEE Transactions on Engineering Management

Volumn 55, Issue 1, 2008, Pages 171-184

  Lui, Kim Man ^a   Chan, Keith C C ^a  

^a HONG KONG POLYTECHNIC UNIVERSITY   (Hong Kong)

Author keywords

IT project failures; Risk management; Software project management; Team management

Indexed keywords

ELECTRONIC MAIL; ENTERPRISE RESOURCE PLANNING; RISK MANAGEMENT; SOFTWARE ENGINEERING;

PROJECT FAILURES; SOFTWARE PROJECT MANAGEMENT; TEAM MANAGEMENT;

PROJECT MANAGEMENT;

EID: 39849085662     PISSN: 00189391     EISSN: None     Source Type: Journal    
DOI: 10.1109/TEM.2007.912933     Document Type: Article

References (47)

1. A. P. Snow and M. Keil, "The challenge of accurate software project status reporting: A two-stage model incorporating status errors," IEEE Trans. Eng. Manage., vol. 49, no. 4, pp. 491-504, Nov. 2002.
2. D. Cooke, L. Gelman, and W. J. Peterson, "ERP trends, the conference board," Rep. R-1292-01-RR, 2001.
3. K. Ewusi-Mensah, Software Development Failures: Anatomy of Abandoned Projects. Cambridge, MA: MIT Press, 2003.
4. J. Verner and W. Evanco, "In house software development: What software management practices are needed for project success," IEEE Softw. vol. 22, no. 1, pp. 86-93.
5. M. Jørgensen and D. Sjoberg, "The importance of not learning from experience," in Proc. Eur. Softw. Process Improv., Copenhagen, Denmark, 2000, pp. 2.2-2.8.
6. C. P. Holland and B. Light, "A critical success factors model for ERP implementation," IEEE Softw., vol. 16, no. 3, pp. 30-36, May/Jun. 1999.
7. N. Welti, Successful SAP R/3 Implementation: Practical Management of ERP Projects. Reading, MA: Addison-Wesley, 1999.
8. Z. Zhang, M. K. O. Lee, P. Huang, L. Zhang, and X. Huang, "A framework of ERP systems implementation success in China: An empirical study," Int. J. Prod. Econ., vol. 98, no. 1, pp. 56-80, 2005.
9. J. Smith, Troubled IT Projects: Prevention and Turnaround. Stevenage, U.K.: Institution of Electrical Engineers, 2001.
10. E. Yourdon, Death March, 2nd ed. Upper Saddle River, N.J.: Prentice-Hall, 2004.
11. T. DeMarco and T. R. Lister, Waltzing with Bears: Managing Risk on Software Projects. New York: Dorset, 2003.
12. D. Remenyi, Stop IT Project Failures Through Risk Management. London, U.K.: Butterworth Heinemann, 1999.
13. R. Schmidt, K. Lyytinen, M. Keil, and P. Cule, "Identifying software project risks: An international delphi study," J. Manage. Inf. Syst. vol. 17, pp. 5-36, 2001.
14. J. J. Jiang, G. Klein, and R. Discenza, "Information system success as impacted by risks and development strategies," IEEE Trans. Eng. Manage., vol. 48, no. 1, pp. 46-55, Feb. 2001.
15. M. Al-Mashari, A. Al-Mudimigh, and M. Zairi, "Enterprise resource planning: Ataxonomy of critical factors," Eur. J. Oper. Res., vol. 146, pp. 352-364, 2003.
16. J. S. K. Ang, C. C. Sum, and L. N. Yeo, "A multiple-case design methodology for studying MRP success and CSFs," Inf. Manage., vol. 39, pp. 271-281, 2002.
17. P. Bingi, M. K. Sharma, and J. K. Godla, "Critical issues affecting an ERP implementation," Inf. Syst. Manage., vol. 16, pp. 7-14, 1999.
18. O. M. Burns and D. Turnipseed, "Critical success factors in manufacturing resource planning implementation," Int. J. Oper. Prod. Manage., vol. 11, pp. 5-19, 1991.
19. J. F. Cox and S. J. Clark, "Problems in implementing and operating a manufacturing resource planning information system," J. Manage. Inf. Syst., vol. 1, pp. 81-101, 1984.
20. K. K. Hong and Y. G. Kim, "The critical success factors for ERP implementation: An organizational fit perspective," Inf. Manage., vol. 40, pp. 25-40, 2002.
21. V. A. Malbert, A. Soni, and M. A. Venkataramanan, "Enterprise resource planning: Managing the implementation process," Eur. J. Oper. Res. vol. 146, pp. 302-314, 2003.
22. Y. Xue, H. Liang, W. Boulton, and C. A. Snyder, "ERP implementation failures in China: Case studies with implications for ERP vendors," Int. J. Prod. Econ., vol. 97, pp. 279-295, 2005.
23. C. Rolland and N. Prakash, "Bridging the gap between organizational needs and ERP functionality," Requirements Eng., vol. 5, pp. 180-193, 2000.
24. C. A. O'Reilly, D. F. Caldwell, and W. P. Bamett, "Work group demography, social integration, and turnover," Administ. Sci. Quart. vol. 34, pp. 21-37, 1989.
25. J. Pfeffer, "Organizational demography," in Research in Organizational Behavior, vol. 5, L. L. Cummings and B. M. Staw, Eds. Greenwich, CT: JAI, 1983, pp. 299-357.
26. Y. J. Yeh and H. W. Chou, "Team composition and learning behaviors in cross functional teams," Soc. Behav. Pers., vol. 33, no. 3, pp. 391-402, 2005.
27. J. Anton and N. L. Petouhoff, Customer Relationship Management : The Bottom Line to Optimizing Your ROI, 2nd ed. Upper Saddle River, NJ: Prentice-Hall, 2002.
28. L. H. Pelled, K. M. Eisenhardt, and K. R. Xin, "Exploring the black box: An analysis of work group diversity, conflict, and performance," Administ. Sci. Quart., vol. 44, pp. 1-28, 1999.
29. K. A. Jehn, G. B. Northcraft, and M. A. Neale, "Why differences make a difference: A field study of diversity, conflict, and performance in workgroups," Administ. Sci. Quart., vol. 44, pp. 741-763, 1999.
30. B. R. Forer, "The fallacy of personal validation: A classroom demonstration of gullibility," J. Abnorm. Psychol., vol. 44, pp. 118-121, 1949.
31. S. Plous, The Psychology of Judgment and Decision Making. New York: McGraw-Hill, 1993.
32. B. Brehmer, "In one word: Not from experience," Acta. Psychol., vol. 45, pp. 223-241, 1980.
33. R. E. Nisbett and T. E. Wilson, "Telling more than we can know: Verbal reports on mental process," Psychol. Rev., vol. 84, pp. 231-259, 1997.
34. A. C. North, D. J. Hargreaves, and J. McKendrick, "The influence of in-store music on wine selections," J. Appl. Psychol., vol. 84, no. 2, pp. 271-276, 1999.
35. J. Preston and N. Epley, "Explanations versus applications: The explanatory power of valuable beliefs," Psychol. Sci., vol. 16, no. 10, pp. 826-832, 2005.
36. J. M. Jackson and J. M. Harkins, "Equity in effort: An explanation of the social loafing effect," J. Pers. Soc. Psychol., vol. 49, pp. 1199-1206, 1985.
37. S. M. Stewart, AcceleratedSAP: Implementation at the Speed of Business. New York: McGraw-Hill, 1998.
38. K. M. Lui and K. C. C. Chan, "Capability maturity model and SAP: Toward a universal ERP implementation model," Int. J. Enterprise Inf. Syst. vol. 1, no. 3, pp. 69-95, 2005.
39. B. D. Hiquet and A. F. Kelly, SAP R/3 Implementation Guide: A Manager's Guide to Understanding SAP. Indianapolis, IN: Macmillan Technical, 1998.
40. M. E. Haynes, Effective Meeting Skills: A Practical Guide for More Productive Meetings. Menlo Park, CA: Crisp, 1997.
41. F. P. Brooks, The Mythical Man-Month: Essays on Software Engineering, Anniversary ed. Reading, MA: Addison-Wesley, 1995.
42. H. J. Smith and M. Keil, "The reluctance to report bad news on troubled software projects: A theoretical model," Inf. Syst. J., vol. 13, pp. 69-95, 2003.
43. B. C. Y. Tan, H. Jeff, H. J. Smith,M. Keil, and R. Montealegre, "Reporting bad news about software projects: Impact of organizational climate and information asymmetry in an individualistic and a collectivistic culture," IEEE Trans. Eng. Manage., vol. 50, no. 1, pp. 64-77, Feb. 2003.
44. D. W. Karolak, Global Software Development: Managing Virtual Teams and Environments. Los Alamitos, CA: IEEE Computer Society, 1998.
45. J. Collins, Good to Great: Why Some Companies Make the Leap - and Others Don't. New York: Harper Collins, 2001.
46. K. Beck, eXtreme Programming Explained, 2nd ed. Boston, MA: Addison-Wesley, 2005.
47. Y. Li, C.-H. Tan, and H.-H. Teo, "Innovative usage of information technology in Singapore organizations: Do CIO characteristics make a difference?," IEEE Trans. Eng. Manage., vol. 53, no. 2, pp. 177-190, May 2006.