Publications-Theses

Article View/Open

Publication Export

Google ScholarTM

NCCU Library

Citation Infomation

Related Publications in TAIR

題名 軟體專案特性對專案管理與專案間互動的影響之研究-以趨勢科技之雲端運算專案為例
Software project characteristics on project management and project the impact of interaction study:the case of Trend Micro Inc.
作者 陳彥甫
貢獻者 吳豐祥
陳彥甫
關鍵詞 雲端運算
專案特性
專案管理
專案間互動
軟體開發
趨勢科技
Cloud Computing
Project characteristics
Project Management
Interaction between projects
Software of development
Trend Micro
日期 2009
上傳時間 4-Sep-2013 11:16:50 (UTC+8)
摘要 隨著商業環境的快速變動,企業為因應市場快速變化,管理階層傾向於將專案規模縮小、目標明確來定義專案的範圍,以助於專案的執行,因此企業大多會執行一個以上的專案,然而專案彼此之間或多或少都會有些關聯與互動,良好的互動關係對於專案執行成效與企業均有其正面助益,因此本研究的目的在探討軟體專案特性對專案管理與專案間互動的影響之研究。
本研究以全球防毒軟體領導廠商-趨勢科技為例,其獨特的企業文化和指標性的企業管理模式,皆已成為國際型企業的典範。因此探討該公司運用雲端運算技術所成立的兩個專案進行研究,藉以探討專案特性、專案管理、專案間互動之關係。本研究經由個案訪談以及次級資料的分析探討,本研究之發現如下:
1.企業在執行軟體專案管理時,充分授權有助於激進式創新專案的開發進行。
2.領導者在軟體專案管理各階段所扮演的角色不同。當技術為外部來源時,領導者需要扮演協調溝通角色;當技術為內部來源時,領導者需要扮演技術支援角色。
3.企業在執行軟體專案管理時,會用師徒制來進行隱性知識的傳承;並利用文件管理系統來管理外顯知識。
4.當激進式創新的產品開發專案運用外部技術來源時,提供員工自我學習的空間,並透過知識分享討論會、知識管理系統、非正式溝通的多個群體協調活動,有助於專案間互動。
In order to adapt to rapidly changing markets, cooperate managers tend to downsize the scales and define specific goals of projects for effective execution. Therefore, cooperates simultaneously deal with multiple projects which are inter-connected to each other. Good interactions benefit both projects and cooperate itself. Hence, the objective of this study is to investigate how the characteristics of software projects influence the managements and interactions of projects.
The study subject is Trend Macro Incorporated, the world-wide leading company of antivirus software. Its unique culture and foremost management style have become the model example of international companies. Therefore, this study investigated two projects of this company, which apply cloud computing, to explore the relationships of the characteristics, management and interactions within and between projects. By case interview and secondary databases, the main findings of this study are listed below.
1.Enterprise in the implementation of software project management, the fully authorized to contribute to the development of radical innovation projects carried out.
2.Leader in software project management role of the different stages. When the technology to external sources, the leaders need to play the role of coordination and communication. When the technology for internal sources, leaders need to play a technical support role.
3.Enterprise in the implementation of software project management, we will use the apprenticeship system to carry out transmission of tacit knowledge; and to use document management system to manage explicit knowledge.
4.When the radical innovation of the product development project the use of external technology sources, to provide space for staff self-learning and knowledge sharing through seminars, knowledge management systems, informal communication between the various groups of coordination activities to facilitate interaction between projects.
參考文獻 一、中文部分
<碩博士論文>
1.方世杰(1996),企業技術交易模式影響因素之研究,國立台灣大學商學研究所博士論文。
2.林國文(1997),產品設計開發過程中企業設計溝通模式與設計品質之相關性研究,國立成功大學工業設計研究所碩士論文。
3.陳恩航(1993),影響專案計畫成效之關鍵因素研究,交通大學管理科學研究所研碩士論文。
4.簡瑞蓮(民89),漸進式和急遽式專案主持人管理角色與新產品開發績效關係之研究,中央大學企業管理研究所碩士論文。
5.黃敏萍(2000),跨功能任務團隊之結構與效能-任務特性與社會系絡之影響,國立台灣大學商學研究所博士論文。
6.曹中仁(1990),新產品發展過程中,研究發展與行銷部門整合因素之研究,國立台灣大學商學研究所碩士論文。
7.吳健鑫(2002),我國中小型資訊軟體業技術知識特質與創新行為之研究,國立政治大學碩士論文。
8.董雅菁(2006),跨功能研發團隊中溝通模式對設計知識整合之影響,大同大學工業設計研究所碩士論文。
9.蘇志遠(2008),專案經理領導風格與知識整合對專案績效的影響—以專案特性為調節變數,銘傳大學資訊管理學系碩士在職專班碩士論文。

