在固定預算與時間限制下，資訊系統開發專案的失敗率一直相當高。資訊專案團隊通常由不同利益團體的成員共同組成，因此，成功整合團隊內部分歧的目的、塑造團結的氣氛，成為影響專案最終績效的重要關鍵。在此篇研究中，我們試圖利用「專案團隊夥伴的事前互動」來打破團隊成員間的藩籬，創造團隊合作的驅動因子。使用者需求的不確定性經常出現在整個資訊系統開發的過程裡，頻繁的溝通亦相對提高了發生衝突的機會。因此，需求分析是在系統開發過程中是必要的步驟，且需要仰賴使用者與資訊部門人員一同完成。本研究將針對台灣公司做實證研究，探討資訊系統專案開發過程中，團隊夥伴事前互動、需求不確定性、人員衝突和資訊專案績效的關係。
本研究的結果顯示：(1) 專案團隊夥伴的事前互動可以有效降低需求不確定性； (2) 需求不確定性對資訊專案績效有負面影響； (3)需求不確定性與人員衝突有顯著的正向關係； (4) 專案團隊夥伴的事前互動與人員衝突無顯著關係； (5) 人員衝突與資訊專案績效的直接負面影響不顯著。
在實際工作的應用上，我們建議專案管理者可增加團隊成員在專案開始之前的互動機會與頻率，藉此建立良好的互動機制與溝通管道，降低使用者需求不確定的發生機率，以提高資訊專案績效，並同時減少衝突的發生。

The budget and time overrun of information system development (ISD) project have been a major concern for the corporate managers. Such mismanagement often causes high failure rate of IS projects. The project team is composed of multiple parties which have different interests and purposes. Therefore the coherent purpose and an agreeable climate for the cooperation would have critical impact on the eventual result of the project. Pre-project partnering was adopted to create collaborative atmosphere among the project team members. Requirement uncertainty also pervades ISD stages, and easily causes the conflict as a result of frequently interaction. For that reason, requirement analysis is needed to be conducted by users and IS staff during ISD. In this study, we try to find the causal relationship among the pre-project partnering, requirement uncertainty, interpersonal conflict and project performance according to empirical data.
Our data collected from the corporation of Taiwan. The research findings showed: (1) pre-project partnering could reduce the requirement uncertainty effectively; (2) requirement uncertainty has negative impact to the project performance; (3) requirement uncertainty has positive effect on interpersonal conflict; (4) The relationship between pre-project partnering and interpersonal conflict is not significant; (5) the relationship between interpersonal conflict and project performance is not significant.
As for the implications for management, we suggest to establish an effective communication channel and interaction platform through pre-project partnering activities. Increasing the opportunities to interact with each other before the project begins would help to do the requirement analysis well. The lower the requirement uncertainty results in the better eventual project performance and the lower of interpersonal conflict.

