An empirical study of Scrumban formation based on the selection of scrum and Kanban practices

Mashal Alqudah, Rozilawati Razali

Research output: Contribution to journalArticle

Abstract

Scrumban is a combination of practices from Kanban and Scrum practices to manage the development of software based on different project situations. Scrumban practices formation can differ based on different projects and team members. However, since each method has its own pros and cons, inappropriate formation of Scrumban practices may lead to increased waste and time of development, and decreased quality, which in turn, affect the Agile organizations and cause inefficient and ineffective development. Practitioners of Kanban and Scrum are convinced that a combination of both methods is better than the use of one and thus, practitioners should be guided in their decision making. This study aims to show how Scrumban method is formed based on a combination of Kanban and Scrum methods. Scrumban formation and the identification of the factors, which assist in 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. Different factors - the method prescription, roles and responsibilities, adoption time, team size, batch size, requirements prioritization, feature size, lead time, technical practices, cost and quality, assist Agile team members in the formation of Scrumban by combining appropriate Kanban and Scrum practices. In addition, Scrumban were found to be more appropriate than Scrum or Kanban in saving time, improving quality and minimizing waste.

Original languageEnglish
Pages (from-to)2315-2322
Number of pages8
JournalInternational Journal on Advanced Science, Engineering and Information Technology
Volume8
Issue number6
Publication statusPublished - 1 Jan 2018

Fingerprint

Decision making
methodology
prioritization
Costs
Prescriptions
decision making
interviews
Decision Making
Software
Organizations
Interviews
Costs and Cost Analysis

Keywords

  • Formation
  • Kanban
  • Scrum
  • Scrumban
  • Selection factors

ASJC Scopus subject areas

  • Computer Science(all)
  • Agricultural and Biological Sciences(all)
  • Engineering(all)

Cite this

@article{bdadf30adf4c47bdb378b10654a1fecb,
title = "An empirical study of Scrumban formation based on the selection of scrum and Kanban practices",
abstract = "Scrumban is a combination of practices from Kanban and Scrum practices to manage the development of software based on different project situations. Scrumban practices formation can differ based on different projects and team members. However, since each method has its own pros and cons, inappropriate formation of Scrumban practices may lead to increased waste and time of development, and decreased quality, which in turn, affect the Agile organizations and cause inefficient and ineffective development. Practitioners of Kanban and Scrum are convinced that a combination of both methods is better than the use of one and thus, practitioners should be guided in their decision making. This study aims to show how Scrumban method is formed based on a combination of Kanban and Scrum methods. Scrumban formation and the identification of the factors, which assist in 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. Different factors - the method prescription, roles and responsibilities, adoption time, team size, batch size, requirements prioritization, feature size, lead time, technical practices, cost and quality, assist Agile team members in the formation of Scrumban by combining appropriate Kanban and Scrum practices. In addition, Scrumban were found to be more appropriate than Scrum or Kanban in saving time, improving quality and minimizing waste.",
keywords = "Formation, Kanban, Scrum, Scrumban, Selection factors",
author = "Mashal Alqudah and Rozilawati Razali",
year = "2018",
month = "1",
day = "1",
language = "English",
volume = "8",
pages = "2315--2322",
journal = "International Journal on Advanced Science, Engineering and Information Technology",
issn = "2088-5334",
publisher = "INSIGHT - Indonesian Society for Knowledge and Human Development",
number = "6",

}

TY - JOUR

T1 - An empirical study of Scrumban formation based on the selection of scrum and Kanban practices

AU - Alqudah, Mashal

AU - Razali, Rozilawati

PY - 2018/1/1

Y1 - 2018/1/1

N2 - Scrumban is a combination of practices from Kanban and Scrum practices to manage the development of software based on different project situations. Scrumban practices formation can differ based on different projects and team members. However, since each method has its own pros and cons, inappropriate formation of Scrumban practices may lead to increased waste and time of development, and decreased quality, which in turn, affect the Agile organizations and cause inefficient and ineffective development. Practitioners of Kanban and Scrum are convinced that a combination of both methods is better than the use of one and thus, practitioners should be guided in their decision making. This study aims to show how Scrumban method is formed based on a combination of Kanban and Scrum methods. Scrumban formation and the identification of the factors, which assist in 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. Different factors - the method prescription, roles and responsibilities, adoption time, team size, batch size, requirements prioritization, feature size, lead time, technical practices, cost and quality, assist Agile team members in the formation of Scrumban by combining appropriate Kanban and Scrum practices. In addition, Scrumban were found to be more appropriate than Scrum or Kanban in saving time, improving quality and minimizing waste.

AB - Scrumban is a combination of practices from Kanban and Scrum practices to manage the development of software based on different project situations. Scrumban practices formation can differ based on different projects and team members. However, since each method has its own pros and cons, inappropriate formation of Scrumban practices may lead to increased waste and time of development, and decreased quality, which in turn, affect the Agile organizations and cause inefficient and ineffective development. Practitioners of Kanban and Scrum are convinced that a combination of both methods is better than the use of one and thus, practitioners should be guided in their decision making. This study aims to show how Scrumban method is formed based on a combination of Kanban and Scrum methods. Scrumban formation and the identification of the factors, which assist in 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. Different factors - the method prescription, roles and responsibilities, adoption time, team size, batch size, requirements prioritization, feature size, lead time, technical practices, cost and quality, assist Agile team members in the formation of Scrumban by combining appropriate Kanban and Scrum practices. In addition, Scrumban were found to be more appropriate than Scrum or Kanban in saving time, improving quality and minimizing waste.

KW - Formation

KW - Kanban

KW - Scrum

KW - Scrumban

KW - Selection factors

UR - http://www.scopus.com/inward/record.url?scp=85059508173&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=85059508173&partnerID=8YFLogxK

M3 - Article

AN - SCOPUS:85059508173

VL - 8

SP - 2315

EP - 2322

JO - International Journal on Advanced Science, Engineering and Information Technology

JF - International Journal on Advanced Science, Engineering and Information Technology

SN - 2088-5334

IS - 6

ER -