A comparison of scrum and Kanban for identifying their selection factors

Scrum and Kanban methods handle and manage the progress of software development. These methods are used in different situations and workflows. Hence, they are effective for different Agile team members and projects in diverse situations. However, the use of inappropriate method or practice leads to software development processes that are inflexible and wasteful, impacting the organization and causing inefficient development. Adopters of Scrum and Kanban believe that wrong practices of both methods are risky and thus, Agile team members should be assisted in their decision making. The aim of this study is to determine the main factors to consider during the selection of Kanban and Scrum method. The identification of the factors was conducted through in-depth review of the relevant work, after which, content analysis was employed in the analysis of data. As discovered, method prescription, roles and responsibilities, adoption time, team size, batch size, requirements prioritization, feature size, lead time, technical practices, cost and quality were the main factors that guide Agile team members in choosing Scrum or Kanban as well as their practices.