The research of Kanban implementation principles and practices in software technical team

• Main Authors: Jui-Hao Lin, 林瑞豪
• Other Authors: Sun-Jen Huang
• Format: Others
• Language: zh-TW
• Published: 2015
• Online Access: http://ndltd.ncl.edu.tw/handle/16773348669210543290

碩士 === 國立臺灣科技大學 === 資訊管理系 === 103 === 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.