Functionality risk in information systems development: An empirical investigation

IEEE Transactions on Engineering Management

Volumn 53, Issue 3, 2006, Pages 412-425

  Tiwana, Amrit ^a   Keil, Mark ^b  

^a IOWA STATE UNIVERSITY   (United States)

^b GEORGIA STATE UNIVERSITY   (United States)

Author keywords

Conjoint; Functionality risk; Implementation failure; Information integration theory; Information systems development; Knowledge integration; Knowledge transformation; Project management; Software project risk

Indexed keywords

KNOWLEDGE BASED SYSTEMS; PROJECT MANAGEMENT; RISK MANAGEMENT;

FUNCTIONALITY RISK; INFORMATION INTEGRATION THEORY; INFORMATION SYSTEMS DEVELOPMENT (ISD); KNOWLEDGE INTEGRATION; KNOWLEDGE TRANSFORMATION; SOFTWARE PROJECT RISK;

MANAGEMENT INFORMATION SYSTEMS;

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

References (72)

1. T. Abdel-Hamid, K. Sengupta, and D. Ronan, "Software project control: An experimental investigation of judgment with fallible information," IEEE Trans. Softw. Eng., vol. 19, no. 6, pp. 603-612, Jun. 1993.
2. N. Anderson, Foundations of Information Integration Theory. New York: Academic, 1981.
3. L. Argote, B. McEvily, and R. Reagans, "Managing knowledge in organizations: An integrative framework and review of emerging themes," Manag. Sci., vol. 49, no. 4, pp. 571-582, 2003.
4. R. D. Banker and S. A. Slaughter, "The moderating effects of structure on volatility and complexity in software enhancement," Inf. Syst. Res., vol. 11, no. 3, pp. 219-240, 2000.
5. H. Barki, S. Rivard, and J. Talbot, "Toward an assessment of software development risk," J. Manag. Inf. Syst., vol. 10, no. 2, pp. 203-225, 1993.
6. H. Barki, S. Rivard, and J. Talbot, "An integrative contingency model of software project risk management," J. Manag. Inf. Syst., vol. 17, no. 4, pp. 37-69, 2001.
7. R. Baskerville and J. Stage, "Controlling prototype development through risk analysis," MIS Quart., vol. 20, no. 4, pp. 481-504, 1996.
8. C. Benko and W. McFarlan, Connecting the Dots: Aligning Projects with Objectives in Unpredictable Times. Boston, MA: Harvard Bus. Sch. Press, 2003.
9. B. Boehm and R. Ross, "'Theory-W software project management: Principles and examples," IEEE Trans. Softw. Eng., vol. 15, no. 7, pp. 902-916, Jul. 1989.
10. B. W. Boehm, "Software risk management: Principles and practices," IEEE Softw. Mag., vol. 8, no. 1, pp. 32-41, Jan. 1991.
11. T. Byrd, K. Cossick, and R. Zmud, "A synthesis of research on requirements analysis and knowledge acquisition techniques," MIS Quart., vol. 16, no. 1, pp. 117-138, 1992.
12. P. Carlile and E. Rebentisch, "Into the black box: The knowledge transformation cycle," Manag. Sci., vol. 49, no. 9, pp. 1180-1195, 2003.
13. P. D. Chatzoglou, "Use of methodologies: An empirical analysis of their impact on the economics of the development process," Eur. J. Inf. Syst., vol. 6, no. 4, pp. 256-270, 1997.
14. V. Choudhury and R. Sabherwal, "Portfolios of control in outsourced software development projects," Inf. Syst. Res., vol. 14, no. 3, pp. 291-314, 2003.
15. E. K. Clemons, "Evaluation of strategic investments in information technology," Commun. ACM, vol. 34, no. 1, pp. 22-36, 1991.
16. A. Cockburn, Agile Software Development. Reading, MA: Addison Wesley, 2002.
17. B. Curtis, H. Krasner, and N. Iscoe, "A field study of the software design process for large systems," Commun. ACM, vol. 31, no. 11, pp. 1268-1287, 1988.
18. H. Drummond, "The Politics of risk: Trials and tribulations of the Taurus project," J. Inf. Technol., vol. 11, pp. 347-357, 1996.
19. R. Fairley, "Risk management for software projects," IEEE Softw. Mag., vol. 11, no. 3, pp. 57-67, May 1994.
20. R. Fairley and M. Willshire, "Why the Vasa sank: 10 problems and some antidotes for software projects," IEEE Softw. Mag., vol. 20, no. 2, pp. 18-25, Mar.-Apr. 2003.
21. S. Faraj and L. Sproull, "Coordinating expertise in software development teams," Manag. Sci., vol. 46, no. 12, pp. 1554-1568, 2000.
22. R. Fichman and S. Moses, "An incremental process for software implementation," Sloan Manag. Rev., pp. 39-52, 1999.
23. R. G. Fichman and C. Kemerer, "The assimilation of software process innovations: An organizational learning perspective," Manag. Sci., vol. 43, no. 10, pp. 1345-1363, 1997.
24. B. Fitzgerald, "Formalized systems development methodologies: A critical perspective," Inf. Syst. J., vol. 6, no. 1, pp. 3-23, 1996.
25. M. Fraser, K. Kumar, and V. Vaishnavi, "Informal and formal requirements specification languages: Bridging the gap," IEEE Trans. Softw. Eng., vol. 17, no. 5, pp. 454-466, May 1991.
26. R. Glass, "Matching methodology to problem domain," Commun. ACM, vol. 47, no. 5, pp. 19-21, 2004.
27. A. Gopal, T. Mukhopadhyay, and M. Krishnan, "The role of software processes and communication in offshore software development," Commun. ACM, vol. 45, no. 4, pp. 193-200, 2002.
28. R. Grant, "Prospering in dynamically-competitive environments: Organizational capability as knowledge integration," Organization Sci., vol. 7, no. 4, pp. 375-387, 1996.
29. P. E. Green, K. Helsen, and B. Shandler, "Conjoint internal validity under alternative profile presentations," J. Consumer Res., vol. 15, no. 3, pp. 392-397, 1988.
30. P. J. Guinan, J. G. Cooprider, and S. Faraj, "Enabling software development team performance during requirements definition: A behavioral versus technical approach," Inf. Syst. Res., vol. 9, no. 2, pp. 101-125, 1998.
31. J. Hartwick and H. Barki, "Explaining the role of user participation in information systems development," Manag. Sci., vol. 40, no. 4, pp. 440-465, 1994.
32. W. Hays, Statistics. New York: Holt, Rinehart, and Winston, 1973.
33. J. Herbsleb and A. Mockus, "An empirical study of speed and communication in globally distributed software development," IEEE Trans. Softw. Eng., vol. 29, no. 6, pp. 481-494, Jun. 2003.
34. A. Hickey and A. Davis, "A unified model of requirements elicitation," J. Manag. Inf. Syst., vol. 20, no. 4, pp. 65-84, 2004.
35. J. Highsmith, "The great methodologies debate part I: Opening statement," Cutter IT J., vol. 14, no. 12, pp. 2-4, 2001.
36. B. Ives and M. M. Olson, "User involvement and MIS success: A review of research," Manag. Sci., vol. 30, no. 5, pp. 586-603, 1984.
37. J. Jiang, G. Klein, and J. Balloun, "Systems analysis attitudes toward information systems development," Inf. Resources Manag. J., vol. 11, no. 4, pp. 5-10, 1998.
38. M. Keil and E. Carmel, "Customer-developer links in software development," Commun. ACM, vol. 38, no. 5, pp. 33-44, 1995.
39. M. Keil, P. E. Cule, K. Lyytinen, and R. C. Schmidt, "A framework for identifying software project risks," Commun. ACM, vol. 41, no. 11, pp. 76-83, 1998.
40. M. Keil, B. C. Y. Tan, K. K. Wei, T. Saarinen, V. Tuunainen, and A. Wassenaar, "A cross-cultural study on escalation of commitment behavior in software projects," MIS Quart., vol. 24, no. 2, pp. 299-325, 2000.
41. M. Khalifa and J. Verner, "Drivers of software development method usage," IEEE Trans. Eng. Manag., vol. 47, no. 3, pp. 360-369, Aug. 2000.
42. L. J. Kirsch, "The management of complex tasks in organizations: Controlling the systems development process," Organization Sci., vol. 7, no. 1, pp. 1-21, 1996.
43. R. Kraut and L. Streeter, "Coordination in software development," Commun. ACM, vol. 38, no. 3, pp. 69-81, 1995.
44. W. Kuhfeld, R. Tobias, and M. Garratt, "Efficient experimental-design with marketing-research applications," J. Marketing Res., vol. 31, no. 4, pp. 545-557, 1994.
45. R. Langlois, "Modularity in technology and organization," J. Econ. Behav. Organization, vol. 49, 2002.
46. M. Laroche, J. Bergeron, and C. Goutaland, "How intangibility affects perceived risk: The moderating role of knowledge and involvement," J. Services Marketing, vol. 17, no. 2, pp. 122-140, 2003.
47. J. Louviere, Analyzing Decision Making: Metric Conjoint Analysis. Beverly Hills, CA: Sage, 1988.
48. K. Lyytinen, L. Mathiassen, and J. Ropponen, "Attention shaping and software risk-A categorical analysis of four classical risk management approaches," Inf. Syst. Res., vol. 9, no. 3, pp. 233-255, 1998.
49. A. MacCormack, R. Verganti, and M. Iansiti, "Developing products on internet time: The anatomy of a flexible development process," Manag. Sci., vol. 47, no. 1, pp. 133-150, 2001.
50. C. Mann, "Why is software so bad," MIT Technol. Rev., pp. 33-38, Jul./Aug. 2002.
51. J. G. March and Z. Shapira, "Managerial perspectives on risk and risk taking," Manag. Sci., vol. 33, no. 11, pp. 1404-1418, 1987.
52. L. Martins and A. Kambil, "Looking back and thinking ahead: Effects of prior success on managers' interpretations of new information technologies," Acad. Manag. J., vol. 42, no. 6, pp. 652-661, 1999.
53. F. W. McFarlan, "Portfolio approach to information systems," Harvard Bus. Rev., vol. 59, no. 5, pp. 17-25, 1981.
54. W. Moore, "Levels of aggregation in conjoint analysis: An empirical comparasion," J. Marketing Res., vol. 17, pp. 516-523, 1980.
55. S. Nidumolu, "The effect of coordination and uncertainty on software project performance - Residual performance risk as an intervening variable," Inf. Syst. Res., vol. 6, no. 3, pp. 191-219, 1995.
56. R. Priem, "An application of metric conjoint analysis for the evaluation of top managers' individual strategic decision making processes: A research note," Strategic Manag. J., vol. 13, pp. 143-151, 1992.
57. J. Ropponen and K. Lyytinen, "Components of software development risk: How to address them? A project manager survey," IEEE Trans. Softw. Eng., vol. 26, no. 2, pp. 98-111, Feb. 2000.
58. I. Rus and M. Lindvall, "Knowledge management in software engineering," IEEE Softw. Mag., vol. 19, no. 3, pp. 26-38, May-Jun. 2002.
59. R. Schmidt, K. Lyytinen, M. Keil, and P. Cule, "Identifying software project risks: An international delphi study," J. Manag. Inf. Syst., vol. 14, no. 4, pp. 5-36, 2001.
60. K. Sengupta and T. Abdel-Hamid, "The impact of unreliable information on the management of software projects: A dynamic decision perspective," IEEE Trans. Syst., Man, Cybern., vol. 26, no. 2, pp. 177-189, Mar. 1996.
61. D. A. Shepherd, "Venture capitalists' assessment of new venture survival," Manag. Sci., vol. 45, no. 5, pp. 621-630, 1999.
62. G. Szulanski, "Exploring internal stickiness: Impediments to the transfer of best practice within the firm," Strategic Manag. J., vol. 17, no. 2, pp. 27-43, 1996.
63. A. Tiwana, "Beyond the black-box: Knowledge overlaps in software outsourcing," IEEE Softw. Mag., vol. 21, no. 5, pp. 51-58, Sep.-Oct. 2004.
64. A. Tiwana and M. Keil, "The one minute risk assessment tool," Commun. ACM, vol. 47, no. 11, pp. 73-77, 2004.
65. A. Tiwana and E. McLean, "Managing the unexpected: The tightrope to E-business project success," Commun. ACM, vol. 46, no. 12, pp. 345-350, 2003.
66. A. Tiwana and E. R. McLean, "Expertise integration and creativity in information systems development," J. Manag. Inf. Syst., vol. 22, no. 1, pp. 13-43, 2005.
67. C. Trumbo, "Information processing and risk perception: An adaptation of the heuristic-symantic model," J. Commun., vol. 52, no. 2, pp. 367-382, 2002.
68. B. Tyler and H. Steensma, "Evaluating technological collaborative opportunities: A cognitive modeling perspective," Strategic Manag. J. (Special Issue), vol. 16, no., pp. 43-70, 1995.
69. J. Vancouver and E. Morrison, "Feedback inquiry: The effect of source attributions and individual differences," Organizational Behav. Hum. Decision Processes, vol. 62, pp. 276-285, 1995.
70. I. Vessey and S. Conger, "Learning to specify information requirements: The relationship between application and methodology," J. Manag. Inf. Syst., vol. 10, no. 2, pp. 177-201, 1993.
71. L. Wallace, M. Keil, and A. Rai, "How software project risk affects project performance: An investigation of the dimensions of risk and an exploratory model," Decision Sci., vol. 35, no. 2, pp. 289-322, 2004.
72. R. W. Zmud, "Management of large software development efforts," MIS Quart., pp. 45-55, 1980.