References：
Associated General Contractors of America, Partnering: A Concept for Success, Washington, DC, 1991
Argote, L. Input Uncertainty and Organizational Coordination in Hospital Emergency Units. Administrative Science Quarterly, 27, 1982, pp. 420-434
Barki H. and Hartwick, J. User Participation, Conflict, and Conflict Resolution： The Mediating Roles of Influence. Information Systems Research, Dec 1994; Vol 5, Iss 4; pp. 422-438
Barki H. and Hartwick, J. Interpersonal Conflict and Its Management in Information System Development. MIS Quarterly, June 2001, Vol. 25 No. 2, pp. 195-228
Bentler PM and Chou CP, Practical issues in structure modeling. Sociological Methods and Research, 16 August 1987, pp78-117
Boehm, B. W. Software Risk Management. Los Alamitos, CA：IEEE Computer Society Press, 1989
Cowan, C., Gray, C. and Larson, E. Project partnering. Project Management Journal, Vol. 22, No. 4, 1992, pp. 5-11
Crowley, L. G., and Karim, M. A. Conceptual Model of Partnering. Journal of Management in Engineering, September/October, 1995
Davis, G. B. Strategies for information requirements determination. IBM Systems Journal, 21 (1), 1982, pp. 3-30
Fazlollahi, B., Tanniru, M. R. Selecting a requirement determination methodology-contingency model approach revisited. Information and Management, 21, 1991, pp. 291-303
Franz, C. R., and Robey, D. An Investigation of User-Led System Design: Rational and Political Perspectives. Communication of the ACM, (27:12), 1984, pp. 1202-1209
Gatewood, R. D. and Field, H. S., Human Resource Selection 2nd Ed., Chicago, IL, Dryden Press, 1990
Gibbs, W.W. Software’s chronic crisis. Scientific American, September 1994, pp.86-95
Glass, R.L. Software Runaways. New York：Prentice-Hall，1998
Glasser, J. Organizational Aspects of System Faiure：A Case Study at the L.A. Police Department. Proceedings of the Second International Conference on Information Systems, C.A.Ross(ed.), Cambridge, MA, 1981, pp.233-245
Goodman, P.S., Ravlin, E., and Schminke, M. (1987). Understanding groups in organizations. In Cumming, L.L. and Staw, B.M. (eds.). Reasearch in Organizational Behavior. Greenwich, CN: JAI Press, pp121-173
Gransberg, D. D., Reynolds, H. L., and Boyd J. Measuring partnered project performance. Cost Engineering, Vol. 41/No. 10, October 1999
Henderson, J.C. and Lee, S. Managing I/S design teams: A control theories perspective. Management Science, 38(6), 1992, pp. 757-777.
Hocker, J. L. and Wilmot, W. W. Interpersonal Conflict (2nd ed.). William C. Brown, Dubuque, IA, 1985
Jiang, J. J., Klein, G. and Chen, H. G. The relative influence of IS project implementation policies and project leadership on eventual outcomes. Project Management Journal, Sylva; Sep 2001; Vol. 32, Iss. 3; pp. 49-55
Jiang, J. J., Chen, E. and Klein, G. The importance of building a foundation for user involvement in information system projects. Project Management Journal, Sylva; Mar 2002; Vol. 33, Iss. 1; pp. 20-26
Jiang, J. J., Klein, G. And Discenza, R. Pre-project partnering impact on an information system, project team and project manager. European Journal of Information Systems, Vol. 11, 2002, pp. 86-97
Klein, G.., Jiang, J., and Boyd, M. (1999). Building a case for consonance. Proceedings of the Third International Conference on Business Information Systems. London: Springer-Verlag
Kolb, D. M. and Sheppard B. H. Do Managers Mediate, or Even Arbitrate? Negotiation Journal, 1(1985), pp. 379-388
Larson, E. Partnering on Construction Projects：A Study of the relationship between partnering Activities and Project Success. IEEE Transactions on Engineering Management, Vol. 44, No. 2, May 1997
Lewis, J. Fundamentals of Project Management. Amacom Books, 1995.
Lucas, H. C. “Alternative Structures for the Management of Information Processing” in Goldberg and Lorin (Eds.), On the Economics of Information Processing, Vol.2, Wiley-InterScience, New York, 1982
Milliken, F.J. Three types of perceived uncertainty about the environment: state, effect and response uncertainty, Academy of Management Review, 12, 1(1987), pp133-143
Moore, C., Mosley, D., and Slagle, M. Partnering：Guidelines for Win-Win Project Management. Project Management Journal，23, No.1, March 1992, pp. 18-21
Nidumolu, S. R. The effect of coordination and uncertainty on software project performance：Residual Performance Risks as an Intervening Variable. Information Systems Research，September 1995, pp. 191-219
Nidumolu, S. R. A comparison of the structural contingency and risk-based perspectives on coordination in software-development projects, Journal of Management Information Systems, Fall 1996, Vol. 13, No2, pp77-113
Nidumolu, S. R. Standardization, requirements uncertainty and software project performance. Information & Management, 31 (1996), pp. 135-150
Pressman, R. S. Software Engineering：A Practitioner’s Approach (3rd Ed.), McGraw-Hill Inc., New York, 1992
Pruitt, D. G. and Rubin, J. Z. Social Conflict, Random House. New York, NY, 1986
Putnam, L. L. and Wilson, C. Communicative Strategies in Organizational Conflict：Reliability and Validity of a Measurement Scale. Communication Yearbook 6, Sage Publications, Newbury Park, CA, 1982, pp. 629-652
Robey, D., Farrow, D. L. User Involvement in Information System Development: A Conflict Model and Empirical Test. Management Science, Vol.28, No.1, January 1982
Robey, D., Farrow, D. L., Franz, C. R. Group process and conflict in system development. Management Science, 35, 10(1989), pp. 1172-1191
Robey, D., Smith, L. A., Vijayasarathy, L. R. Perceptions of Conflict and Success in Information System Development Projects. Journal of Management Information System, Summer 1993, Vol. 10, No. 1, pp. 123-139
Schmidt, S.M. and Kochan, T. A. Conflict: Toward Conceptual Clarity. Administrative Science Quarterly, 17 (1972), pp359-370
Smith, H. A. and McKeen, J. D. Computerization and Management：A Study of Conflict and Change. Information & Management, 22 (1992), pp. 53-64
Thamhain, H.J. and Wilemon, D.L. Building high performing engineering project teams. IEEE Transactions on Engineering Management, EM-34 (3), 1987 pp.130-137
Thayer, R. H. and Lehman, J. H. Software engineering project management：a survey concerning U.S. Aerospace industry management of software development projects. Software Management (Reifer, D.J., Ed.), IEEE Computer Society Press, Washington, D.C., 1979
Thomas, K. W. Conflict and Conflict Management: Reflections and Update. Journal of Organizational Behavior, (13), 1992a, pp265-274
Tjosvold D The Conflict – Positive Organization, Addison Wesley, Reading
Tuner, J. A. A Comparison of the Process of Knowledge Elicitation with that of Information Requirements Determination. Challenges and Strategies fro Research in Systems Development (Cotterman, W. W. and Senn, J. A. Eds.)，John Wiley & Sons Ltd., New York, 1992
Wall, J. A. Jr. and Callister, R. R. Conflict and its Management. Journal of Management (21:3), 1995, pp. 515-558
Wilson Jr., R. A., Songer, A. D., Diekmann, J. Partnering: More than a workshop, A catalyst for Change, Journal of management in Engineering, September/October, 1995
Zmud, R. W. Management of large software development efforts. MIS Quarterly, September 1980, pp. 45-55