Scrum或是各類常見敏捷軟體開發 (Agile Software Development) 的方法如看板方法 (Kanban) 、精實開發 (Lean Software Development) 、極限程式開發 (eXtreme Programming - XP) 等等，早已經是軟體業的趨勢。然而從傳統瀑布式 (Waterfall) 轉換成敏捷式開發的過程並不一定如預期般順利。 而最近幾年來又出現了一個新的名詞 “Water-Scrum-fall＂，這個字正是由傳統開發方法Waterfall與各種敏捷開發方法中最廣泛被導入的Scrum所組合而成。在現實中各種規模的公司或組織其環境、企業文化、內外部問題都不一樣，導入敏捷開發方法時最有機會成功的方式則是能根據各公司的特性與原本適用的傳統開發方法融合，而這種演進趨勢其實某種程度上恰恰符合敏捷軟體開發中對各種狀況快速反應的精神。 希望藉由此個案對於Scrum開發方法導入之觀察與整理分析的過往資料加以分析，並依據當時內部和外部環境情勢、團隊成員對於敏捷開發的經驗與導入狀況來檢視軟體開發執行過程中遇到的難題，並檢視最終交付產出與導入Scrum敏捷開發方法成效。 探討對於預期中的變動如何在事前導入評估時可以被發現，並對預期外的變動狀況分析處理方式是否有效，以對日後導入Scrum開發方法的其他團隊或組織有所助益並降低導入失敗的機率。 ;Scrum and other Agile software development methodologies, such as Kanban, Lean, and eXtreme Programming, are already the mainstream of software development. However, it has not been always successful when adopting an agile methodology in a traditional Waterfall development environment. In recent years, there is a new hybrid software development methodology called “Water-Scrum-fall” that combines Scum, the most popular agile development methodology, with the traditional Waterfall development methodology. This flexible software development methodology that embraces both agile development principles and traditional Waterfall methodology allows development teams to adopt techniques and practices best meet the needs of solving software development problems. Goals of the research are to find out what situations and difficulties are unexpected when adopting Scrum software development methodology. Also, the study analyzes if software team members are able to manage those situations and difficulties effectively. The results of this case study reflected largely in the experience of Scrum adoption can provide some help to other development teams that plan to adopt Scrum or other agile development methodologies.
