Paper Info
Title
Transition Of Software Maintenance Teams From Scrum To Kanban
Abstract
Software companies are increasingly moving to use Kanban after Scrum since Kanban claimed to offer improved project visibility, software quality, team motivation, communication and collaboration. However, empirical studies are needed to verify these effects and companies' real motivation for the transition. In particular, underlying reasons leading software companies to start using Kanban in software maintenance must be understood. A multiple-case study was conducted to investigate why two experienced Scrum maintenance teams transitioned to Kanban. We conducted 17 semi-structured interviews with two different teams from two large Finnish software companies. Thematic analysis was applied to identify the most common challenges in Scrum and their solutions in Kanban. The results showed that Scrum maintenance teams faced challenges, such as lack of work visibility, task prioritisation, communication and collaboration, over commitment of sprints, work synchronisation and changing people. We discuss how maintenance teams mitigated these challenges with Kanban and present the lessons learned.
Year
DOI
Venue
2016
10.1109/HICSS.2016.670
PROCEEDINGS OF THE 49TH ANNUAL HAWAII INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES (HICSS 2016)
Field
DocType
ISSN
Kanban,Scrum,Personal software process,Software engineering,Software peer review,Computer science,Knowledge management,Kanban (development),Software maintenance,Empirical process (process control model),Social software engineering,Process management
Conference
1060-3425
Citations 
PageRank 
References 
6
0.52
16
Authors
4
Name
Order
Citations
PageRank
Muhammad Ovais Ahmad1596.47
Pasi Kuvaja223624.82
Markku Oivo365081.11
Jouni Markkula425025.91