SCRUMBAN : The Optimal Approach Using Scrum and Kanban

Abstract

Scrumban may be a combination of practices from Kanban and Scrum practices to manage the event of
software supported different project situations. Scrumban practices formation can differ supported different projects and
team members. However, since each method has its own pros and cons, inappropriate formation of Scrumban practices
may cause increased waste and time of development, and decreased quality, which successively, affect the Agile
organizations and cause inefficient and ineffective development. This study aims to show how Scrumban method is
created supported a combination of Kanban and Scrum using task priority approach and indivisual team effort.
Scrumban formation and therefore the identification of the factors, which assist within the combination of Kanban and
Scrum were conducted through a review of the previous work and semi-structured interviews with 7 Agile experts, after
which, content analysis was conducted to analyse the gathered data. various factors - the strategy prescription, roles and
responsibilities, adoption time, team size, batch size, requirements prioritization, feature size, lead time, technical
practices, cost and quality, assist Additionally, Scrumban were found to be more appropriate than Scrum or Kanban in
measuring task priority, saving time, improving quality and minimizing waste