在日新月異的社會下，專案式的開發結構越來越受各類型產業所喜愛，特別是資訊科技類，在舊有的開發流程為需求設計→產出→客戶與設計團隊的互動較少，所以產出結果與績效往往不盡理想，間接浪費了較多的時間及人力成本，設計團隊一直在重複設計及產出這兩個過程，而客戶依然收到不盡理想的產品，這樣反覆之下會造成專案的延宕。以往的新產品開發績效會受到團隊之間或是與客戶溝通不良、無法應變突發狀況…等問題影響，導致績效不如預期。「敏捷開發」一詞是近十年來在國外盛行的新開發流程，在國內鮮少人知曉。因此，本研究欲探究敏捷開發、需求品質、團隊互動及新產品開發績效彼此之間的關係，並從中探討其關聯性。
本研究採用SPSS統計軟體作為分析工具，以便利抽樣之方式收集台灣科技產業為樣本，作為研究對象來進行實證分析。並以因素分析、信度分析、單因子變異分析(ANOVA)、迴歸分析等方法進行分析。問卷發放期間為2017年3月至2017年4月，共計發放130份問卷，最終回收之有效問卷為126份。
這項研究的結果如下： 
1.敏捷開發對新產品開發績效有顯著正向之影響。
2.敏捷開發對需求品質有顯著正向之影響。
3.需求品質對新產品開發績效有顯著正向之影響。
4.敏捷開發對團隊互動有顯著正向之影響。 
5.團隊互動對新產品開發績效有顯著正向之影響。

With incessant progress of science and technology, the project-based development structure is becoming more and more popular for all types of industries, especially for the information technology industry, because old development process based on design requirement and production, customers had less interaction with design team, so the result and performance were imperfect; with indirect wasting of time and labor costs, design team only kept repeating design and produce processes, but still providing customers with unsatisfactory product, which led to project’s delaying. In the past, new product development performance could be affected by lack of communication within the team or with customers, inability to adapt to unexpected situations and other issues. "Agile development" is a new development process that was popular all over the world last few decades, but on the contrary, by now this term is only known by few people in Taiwan. Therefore, the primary goal of this study is to discuss agile development, requirement quality, team interaction and their relationship with new product development performance.
This study used SPSS statistical software to analyze data and selected sample from high-tech industries of Taiwan. During the research, this study has focused on factor analysis, reliability analysis, one way ANOVA and regression analysis. In period from March to April 2017, there were issued 130 questionnaires and eventually 126 were returned. The results of this study are as follows：
1.Agile Development has a significant positive influence on new product development performance.
2.Agile Development has a significant positive influence on requirement quality.
3.Requirement quality has a significant positive influence on new product development performance.
4.Agile Development has a significant positive influence on team interaction.
5.Team interaction has a significant positive influence on new product development performance.

目錄
目錄 I
表目錄 III
圖目錄 V
第一章緒論 1
第一節研究背景與動機 1
第二節研究目的 2
第三節研究流程 3
第二章文獻探討 5
第一節敏捷開發 5
第二節需求品質 8
第三節團隊互動 11
第四節新產品開發績效 15
第五節研究假設發展 20
第三章研究方法 23
第一節研究架構 23
第二節研究假設 23
第三節變數定義與問卷設計 24
第四節研究樣本來源 30
第五節資料分析方法 31
第四章資料分析與研究結果 33
第一節敘述性統計 33
第二節因素分析 41
第三節信度分析 47
第四節差異性分析 48
第五節迴歸分析 52
第六節研究假設驗證之結果 58
第五章結論與建議 60
第一節研究結論 60
第二節管理意涵 62
第三節研究限制與建議 63
參考文獻 65
附錄：研究問卷 72

表目錄
表2-1需求品質屬性規範 9
表2-2團隊與團體差異 13
表2-3新產品開發之衡量整理 18
表3-1敏捷開發問項 24
表3-2需求品質問項 27
表3-3團隊互動問項 28
表3-4新產品開發績效問項 29
表4-1產業類型次數分配表 34
表4-2工作內容次數分配表 34
表4-3職位次數分配表 35
表4-4年齡次數分配表 36
表4-5教育程度次數分配表 36
表4-6產品所屬類型次數分配表 37
表4-7產品種類次數分配表 38
表4-8產品創新程度次數分配表 38
表4-9產品複雜度次數分配表 39
表4-10產品總預算次數分配表 39
表4-11產品開發專案團隊人數次數分配表 40
表4-12產品開發的完成時間次數分配表 40
表4-13產品開發的持續時間次數分配表 41
表4-14各變數之Bartlett球形檢定及KMO檢定 42
表4-15敏捷開發構面之因素分析表 43
表4-16需求品質構面之因素分析表 45
表4-17各構面之信度分析表 47
表4-18產品種類在各變項之差異分析 48
表4-19產品創新程度在各變項之差異分析 50
表4-20產品複雜度在各變項之差異分析 51
表4-21產品總預算在各變項之差異分析 52
表4-22敏捷開發子構面對新產品開發績效之迴歸分析表 53
表4-23敏捷開發子構面對需求品質子構面之需求取得之迴歸分析表 54
表4-24 敏捷開發子構面對需求品質子構面之需求一致性之迴歸分析表 55
表4-25需求品質子構面對新產品開發績效之迴歸分析表 56
表4-26敏捷開發子構面對團隊互動之迴歸分析表 57
表4-27團隊互動對新產品開發績效之迴歸分析表 58
表4-28本研究假設驗證之結果 58