<期刊、書籍>
10.季延平、郭鴻志(1995),系統分析與設計:由自動化到企業再造,華泰出版社。
11.賴士葆(1997),研究發展規劃、研發與行銷之介面管理,科技管理。
12.林文鵬(1998),「策略聯盟價值、組織特性與技術創新績效關係之研究」,國立屏東商業專科學校學報,第5期,頁35-52。
13.詹碧綢(2003),「影響專案成功關鍵因素的研究-以網路通訊設備服務業為例」,品質月刊,台北,民國92年5月。
14.陳冠年(2003),「專案管理在圖書館之應用」,中華民國圖書館學會會報,第74期,第185-201頁,台北,民國94年6月。
15.林欽榮(2004),組織理論與管理,揚智文化事業股份有限公司。
16.陳振遠、陳振田譯,Philip Kotler(1990),行銷管理,五南圖書出版公司。
17.鍾啟東(2006),「成功之專案管理」,臺肥季刊,第47期第4卷,第33-37 頁,台北市,民國95年12月。
二、英文部分
1.Allen, T. J. & Hauptman, O. (1987), The Influence of Communication Technologies on Organizational Structure:A Conceptual Model for Future Research, Oxford University Press, Oxford, pp.475-483.
2.Archibald, R. B. (1981), The Implementation of Project Management: the Professional’s Handbook, Massachusetts, Addison-Wesley Publishing, U.S.A.
3.Archibald, C. (1981), Book Review: Democracy and Distrust, 94 Harvard Law Review, pp.700-717.
4.Baldwin, T. T. & Ford, J. K. (1988), “Transfer of Training: A Review and Directions for Future Research”, Personnel Psychology, Vol.41, pp.63-105.
5.Barczak, G. & Wilemon, D. (1989), “Leadership Differences in New Product Development Teams”, Journal of Product Innovation Management, Vol.6, pp.259-267.
6.Bergen, S. A. & Pearson, A. W. (1983), “Project Management and Innovation in the Scientific Instrument Industry”, IEEE Transactions on Engineering Management, No.4, pp.194-199.
7.Booz, Allen & Hamilton (1982), New Product Management For The 1980’s, NY: Booz-Allen and Hamilton, Inc.
8.Bostrom, R. P. (1984), “Development of Computer-Based Information Systems: A Communication Perspective”, Computer Personnel, Vol.9(4), pp.254-258.
9.Bubshait, A. A. & Farooq, G. (1999), “Team Building And Project Success”, Cost Engineering, Vol.41(7), pp.25-27
10.Clark, K. B. & Wheelwright, S. C. (1993), Managing New Product and Process Development, New York, Free Press.
11.Cleland, D. I. & King, W. R. (1983), System Analysis and Project Management, 3rd ed., p45.
12.Cooper, R. G. (1983), “Process Model for Industrial New Product Development”, IEEE Transactions on Engineering Management, Vol.30(1), pp.2-11.
13.Crawford, C. Merle (1991), New Product Management 3rd ed.
14.Danila S. (1989), “Technological Innovation Strategies”, Engineering Management Journal, Vol.1, pp.17-24.
15.Davis (1972), Human Relations at Work, The Dynamics of Organizational Behavior, pp.42-48.
16.Drucker, P. F. (1993), Post-Capital Society, Harper Collins. Gilbert, Myrna & Gordey-Hayes, Martyn(1996), ”Understanding The Process of Knowledge Transfer to Achieve Successful Technological Innovation”, Tcehnovation, Vol.16(6), pp.365-385.
17.Davenport, T. H. & Prusak, L. (1998), Working Knowledge: How Organizations Manage What They Know, Boston: Harvard College Press.
18.Fife, D. (1987), “Injuries and Deaths among Elderly Persons”, American Journal of Epidemiology, 126(5), pp.936-941.
19.Ford, R. C. & McLaughlin, F. C. (1992), “Successful Project Teams: a Study of MIS Managers”, IEEE Transactions on Engineering Management, Vol.39, pp.312-317.
20.Fleishman, E. A. (1973), Twenty Years of Consideration And Structure, In E. A. Fleishman & J. G.Hunt (Eds), Current Developments In the Study of Leadership, Carbondale:Southern Illinois University Press.
21.Friar, J. & Horwitch, M. (1986), The Emergence of Technology Strategy: A New Dimension of Strategic Management, Technology in the Modern Corporation: A Strategic Perspective, Pergamon Press Inc., New York.
22.Gobeli, D. H. & Brown, D.J. (1987), “Analyzing Product Innovations”, Research Management, Vol.30(4), pp.25-31.
23.Granstrand, et al. (1992), “External Technology Acquisition in Large Multi-Technology Corporations”, R&D Management, Vol.22(2), pp.111-133.
24.Hemphill, J. K. & Coons, A. E. (1950), Leadership Behavior Description, Personnel Research Board, Ohio State University.
25.Hedlund, G. (1994), “A Model of Knowledge Management and The M-Form Corporation”, Strategic Management Journal, Vol.15, pp.73-90.
26.Kaiser, K. & Bostrom, R. P. (1982), “Personality Characteristics of MIS Project Teams: An Empirical Study and Action-Research Design”, MIS Quarterly, pp.43-60.
27.Kerzner, H. (1984), Project Management: A System Approach to Planning, Scheduling and Controlling, Van Nostrand Reinhold Co. Inc.
28.Kotler, P. (1994), Marketing Management - Analysis, Planning, Implementation and Control, 8th ed., Englewood Cliffs:Prentice-Hall, pp.174.
29.Kuczmarski, T. D. (1992), Managing New Product: The Power of Innovation, 2nd ed., Prentice-Hall, Englewood Cliffs, pp.33-36.
30.Lee, M. & Om, K. (1994), “A Conceptual Framework of Technological Innovation Management”, Technovation, Vol.14(1), pp.7-16.
31.Nicholas, J. M. (1990), Managing Business and Engineering Projects, NJ: Prentice-Hall.
32.Nonaka, I. & Takeuchi, H. (1995), The Knowledge-Creating Company, Oxford University Press, Inc.
33.Rakos, J. J. (1990), Software Project Management for Small To Medium Sized Projects, Englewood Cliffs, N. J., Prentice-Hall.
34.Rauch, C. F. & Behling, O. (1984), Functionalism: Basis For An Alternate Approach To The Study Of Leadership. In J. G. Hunt, D. M. Hosking, C. A. Schriesheim, & R.Stewart(Eds.), Leaders and managers: International Perspectives on Managerial Behavior and Leadership. Elmsford, NY: Pergamon Press, pp.45-62.
35.Stanley, B. B., Aldag, R. J. & Cunningham, W. H. (1993), Business In A Changing World, 3rd ed., pp.371-391.
36.Shenhar, A. J. & Wideman, R. M. (2000), Optimizing Project Success by Matching PM Style With Project Type, (available online at http://www.pmforum.org).
37.Terry, G. R. (1960), Principles of Management, 3rd ed., Homewood III: Richard D. Irwin. Pattern, pp.95-101.
38.Tuman, G. J. (1983), Development and Implementation of Effective Project Management Information and Control Systems, Project Management Hand Book.
39.Jessup, H. R. (1990), “New Roles in Team Leadership”, Training & Development Journal, Vol.44(11), pp.79-83.
40.Kirkpatrick, S. A. & Locke, E. A. (1991), “Leadership: Do Traits Really Matter?”, Academy of Management Executive, Vol.5(2), pp.48.
41.Moenaert, R. K. (1995), “CR&D/Marketing Communication During The FuzzyFront-End”, IEEE Transactions on Engineering Management, Vol.42(3), pp.243-258.
42.Munns, A. K. & Bjeirmi, B. F. (1996), “The Role of Project Management in Achieving Project Success”, International Journal of Project Management, Vol.14(2), pp.81-87.
43.Pinto, J. K. & Slevin, D. P. (1988), “Project Success: Definition and Measurement Techniques”, Project Management Journal, Vol.19(1), pp.67-72.
44.Ring, P. S. & Van de Ven, A. H. (1994), “Developmental Process of Cooperative Interorganizational Relationships”, Academy of Management Review, Vol.19(1), pp.90-118.
45.Roessner, D. (1989), “Evaluation Government Innovation Programmes: Lessons From The U.S. Experience”, Research Policy, Vol.18(6), pp.343-359.
46.Ronkainen, I. A. (1985), “Criteria Changes across Product Development Stages”, Industrial Marketing Management, Vol.14, pp.171-178.
47.Sheth, Jagdish N. & Atul Parvatiyer (1995), “Relationship Marketing in Consumer Markets: Antecedents and Consequences”, Journal of the Academy of Marketing Science, Fall, pp.255-271.
48.Shockley, R. & Holt, R. (1983), “A Behavioral Investigation of Supplier Differentiation in The Market For Audit Services”, Journal of Accounting Research, Vol.21(Autumn), pp.545-564.
49.Song, X. M. & Montoya-Weiss, M. M. (1998b), “Critical Development Activities for Really New Versus Incremental Products”, Journal of Product Innovation Management, Vol.15, pp.124-135.
50.Teece, D. J., Rumelt, R., Dosi, G. & Winter, S. (1994), “The Dynamic Capabilities of Firms: An Introduction”, Industrial and Corporate Change, Vol.3( 3), pp.537-556.
51.Utler, W. G. (1991), “Acquiring Technology From Outside”, Research Technology Management, Vol.34(3), pp.11-18.
52.Van de Ven, A. H., Delbecq, A. L. & Koenig, R. Jr. (1976), “Determinants of Coordination Modes Within Organizations”, American Sociological Review, pp.322-338.
53.Veryzer, R. W. (1998), “Discontinuous Innovation and the New Product Development Process”, Journal Product Innovation Management, Vol.15, pp.304-321.
54.Whitten, J. L. & Bentley, L. D. (1998), “Project Manage Dictionary of Terms”, International Journal of Project Management, Vol.38, pp.56-78.
55.Wheelwright, S. C. & Clark, K. B. (1992), Revolutionizing Product Development, New York, The Free Press, pp.165-187.
56.Zimmerer, T. & Yasin, M. (1998), “The Leadership Profile of American Project Managers”, Project Management Journal, Vol.29(1), pp.31–38.
描述 碩士
國立政治大學
科技管理研究所
96359014
98
資料來源 http://thesis.lib.nccu.edu.tw/record/#G0096359014
資料類型 thesis
dc.contributor.advisor 吳豐祥zh_TW
dc.contributor.author (Authors) 陳彥甫zh_TW
dc.creator (作者) 陳彥甫zh_TW
dc.date (日期) 2009en_US
dc.date.accessioned 4-Sep-2013 11:16:50 (UTC+8)-
dc.date.available 4-Sep-2013 11:16:50 (UTC+8)-
dc.date.issued (上傳時間) 4-Sep-2013 11:16:50 (UTC+8)-
dc.identifier (Other Identifiers) G0096359014en_US
dc.identifier.uri (URI) http://nccur.lib.nccu.edu.tw/handle/140.119/59990-
dc.description (描述) 碩士zh_TW
dc.description (描述) 國立政治大學zh_TW
dc.description (描述) 科技管理研究所zh_TW
dc.description (描述) 96359014zh_TW
dc.description (描述) 98zh_TW
dc.description.abstract (摘要) 隨著商業環境的快速變動,企業為因應市場快速變化,管理階層傾向於將專案規模縮小、目標明確來定義專案的範圍,以助於專案的執行,因此企業大多會執行一個以上的專案,然而專案彼此之間或多或少都會有些關聯與互動,良好的互動關係對於專案執行成效與企業均有其正面助益,因此本研究的目的在探討軟體專案特性對專案管理與專案間互動的影響之研究。
本研究以全球防毒軟體領導廠商-趨勢科技為例,其獨特的企業文化和指標性的企業管理模式,皆已成為國際型企業的典範。因此探討該公司運用雲端運算技術所成立的兩個專案進行研究,藉以探討專案特性、專案管理、專案間互動之關係。本研究經由個案訪談以及次級資料的分析探討,本研究之發現如下:
1.企業在執行軟體專案管理時,充分授權有助於激進式創新專案的開發進行。
2.領導者在軟體專案管理各階段所扮演的角色不同。當技術為外部來源時,領導者需要扮演協調溝通角色;當技術為內部來源時,領導者需要扮演技術支援角色。
3.企業在執行軟體專案管理時,會用師徒制來進行隱性知識的傳承;並利用文件管理系統來管理外顯知識。
4.當激進式創新的產品開發專案運用外部技術來源時,提供員工自我學習的空間,並透過知識分享討論會、知識管理系統、非正式溝通的多個群體協調活動,有助於專案間互動。
zh_TW
dc.description.abstract (摘要) In order to adapt to rapidly changing markets, cooperate managers tend to downsize the scales and define specific goals of projects for effective execution. Therefore, cooperates simultaneously deal with multiple projects which are inter-connected to each other. Good interactions benefit both projects and cooperate itself. Hence, the objective of this study is to investigate how the characteristics of software projects influence the managements and interactions of projects.
The study subject is Trend Macro Incorporated, the world-wide leading company of antivirus software. Its unique culture and foremost management style have become the model example of international companies. Therefore, this study investigated two projects of this company, which apply cloud computing, to explore the relationships of the characteristics, management and interactions within and between projects. By case interview and secondary databases, the main findings of this study are listed below.
1.Enterprise in the implementation of software project management, the fully authorized to contribute to the development of radical innovation projects carried out.
2.Leader in software project management role of the different stages. When the technology to external sources, the leaders need to play the role of coordination and communication. When the technology for internal sources, leaders need to play a technical support role.
3.Enterprise in the implementation of software project management, we will use the apprenticeship system to carry out transmission of tacit knowledge; and to use document management system to manage explicit knowledge.
4.When the radical innovation of the product development project the use of external technology sources, to provide space for staff self-learning and knowledge sharing through seminars, knowledge management systems, informal communication between the various groups of coordination activities to facilitate interaction between projects.
en_US
dc.description.tableofcontents 第一章 緒論 ---------------------------------------------01
第一節 研究背景與動機 ------------------------------------01
一、研究背景 -------------------------------------------01
二、研究動機 -------------------------------------------03
第二節 研究目的 -----------------------------------------04
第三節 研究流程 -----------------------------------------04
第四節 論文架構 -----------------------------------------05
第二章 文獻探討 -----------------------------------------06
第一節 專案特性 -----------------------------------------06
一、專案定義 -------------------------------------------06
二、專案目標 -------------------------------------------07
三、專案組織 -------------------------------------------08
四、專案類型 -------------------------------------------10
五、技術取得 -------------------------------------------13
六、小結 ----------------------------------------------17
第二節 專案管理 -----------------------------------------18
一、專案管理定義 ---------------------------------------18
二、開發流程之階段歸納 ---------------------------------19
三、投入人力 -------------------------------------------25
四、領導者扮演角色 -------------------------------------26
五、知識創造 -------------------------------------------31
六、小結 -----------------------------------------------34
第三節 溝通協調 -----------------------------------------35
一、協調模式 -------------------------------------------35
二、溝通方式 -------------------------------------------36
三、小結 -----------------------------------------------37
第四節 本章小結 -----------------------------------------38
第三章 研究方法 -----------------------------------------39
第一節 研究架構 -----------------------------------------39
第二節 研究變項說明 -------------------------------------40
一、專案特性 -------------------------------------------40
二、專案管理 -------------------------------------------42
三、專案間互動 -----------------------------------------43
第三節 研究設計與資料蒐集 --------------------------------46
一、研究方法 -------------------------------------------46
二、資料蒐集方法 ---------------------------------------46
三、研究對象 -------------------------------------------46
第四節 研究限制 ----------------------------------------48
第四章 個案研究 ----------------------------------------49
第一節 個案背景介紹 -------------------------------------49
一、趨勢科技的發展沿革 ---------------------------------49
二、雲端運算 -------------------------------------------51
三、主動式雲端截毒技術 ---------------------------------56
四、Cloud Node與Cloud Lego專案 --------------------------58
第二節 專案特性 -----------------------------------------63
一、專案目標 -------------------------------------------63
二、專案組織 -------------------------------------------66
三、專案類型 -------------------------------------------67
四、技術來源 -------------------------------------------68
五、專案特性之彙整分析 ----------------------------------69
第三節 專案管理 ----------------------------------------71
一、投入人力 -------------------------------------------71
二、領導者扮演角色 --------------------------------------72
三、知識創造 -------------------------------------------74
四、專案管理之彙整分析 -----------------------------------75
第四節 專案間互動 ---------------------------------------77
一、協調模式 -------------------------------------------77
二、溝通方式 -------------------------------------------78
三、專案間互動之彙整分析 ---------------------------------78
第五章 研究發現與討論 -----------------------------------80
第一節 專案特性與專案管理的關係 ----------------------------80
第二節 專案特性與組織間互動的關係 --------------------------91
第六章 結論與建議 ----------------------------------------95
第一節 研究結論 -----------------------------------------95
第二節 研究建議 -----------------------------------------97
一、實務上的建議 ---------------------------------------97
二、後續研究建議 ---------------------------------------98

參考文獻 ----------------------------------------------99
zh_TW
dc.format.extent 7057815 bytes-
dc.format.mimetype application/pdf-
dc.language.iso en_US-
dc.source.uri (資料來源) http://thesis.lib.nccu.edu.tw/record/#G0096359014en_US
dc.subject (關鍵詞) 雲端運算zh_TW
dc.subject (關鍵詞) 專案特性zh_TW
dc.subject (關鍵詞) 專案管理zh_TW
dc.subject (關鍵詞) 專案間互動zh_TW
dc.subject (關鍵詞) 軟體開發zh_TW
dc.subject (關鍵詞) 趨勢科技zh_TW
dc.subject (關鍵詞) Cloud Computingen_US
dc.subject (關鍵詞) Project characteristicsen_US
dc.subject (關鍵詞) Project Managementen_US
dc.subject (關鍵詞) Interaction between projectsen_US
dc.subject (關鍵詞) Software of developmenten_US
dc.subject (關鍵詞) Trend Microen_US
dc.title (題名) 軟體專案特性對專案管理與專案間互動的影響之研究-以趨勢科技之雲端運算專案為例zh_TW
dc.title (題名) Software project characteristics on project management and project the impact of interaction study:the case of Trend Micro Inc.en_US
dc.type (資料類型) thesisen
dc.relation.reference (參考文獻) 一、中文部分
<碩博士論文>
1.方世杰(1996),企業技術交易模式影響因素之研究,國立台灣大學商學研究所博士論文。
2.林國文(1997),產品設計開發過程中企業設計溝通模式與設計品質之相關性研究,國立成功大學工業設計研究所碩士論文。
3.陳恩航(1993),影響專案計畫成效之關鍵因素研究,交通大學管理科學研究所研碩士論文。
4.簡瑞蓮(民89),漸進式和急遽式專案主持人管理角色與新產品開發績效關係之研究,中央大學企業管理研究所碩士論文。
5.黃敏萍(2000),跨功能任務團隊之結構與效能-任務特性與社會系絡之影響,國立台灣大學商學研究所博士論文。
6.曹中仁(1990),新產品發展過程中,研究發展與行銷部門整合因素之研究,國立台灣大學商學研究所碩士論文。
7.吳健鑫(2002),我國中小型資訊軟體業技術知識特質與創新行為之研究,國立政治大學碩士論文。
8.董雅菁(2006),跨功能研發團隊中溝通模式對設計知識整合之影響,大同大學工業設計研究所碩士論文。
9.蘇志遠(2008),專案經理領導風格與知識整合對專案績效的影響—以專案特性為調節變數,銘傳大學資訊管理學系碩士在職專班碩士論文。

<期刊、書籍>
10.季延平、郭鴻志(1995),系統分析與設計:由自動化到企業再造,華泰出版社。
11.賴士葆(1997),研究發展規劃、研發與行銷之介面管理,科技管理。
12.林文鵬(1998),「策略聯盟價值、組織特性與技術創新績效關係之研究」,國立屏東商業專科學校學報,第5期,頁35-52。
13.詹碧綢(2003),「影響專案成功關鍵因素的研究-以網路通訊設備服務業為例」,品質月刊,台北,民國92年5月。
14.陳冠年(2003),「專案管理在圖書館之應用」,中華民國圖書館學會會報,第74期,第185-201頁,台北,民國94年6月。
15.林欽榮(2004),組織理論與管理,揚智文化事業股份有限公司。
16.陳振遠、陳振田譯,Philip Kotler(1990),行銷管理,五南圖書出版公司。
17.鍾啟東(2006),「成功之專案管理」,臺肥季刊,第47期第4卷,第33-37 頁,台北市,民國95年12月。
二、英文部分
1.Allen, T. J. & Hauptman, O. (1987), The Influence of Communication Technologies on Organizational Structure:A Conceptual Model for Future Research, Oxford University Press, Oxford, pp.475-483.
2.Archibald, R. B. (1981), The Implementation of Project Management: the Professional’s Handbook, Massachusetts, Addison-Wesley Publishing, U.S.A.
3.Archibald, C. (1981), Book Review: Democracy and Distrust, 94 Harvard Law Review, pp.700-717.
4.Baldwin, T. T. & Ford, J. K. (1988), “Transfer of Training: A Review and Directions for Future Research”, Personnel Psychology, Vol.41, pp.63-105.
5.Barczak, G. & Wilemon, D. (1989), “Leadership Differences in New Product Development Teams”, Journal of Product Innovation Management, Vol.6, pp.259-267.
6.Bergen, S. A. & Pearson, A. W. (1983), “Project Management and Innovation in the Scientific Instrument Industry”, IEEE Transactions on Engineering Management, No.4, pp.194-199.
7.Booz, Allen & Hamilton (1982), New Product Management For The 1980’s, NY: Booz-Allen and Hamilton, Inc.
8.Bostrom, R. P. (1984), “Development of Computer-Based Information Systems: A Communication Perspective”, Computer Personnel, Vol.9(4), pp.254-258.
9.Bubshait, A. A. & Farooq, G. (1999), “Team Building And Project Success”, Cost Engineering, Vol.41(7), pp.25-27
10.Clark, K. B. & Wheelwright, S. C. (1993), Managing New Product and Process Development, New York, Free Press.
11.Cleland, D. I. & King, W. R. (1983), System Analysis and Project Management, 3rd ed., p45.
12.Cooper, R. G. (1983), “Process Model for Industrial New Product Development”, IEEE Transactions on Engineering Management, Vol.30(1), pp.2-11.
13.Crawford, C. Merle (1991), New Product Management 3rd ed.
14.Danila S. (1989), “Technological Innovation Strategies”, Engineering Management Journal, Vol.1, pp.17-24.
15.Davis (1972), Human Relations at Work, The Dynamics of Organizational Behavior, pp.42-48.
16.Drucker, P. F. (1993), Post-Capital Society, Harper Collins. Gilbert, Myrna & Gordey-Hayes, Martyn(1996), ”Understanding The Process of Knowledge Transfer to Achieve Successful Technological Innovation”, Tcehnovation, Vol.16(6), pp.365-385.
17.Davenport, T. H. & Prusak, L. (1998), Working Knowledge: How Organizations Manage What They Know, Boston: Harvard College Press.
18.Fife, D. (1987), “Injuries and Deaths among Elderly Persons”, American Journal of Epidemiology, 126(5), pp.936-941.
19.Ford, R. C. & McLaughlin, F. C. (1992), “Successful Project Teams: a Study of MIS Managers”, IEEE Transactions on Engineering Management, Vol.39, pp.312-317.
20.Fleishman, E. A. (1973), Twenty Years of Consideration And Structure, In E. A. Fleishman & J. G.Hunt (Eds), Current Developments In the Study of Leadership, Carbondale:Southern Illinois University Press.
21.Friar, J. & Horwitch, M. (1986), The Emergence of Technology Strategy: A New Dimension of Strategic Management, Technology in the Modern Corporation: A Strategic Perspective, Pergamon Press Inc., New York.
22.Gobeli, D. H. & Brown, D.J. (1987), “Analyzing Product Innovations”, Research Management, Vol.30(4), pp.25-31.
23.Granstrand, et al. (1992), “External Technology Acquisition in Large Multi-Technology Corporations”, R&D Management, Vol.22(2), pp.111-133.
24.Hemphill, J. K. & Coons, A. E. (1950), Leadership Behavior Description, Personnel Research Board, Ohio State University.
25.Hedlund, G. (1994), “A Model of Knowledge Management and The M-Form Corporation”, Strategic Management Journal, Vol.15, pp.73-90.
26.Kaiser, K. & Bostrom, R. P. (1982), “Personality Characteristics of MIS Project Teams: An Empirical Study and Action-Research Design”, MIS Quarterly, pp.43-60.
27.Kerzner, H. (1984), Project Management: A System Approach to Planning, Scheduling and Controlling, Van Nostrand Reinhold Co. Inc.
28.Kotler, P. (1994), Marketing Management - Analysis, Planning, Implementation and Control, 8th ed., Englewood Cliffs:Prentice-Hall, pp.174.
29.Kuczmarski, T. D. (1992), Managing New Product: The Power of Innovation, 2nd ed., Prentice-Hall, Englewood Cliffs, pp.33-36.
30.Lee, M. & Om, K. (1994), “A Conceptual Framework of Technological Innovation Management”, Technovation, Vol.14(1), pp.7-16.
31.Nicholas, J. M. (1990), Managing Business and Engineering Projects, NJ: Prentice-Hall.
32.Nonaka, I. & Takeuchi, H. (1995), The Knowledge-Creating Company, Oxford University Press, Inc.
33.Rakos, J. J. (1990), Software Project Management for Small To Medium Sized Projects, Englewood Cliffs, N. J., Prentice-Hall.
34.Rauch, C. F. & Behling, O. (1984), Functionalism: Basis For An Alternate Approach To The Study Of Leadership. In J. G. Hunt, D. M. Hosking, C. A. Schriesheim, & R.Stewart(Eds.), Leaders and managers: International Perspectives on Managerial Behavior and Leadership. Elmsford, NY: Pergamon Press, pp.45-62.
35.Stanley, B. B., Aldag, R. J. & Cunningham, W. H. (1993), Business In A Changing World, 3rd ed., pp.371-391.
36.Shenhar, A. J. & Wideman, R. M. (2000), Optimizing Project Success by Matching PM Style With Project Type, (available online at http://www.pmforum.org).
37.Terry, G. R. (1960), Principles of Management, 3rd ed., Homewood III: Richard D. Irwin. Pattern, pp.95-101.
38.Tuman, G. J. (1983), Development and Implementation of Effective Project Management Information and Control Systems, Project Management Hand Book.
39.Jessup, H. R. (1990), “New Roles in Team Leadership”, Training & Development Journal, Vol.44(11), pp.79-83.
40.Kirkpatrick, S. A. & Locke, E. A. (1991), “Leadership: Do Traits Really Matter?”, Academy of Management Executive, Vol.5(2), pp.48.
41.Moenaert, R. K. (1995), “CR&D/Marketing Communication During The FuzzyFront-End”, IEEE Transactions on Engineering Management, Vol.42(3), pp.243-258.
42.Munns, A. K. & Bjeirmi, B. F. (1996), “The Role of Project Management in Achieving Project Success”, International Journal of Project Management, Vol.14(2), pp.81-87.
43.Pinto, J. K. & Slevin, D. P. (1988), “Project Success: Definition and Measurement Techniques”, Project Management Journal, Vol.19(1), pp.67-72.
44.Ring, P. S. & Van de Ven, A. H. (1994), “Developmental Process of Cooperative Interorganizational Relationships”, Academy of Management Review, Vol.19(1), pp.90-118.
45.Roessner, D. (1989), “Evaluation Government Innovation Programmes: Lessons From The U.S. Experience”, Research Policy, Vol.18(6), pp.343-359.
46.Ronkainen, I. A. (1985), “Criteria Changes across Product Development Stages”, Industrial Marketing Management, Vol.14, pp.171-178.
47.Sheth, Jagdish N. & Atul Parvatiyer (1995), “Relationship Marketing in Consumer Markets: Antecedents and Consequences”, Journal of the Academy of Marketing Science, Fall, pp.255-271.
48.Shockley, R. & Holt, R. (1983), “A Behavioral Investigation of Supplier Differentiation in The Market For Audit Services”, Journal of Accounting Research, Vol.21(Autumn), pp.545-564.
49.Song, X. M. & Montoya-Weiss, M. M. (1998b), “Critical Development Activities for Really New Versus Incremental Products”, Journal of Product Innovation Management, Vol.15, pp.124-135.
50.Teece, D. J., Rumelt, R., Dosi, G. & Winter, S. (1994), “The Dynamic Capabilities of Firms: An Introduction”, Industrial and Corporate Change, Vol.3( 3), pp.537-556.
51.Utler, W. G. (1991), “Acquiring Technology From Outside”, Research Technology Management, Vol.34(3), pp.11-18.
52.Van de Ven, A. H., Delbecq, A. L. & Koenig, R. Jr. (1976), “Determinants of Coordination Modes Within Organizations”, American Sociological Review, pp.322-338.
53.Veryzer, R. W. (1998), “Discontinuous Innovation and the New Product Development Process”, Journal Product Innovation Management, Vol.15, pp.304-321.
54.Whitten, J. L. & Bentley, L. D. (1998), “Project Manage Dictionary of Terms”, International Journal of Project Management, Vol.38, pp.56-78.
55.Wheelwright, S. C. & Clark, K. B. (1992), Revolutionizing Product Development, New York, The Free Press, pp.165-187.
56.Zimmerer, T. & Yasin, M. (1998), “The Leadership Profile of American Project Managers”, Project Management Journal, Vol.29(1), pp.31–38.
zh_TW