Scrum, Kanban or a Mix of Both? A Systematic Literature Review

Among the Agile methods, Scrum and Kanban are widely used in software development and they are considered the two most effective ones influencing the direct results of projects. Despite the importance of knowing their relative strengths and advantages and integrating them to achieve better results t...

Full description

Saved in:
Bibliographic Details
Published in2022 17th Conference on Computer Science and Intelligence Systems (FedCSIS) Vol. 30; pp. 883 - 893
Main Authors Ozkan, Necmettin, Bal, Sevval, Erdogan, Tugba Gurgen, Gok, Mehmet Sahin
Format Conference Proceeding Journal Article
LanguageEnglish
Published Polish Information Processing Society 01.01.2022
Subjects
Agile
agility
Bibliographies
Computer science
Industries
Organizations
project management
Scrum (Software development)
SLR
Software
software development
systematic literature review
Systematics
Online AccessGet full text
ISSN2300-5963
DOI10.15439/2022F143

Cover

More Information
Summary:Among the Agile methods, Scrum and Kanban are widely used in software development and they are considered the two most effective ones influencing the direct results of projects. Despite the importance of knowing their relative strengths and advantages and integrating them to achieve better results than individual use, none of the secondary studies provide extensive knowledge on the topic. In this paper, we performed a Systematic Literature Review (SLR) study to investigate the characteristics of the empirical studies which involve Scrum and Kanban by comparing or integrating them. Our final set includes 38 studies posing primary information on the advantages of each method over another one, the properties including artifacts, roles, and events from Scrum and Kanban in combining them in a hybrid way, and the properties of transitions from one to another such as transition directions (Scrum to Kanban, Kanban to Scrum or Scrum/Kanban to Hybrid), transition years, and transition reasons. The outputs can be interesting for both industry and researchers. For example, nearly all of the transitioning organizations are moving from Scrum to Kanban or to hybrid method. Among the reasons for the transitions, the problems experienced with Scrum are remarkable. In comparison, Kanban stands out clearly in a positive way. Almost all of the teams combining both use flow instead of a sprint.
ISSN:2300-5963
DOI:10.15439/2022F143