圖目錄
圖1-1研究流程圖 4
圖2-1工作團隊與工作團體比較圖 13
圖3-1研究架構 23

參考文獻
中文文獻
1.司徒達賢.(2005).策略管理新論:觀念架構與分析方法,再版,台北:智勝文化事業有限公司。
2.胡淑珍、莊青樹、蘇溢祥、陳維政(2008):手提CD音響外觀設計專案。專案管理學刊，1(1)，34-54。
3.楊劍鋒.(2010).捲煙新產品開發中消費者需求轉化路徑研究.工業技術經濟, 29(9),94-99。
4.葛中俊譯(1996).團隊工作的原理。台北:業強出版社。(Spiegel,J.,&Torres,C.,1994)。
英文文獻：
1.Agile Alliance.(2002)https://www.agilealliance.org/
2.Agile Alliance.(2016).Version One State of Agile Survey.https://explore.versionone.com/state-of-agile/versionone-10th-annual-state-of-agile-report-2
3.Agile Alliance.(2017).Version One State of Agile Survey.https://explore.versionone.com/state-of-agile/versionone-11th-annual-state-of-agile-report-2
4.Atuahene‐Gima,K.(1995).An exploratory analysis of the impact of market orientation on new product performance.Journal of Product Innovation Management,12(4),275-293.
5.Bae,Z.T.,&Lee,J.(1986).Technology development patterns of small and medium sized companies in the Korean machinery industry.Technovation,4(4),279-296.
6.Campion,M.A.,Medsker,G.J.,& Higgs,A.C.(1993).Relations between work group characteristics and effectiveness:Implications for designing effective work groups.Personal Psychology,46,823-825.
7.Cerpa,N.,Bardeen,M.,Kitchenham,B.,&Verner,J.(2010).Evaluating logistic regression models to estimate software project outcomes.Information and Software Technology,52(9),934-944.
8.Chen,C.(2007).Information technology,organizational structure,and new product development---the mediating effect of cross-functional team interaction.IEEE Transactions on Engineering Management,54(4)
9.Cooper,R.G.&Kleinschmidt,E.J.(1987),“New Product:What separates winners form loserss”,Journal of Product Innovation Management,4(3),169-184.
10.Dagnino,A.,Smiley,K.,Srikanth,H.,Anton,A.I.,&Williams,L.(2004).Experiences in applying agile software development practices in new product development.
11.Dayan,M.,&Di Benedetto,C.A.(2009).Antecedents and consequences of teamwork quality in new product development projects. European Journal of Innovation Management,12(1),129-155.
12.Driva,H.,Pawar,K.S.,& Menon,U.(2000).Measuring product development performance in manufacturing organisations.International Journal of Production Economics,63(2),147-159.
13.Durmuşoğlu,S.S.,&Barczak,G.(2011).The use of information technology tools in new product development phases:Analysis of effects on new product innovativeness, quality,and market performance.Industrial Marketing Management,40(2),321-330.
14.Feldman,D.C.,& Arnold,H.J(1983).Managing individual and group behavior in organizations. McGraw-Hill College.
15.Fried,B.J.,Topping,S.,&Rundall,T.G.(2000).Groups and teams in health services organizations. Health Care Management:Organization Design And Behavior.Albany,NY:Delmar Publishers,154-190. 
16.George,J.M.,Jones,G.R.,&Sharbrough,W.C.(1996).Understanding and managing organizational behavior.Reading,MA:Addison-Wesley.
17.Gorschek,T.,Svahnberg,M.,Borg,A.,Loconsole,A.,Börstler,J.,Sandahl,K.,& Eriksson,M.(2007).A controlled empirical evaluation of a requirements abstraction model.Information and Software Technology,49(7),790-805.
18.Gorschek,T.,&Davis,A.M.(2008).Requirements engineering: In search of the dependent variables.Information and Software Technology,50(1),67-75.
19.Griffin,A.,&Page,A.L.(1993).An interim report on measuring product development success and failure.Journal of product innovation management,10(4),291-308.
20.IEEE Computer Society. Software Engineering Standards Committee,&IEEE-SA Standards Board.(1998).IEEE Recommended Practice for Software Requirements Specifications.Institute of Electrical and Electronics Engineers.
21.IEEE Standards Association.(1990).Standard glossary of software engineering terminology.lEEE Std,610-12.
22.Inayat,I.,Salim,S.S.,&Kasirun,Z.M.(2013).Agile-based software product development using cloud computing services:findings from a case study.ScienceInternational journal(Lahore),1065-1069.
23.Jaitly,S.(2014).Implementation of quality in an Agile software development environment to quicken delivery of software based on customer requirements.California State University,Dominguez Hills. 
24.Jeff Sutherland(2013)https://msdn.microsoft.com/zh-tw/library/dd997578(v=vs.120).aspx
25.Jessup,H.R.(1990).New roles in team leadership.Training & Development Journal,44(11),79-84.
26.Jiao,J.R.,&Chen,C.H.(2006).Customer requirement management in product development:a review of research issues.Concurrent Engineering,14(3),173-185.
27.KatzenbachJ.R.,&Smith,D.K.(1993).The wisdom of teams:Creating the high-performance organization.Harvard Business Press.
28.Kitchenham,B.,&Pfleeger,S.L.(1996).Software quality:The elusive target.IEEE software,13(1),12-21.
29.Komorita,S.S.,&Parks,C.D.(1995).Interpersonal relation:Mixed-motive interaction.Annual Review of Psychology,46,183-207.
30.Kotlarsky,J.,&Oshri,I.(2005).Social ties,knowledge sharing and successful collaboration in globally distributed system development projects. European Journal of Information Systems,14(1),37-48
31.Kotler,P.(1997).Marketing Management-Analysis,Planning,Implementation,and Control,Prentice Hall.Inc.,New Jersey.
32.Kumar,B.(2015).The sway of agile processes over software maintainability.International Journal of Computer Applications,109(1),25-29.
33.Li,J.,Hou,L.,Qin,Z.,Wang,Q.,&Chen,G.(2008).An Empirically–Based Process to Improve the Practice of Requirement Review.In International Conference on Software Process (pp.135-146).Springer Berlin Heidelberg.
34.Liu,J.Y.C.,Chen,H.G.,Chen,C.C.,&Sheu,T.S.(2011).Relationships among interpersonal conflict,requirements uncertainty, and software project performance. International Journal of Project Management,29(5),547-556.
35.Lussier,R.(2011).Management fundamentals:Concepts,applications,skill development.Cengage Learning.
36.Macaulay,L.(1996).Requirements for requirements engineering techniques.In Requirements Engineering,1996.,Proceedings of the Second International Conference on (pp.157-164).IEEE.
37.Martin,R.C.(2003).Agile software development:principles,patterns,and practices.Prentice Hall PTR.
38.McIntosh-Fletcher,D.(1996).Teaming by design:Real teams for real people. Irwin Professional Pub..
39.Mead,M.(Ed.).(2002).Cooperation and competition among primitive peoples(Vol.123).Transaction Publishers.
40.Millson,M.R.,&Wilemon,D.(2002).The impact of organizational integration and product development proficiency on market success.Industrial Marketing Management,31(1),1-23.
41.Minguela-Rata,B.,&Arias-Aranda,D.(2009).New product performance through multifunctional teamwork:An analysis of the development process towards quality excellence.Total Quality Management,20(4),381-392.
42.Misra,S.(2012).Agile software development practices:Evolution,principles, and criticisms.The International Journal of Quality & Reliability Management,29(9),972-980.
43.Robbins,S.P.,Judge,T.A.,& Sanghi,S.(2002).Organizational Behavior Prentice Hall of India.New Delhi.
44.Robbins,S.P.,&Judge,T.A.(2011).Organizational Behavior.New Jersey:Person Education.
45.Schwaber,K.(2004).Agile project management with Scrum.Microsoft press.
46.Smith,D.H.(1967).A Parsimonious Definition of“Group:”Toward Conceptual Clarity and Scientific Utility.Sociological Inquiry,37(2),141-168.
47.Souder,W.E.,Sherman,J.D.and Cooper,R.D.(1998),”Environmental Uncertainty,Organizational Integration,and New Product Development Effectiveness:A Test of Contingency Theory,Journal of Product Innovation Management,15(6),pp.520–533.
48.Stokes,D.A.(1991).Requirements analysis. Software Engineer’s Reference Book,16.
49.Tervonen,N.,Hannola,L.,& Pynnönen,M.(2014).Agile Methods for Boosting the Commercialization of Innovations.In ISPIM Conference Proceedings (p.1).The International Society for Professional Innovation Management(ISPIM).
50.The Standish Report(2004),http://www.standishgroup.com/chronicles/index.php.
51.Tjosvold,D.(1986).Working Together to Get Things Done,Lexington.MA:Lexington Books.
52.Tjosvold,D.(1988).Cooperative and competitive dynamics within and between organizational units.Human Relations,41(6),425-436.
53.Wilson,W.M.,Rosenberg,L.H.,&Hyatt,L.E.(1997).Automated analysis of requirement specifications.In Proceedings of the 19th international conference on Software engineering(pp.161-171).ACM.
54.Wohlin,C.(2005).Engineering and managing software requirements.Springer Science & Business Media.
55.Wu,J.Z.,& Axelrod,R.(1995).How to cope with noise in the iterated prisoner’s dilemma.The Journal of Conflict Resolution,39(1),183-189.