隨著社群網路、雲端運算及行動應用的快速興起，當今企業不只將軟體作為輔助的工具，更將軟體開發能力作為其核心競爭優勢。然而企業在面臨快速變化的市場環境及日新月異的客戶需求，以預測、計畫及循序漸進開發為基礎的線性式軟體開發流程，如瀑布式模型(Waterfall Model)已無法快速的回應市場需求，並及時交付有價值的軟體。
因此，愈來愈多企業開始導入敏捷開發流程，期望透過敏捷開發中與客戶互動、團隊合作、接受並回應變化及可用的軟體的特性來確保研發團隊能夠快速的交付可用且高價值的產品給客戶，而 Scrum 為最多企業所導入的敏捷開發流程。
然而許多企業也發現，Scrum 對於某些情境及研發團隊仍有太多的限制、浪費與不透明。因此，精實軟體開發中的「看板方法」(Kanban)開始被導入軟體開發流程當中。
本研究將透過文獻探討來瞭解敏捷開發、精實軟體開發、Scrum、看板方法的原則及核心實踐，並透過多個導入看板方法的個案，來分析其導入看板方法的原則、實踐與成效，供未來準備導入敏捷開發的團隊參考，可選擇最適合的方法、減少導入障礙，達到快速反應與即時交付的目標。

With the rapid emergence of social networks, cloud computing and mobile applications, today’s enterprises no longer regard software as assisting tools. They even upgrade their capabilities in developing software as their core competitiveness. Nevertheless, enterprises face the environment of rapid changing market and changing customer requirements, the sequential design process that founded on the basis of predicting, planning and progressive development life cycle, such as the Waterfall Model, incapable of responding to market requirements and provide any valuable software promptly. For the reason, more and more enterprises introduce Agile developoment into software development process. Hoping the development team can deliver valuable, working software to customer swiftly through the features of Agile developoment — direct interaction with customer, teamwork, accept and respond to changes and working software. Moreover, Scrum is the most popular framework of Agile development. In addition, many enterprises consider that Scrum still has many limitations, wastes and is not transparent enough for some situations. Therefore, “Kanban” a methodology of Lean software development, has been introduced into the software development process. This research intends to explore Agile, Lean software development, Scrum and the principles and core practices of Kanban by literature review. Analyzing the the principles, core practices and effects by the cases that implement Kanban to development process. Providing the reference to the devlopment teams and assist them in choosing the most suitable options and minimizing barriers in introduction Agile development. To achieve the objectiives of prompt response and timely delivery.

中文文獻

陳建村 (2014)，Kanban 方法的六個實務做法—Improve Collaboratively, Evolve
Expermierntally，線上檢索日期：2015 年 2 月 28 日，網址：
http://teddy-chen-tw.blogspot.tw/2014/08/7kanbanimprove-collaboratively-evol
ve.html
張松(2014)，精實軟體度量，博碩文化
鄭炳強(2007)，軟體工程：從實務出發，智勝文化

英文文獻

Agile Alliance. (2001) What is Agile? Retrieved 1/25, 2015, from
http://www.agilealliance.org/the-alliance/what-is-agile/
Anderson, J.D. (2012) Lean Software Development. Retrieved 1/29, 2015, from
https://msdn.microsoft.com/en-us/library/hh533841.aspx
Anderson, J. D. (2010) Kanban-Successful Evolutionary Change for Your Technology
Business. Sequim, Washington: Blue Hole Press.
Anderson, J. D.(2010) The Principles of the Kanban Method. Retrieved 2/24, 2015,
from http://www.djaa.com/principles-kanban-method-0
Books, F.P. (1987) No silver bullet: Essence and accidents of software engineering.
Computer,Vol. 20, 10-19, doi: 10.1109/MC.1987.1663532
Burrows, M. (2014) Kanban from the Inside. Sequim, Washington. Blue Hole Press.
Cockburn, A. (2002) Agile Software Development. Pearson Education.
Hall, L., & Futela, S., & Gupta, D. (2014) IT Key Metrics Data 2015: Key Applications
Measures: Project Measures: Current Year. Gartner. (G00266081)
Hamel, G. (2006) “Management Innovation”, Harvard Business Review, February,
2006, p. 74.
Kniberg, H., & Skarin, M. (2010) Kanban and Scrum making the most of both.
[Adobe Digital Editions version]. Retrieved 2/24, 2015 from
http://www.infoq.com/minibooks/kanbanscrum-minibook
Liker, J., Morgan, J., (2006) The Toyota Product Development System: Integrating
People, Process, and Technology. Productivity Press.
Martin, R. C. (2003) Agile Software Development: Principles, Patterns, and Practices.
Pearson Education.
Ohno, T. (1988) Toyota Production System: Beyond Large Scale Production.
Productivity Press.
Polk, R. (2011) Agile & Kanban in Coordination. IEEE Computer society, 2011 Agile
Conference, 263-268. doi:10.1109/AGILE.2011.10
Poppendieck, M., Poppendieck, T., (2003).Lean Software Development: An Agile
Toolkit. Addison Wesley
Poppendieck, M., Poppendieck, T., (2006). Implementing Lean Software
Development: From concept to cash. Addison Wesley
Schwaber, K. (2001) Agile Software Development with SCRUM. Addison-Wesley.
Schwaber, K., Sutherland, J.,(2013) The Scrum Guide. Retrieved 2/23, 2015, from
http://www.scrumguides.org/download.html
Seikola,M., Loisa, H. M., & Jagos, A. (2011) Kanban Implementation in a Telecom
Product Maintenance. IEEE Computer society, 2011 37th EUROMICRO
Conference on Software Engineering and Advanced Applications, 321-329. doi:
10.1109/SEAA.2011.56
Shingo, S. (1981) Study of “Toyota” Production System from an Industrial
Engineering Viewpoint. Productivity Press.
Skarin, M. (2010) 10 Different Kanban boards and their context. [Adobe Digital
Editions version]. Retrieved 2/24, 2015 from
http://blog.crisp.se/mattiasskarin/files/pdf/10different_kanban_boards_and_th
eir_context_mskarin.pdf
Sutherland, J. (2010) Agile Principles and Values. Retrieved 1/26, 2015, from
http://www.scruminc.com/microsoft-agile-guidance-visual-studio/
Version one. (2014) 8th State of Agile Survey. VersionOne.