探討專案風險察覺之前置因子

Exploring Antecedents of Risk Perception on IS Project

徐維澤(Wei-Tse Hsu)

指導教授 ： 劉俞志

元智大學/資訊學院/資訊管理學系/碩士(2011年)

https://doi.org/10.6838/YZU.2011.00282

摘要

風險察覺在軟體專案中是一個重要的概念，因為對於專案經理而言，能有準確風險察覺能力，可避免持續一些很可能會失敗的專案。本文想要探討專案複雜度與任務的專業程度對於風險察覺的影響，並提供一個更為準確的方法，來探討專案經理的風險察覺能力與專案績效之間的關係。先前文獻指出專案複雜度對專案績效有負面影響的，並證實風險察覺影響會專案績效，但根據本研究結果卻發現，專案複雜度不會影響風險察覺，任務性的專業程度會顯著影響風險察覺與專案績效的產品績效，卻不影響專案的流程績效。此發現非常有趣，因為這意味專案的流程績效不直接受專案經理之任務性專業程度高低影響，而是取決於專案經理的風險察覺能力。

關鍵字

風險察覺 ； 專案複雜度 ； 專業程度 ； 專案績效 ； 軟體專案

並列摘要

Risk perception is a very important concept in software project. Project managers will stop putting effort into projects that might fail or adopt appropriate strategy at an earlier stage to avoid fail if having accurate risk perception. This study focuses on how project complexity and expertise will influence risk perception and provides more accurate measures to explore the relationship between project managers’ risk perception and project performance. Some literature indicated that project complexity does have a negative effect on project performance and that risk perception did affect project performance. However, the results of our data analysis show that project complexity would not affect risk perception. And, task-based expertise have a significant effect on risk perception and the product performance for software project, but not process performance for software project. These findings indicate project performance is directly affected by project manager’s risk perceptions, rather than task-based expertise of software developers.

並列關鍵字

software project ； risk perception ； project complexity ； expertise ； project performance

參考文獻

[3] Anderson, H., Narshimhan, R., (1979), "Assessing project implementation risk: a methodological approach", Management Science, 25 512-521.

[4] Baird, I. S., Thomas, H. , (1985), "Toward a contingency model of strategic risk taking", Academy of Management Review, 10 230-243

[5] Bannerman, P.L., (2008), "Risk and risk management in software projects: a reassessment", The Journal of Systems and Software, 8(1) 2118-2133

[6] Barki, H., Hartwick, J., (2001), "Interpersonal Conflict and Its Management in Information System Development", MIS Quarterly, 25(2) 195-228

[7] Barki, H., Rivard, S., Talbot, J., (1993), "Toward an Assessment of Software Development Risk", Journal of Management information Systems, 10(2) 203-225