近年來以物聯網為概念的相關應用已經成為最熱門的議題之一，各國家與企業皆致力於發展其技術以及相關應用。而物聯網的應用範圍十分廣泛，舉凡交通、醫療、電力、物流、家居等都是其應用的範圍。亞洲國家於近十年來也紛紛提出相關發展計畫，由此可看出各國對發展物聯網產品之野心與競爭。而台灣政府於2008年開始積極推展智慧家庭政策，端看目前成果，以技術層面而言並非無法達成，但在實際應用與推廣上明顯仍有許多不足之處。因此本研究欲探討使用者對於物聯網相關應用產品的使用動機為何，以智慧家庭為例，先進行相關文獻探討，並以修正式德菲法做為發展ANP專家問卷的基礎，再利用ANP法施行專家問卷，排序出影響消費者使用動機的各項權重，選擇出最符合消費者需求的產品組合，讓開發者能了解在開發與推展智慧家庭相關應用時，應滿足消費者哪些心理層面之動機因素，提升未來發展相關產品時的成功機率。 / In recent years, applications related to the concept of IoT become one of the most popular issues all over the world. Countries and enterprises devote themselves to developing the technique and application related to IoT. The range of its applications is very wide, including transportation, medical treatment, electricity, logistics, and home, etc. Asian countries set forth some development projects in the past decade, demonstrating the ambition and competition between countries in developing IoT products. Taiwan has started to push the development of smart home related applications since 2008. After development for some years, insufficiency in actual implementation and diffusion remains given our technological advantage. Therefore, this research intends to study the motivation for users to use IoT products taking smart home as an example. First, we study the related literature review and use modified Delphi method to develop the ANP expert questionnaires. Then, we prioritize the weights of consumer’s motives. The result can enable developers of smart home products to understand what kind of consumer motives they should satisfy when developing and promoting smart home applications. This enhances the probability of success for developing related products in the future.

90年代的後期，敏捷式系統發展方法開始被倡導。相對於傳統的系統發展方法，敏捷式系統發展方法著重於回饋機制而非事前的計畫、以人為中心而非以流程為中心。這樣的方法希望能助於提高組織對回應市場、客戶的效率，進而提高效益。目前在商場中使用此方法做為開發工具的企業仍是少數，本研究希望透過探討敏捷式系統發展方法論的使用時機來進行教學，進而得知系統開發人員對於接受敏捷式系統發展方法的關鍵因素，並藉此了解該如何在企業中導入此方法。本研究發現除了使用此方法的能力會影響影響使用意圖之外，在內在因素方面也包含了公司結構與團隊因素，外部因素則包含了顧客與成功案例因素，這些都是接受敏捷式系統發展方法的關鍵因素。本研究希望根據以上的分析結果，提出敏捷式系統發展方法導入之建議，提供組織做為參考用。 / Awareness of agile system development methodologies (SDM) has grown among information systems development community in recent years. Many of their advocates consider the agile and the plan-driven SDMs polar opposites. Indeed there are circumstances where agile SDMs are more suitable than plan-driven SDMs. Yet, there have been few studies on understanding developers’ adoption intention. This paper takes an initial attempt to gauge new generation of software developers’ intention to select agile SDMs. To many of these developers, agile SDMs are relatively new if not unheard of, in order to assess their intention to choose such category of methodologies, this research first introduced the methodologies to a group of 21 IS-major graduate students and discussed how and when to use agile SDMs. Then a survey was conducted, which was comprised of two parts of questions: agile SDM self-efficacy and intention to use. PLS analysis results showed that agile SDM self-efficacy influence the intention to use through performance outcome expectation, personal outcome expectation, and affect. Although the relationship between self-efficacy and anxiety was not confirmed, anxiety does affect intention to use. The fact that direct relationships between all four emotive variables and the intention to use are established implies that in order to encourage the use of agile SDMs, the focus should be emotive variables, and that self efficacy may be just one of various ways to promote the favorable emotional states. In addition, these participates were invited to a three-round Delphi test and analytic hierarchy process to retrieved their concerns about accepting or rejecting agile SDMs. Ten key factors were extracted and categorized. Adding up the pros and cons, team dimension is the most important dimension, which explains individual first concerns about how the collaboration when using agile SDMs. Other than team dimension, customer, corporate structure, project, success cases and methodology dimensions were consistent with the literatures. Thus our study provides a critical understanding of the factors that affect new generation of software developers’ intention to select agile SDM.