Scrum是目前許多企業採用的流程之一,市面上有許多支援Scrum的工具,ezScrum為其中之一。Scrum不只提昇專案的管理性還增加了專案透明度,並且以迭代式開發使得專案可以適應變化的需求。然而Scrum流程並不是所有軟體開發階段都適合,例如:軟體在完成釋出(Release)進入維護階段之後,先前積極去消化需求庫存的活動暫告一段落,取而代之的是積極解決用戶回報的錯誤。由於錯誤具有不可預期與緊急的特性,使得Scrum規劃迭代的意義漸漸喪失。此時,具有事件驅動特性的Kanban流程,比Scrum流程更為合適。 在本論文中,提出Scrum與Kanban流程轉換的方式來解決上述的問題。我們在ezScrum上擴增模組—ezKanban,讓ezScrum上可同時支援Scrum與Kanban流程,使得專案從開發階段轉至維護階段的時候,可以將軟體流程從Scrum轉換為Kanban。最後透過一個實例來說明流程轉換的時機,並逐步說明ezScrum如何轉換流程。
Scrum is a software development process which has been widely used in many companies. There are many Scrum tools, and ezScrum is one of them. Scrum increases the project not only in manageability but also in visibility. Scrum iterative development makes adaptive to requirement changes. However, Scrum may not be suitable to cover all phases in software lifecycle. For example, when the project enters maintenance phase, most requirements have been completed, and the team start focusing on fixing reported bugs. Since bugs are unpredictable and emergent, the benefits of iteration plans in Scrum disappear. In this case, Kanban is more suitable because it is event-driven. In this thesis, we extended ezScrum with Kanban support, so when a project transfers from development to maintenance phase, developers can transfer the project from Scrum to Kanban seamlessly. Furthmore, we provided a case study to explain when to make transition and how to accomplish this with the ezScrum extension module—ezKanban.