An Empirical Study of Scrumban Formation based on the Selection of Scrum and Kanban Practices

Mashal Alqudah, Rozilawati Razali


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.


scrumban; formation; selection factors; Kanban; scrum.

Full Text:



A. Alliance, “Agile Manifesto,†Online at, vol. 6, no. 1, 2001.

S. W. Ambler, “The Non-Existent Software Crisis: Debunking the Chaos Report,†2014. [Online]. Available:

N. Nikitina and M. Kajko-Mattsson, “Developer-driven big-bang process transition from Scrum to Kanban,†in Proceedings of the 2011 international conference on software and systems process, 2011, pp. 159–168.

H. Kniberg and M. Skarin, Kanban and Scrum-making the most of both. Lulu. com, 2010.

R. Cuellar, “Kanban for Help Desks: Managing the Unplannable,†Cut. IT J., vol. 24, no. 3, p. 23, 2011.

A. Shalloway, “Demystifying Kanban,†Cut. IT is J., vol. 24, no. 3, p. 12, 2011.

R. H. Al-Ta’ani and R. Razali, “A Framework for Requirements Prioritisation Process in an Agile Software Development Environment: Empirical Study,†Int. J. Adv. Sci. Eng. Inf. Technol., vol. 6, no. 6, pp. 846–856, 2016.

A. M. M. Hamed and H. Abushama, “Popular agile approaches in software development: Review and analysis,†in Computing, Electrical and Electronics Engineering (ICCEEE), 2013 International Conference on, 2013, pp. 160–166.

R. V. Anand and M. Dinakaran, “Popular Agile Methods in Software Development: Review and Analysis,†Int. J. Appl. Eng. Res., vol. 11, no. 5, pp. 3433–3437, 2016.

A. S. Campanelli and F. S. Parreiras, “Agile methods tailoring–A systematic literature review,†J. Syst. Softw., vol. 110, pp. 85–100, 2015.

R. H. AL-TA’ANI and R. Razali, “Process Model For Systematic Requirements Prioritisation Process In An Agile Software Development Environment Based On 5S Approach: Empirical Study.,†J. Theor. Appl. Inf. Technol., vol. 95, no. 8, 2017.

R. Hoda and J. Noble, “Becoming Agile: A Grounded Theory of Agile Transitions in Practice,†in Proceedings - 2017 IEEE/ACM 39th International Conference on Software Engineering, ICSE 2017, 2017.

O. N. A. Al-Allaf, “The Adoption of Agile Processes in Large Web Development Enterprises: A Survey in Jordan.,†IJWA, vol. 2, no. 3, pp. 206–216, 2010.

F. Ahmad, F. Baharom, and M. Husni, “Agile development methods for developing a web application in small software firms,†in Knowledge Management International Conference (KMICe), 2012.

D. Verweij and O. Maassen, “Kanban at an Insurance Company in the Netherlands,†Viral Growth Kanban Enterp. Cut. IT J., 2011.

D. J. Anderson and A. Rock, “An agile evolution: why Kanban is catching on in Germany and around the world,†Cut. IT is J., vol. 24, no. 3, p. 6, 2011.

S. Denning, “Why Agile can be a game changer for managing continuous innovation in many industries,†Strategy. Leadersh., vol. 41, no. 2, pp. 5–11, 2013.

M. Alqudah and A. Abdulsalam, “Implementing computer-aided language learning tool using the hybrid agile method: A case study,†in Proceedings - 2013 International Conference on Informatics and Creative Multimedia, ICICM 2013, 2013.

M. Alqudah and A. Abdulsalam, “Basic English language tools for beginners: Using animations and audio,†Int. J. Sci. Eng. Res., vol. 4, no. 4, pp. 228–233, 2013.

L. Abdulwahab, A. A. Abdalla, B. S. Galadanci, M. Algudah, and M. Murtala, “Agile Methods for Software Engineering Students Project: A Proposed Hybrid Methodology,†in The Third International Conference on Digital Enterprise and Information Systems (DEIS2015), 2015, vol. 63.

J. Sutherland and K. Schwaber, “The scrum guide. The definitive guide to scrum: The rules of the game,†Scrum. org October 2013.

J. López-Mart’inez, R. Juárez-Ram’irez, C. Huertas, S. Jiménez, and C. Guerra-Garc’ia, “Problems in the Adoption of Agile-Scrum Methodologies: A Systematic Literature Review,†in Software Engineering Research and Innovation (CONISOFT), 2016 4th International Conference in, 2016, pp. 141–148.

D. J. Anderson, “Kanban.†Blue Hole Press Sequim, WA, 2010.

Z. Mansor, S. Yahya, and N. H. Arshad, “Towards the Development of Success Determinants Charter for Agile Development Methodology,†Int. J. Inf. Technol. Eng., vol. 2, no. 1, pp. 1–7, 2011.

M. Alqudah and R. Razali, “A review of scaling agile methods in large software development,†Int. J. Adv. Sci. Eng. Inf. Technol., vol. 6, no. 6, 2016.

A. A. Hamid and Z. Mansor, “Client’s Readiness Assessment Success Factors for Outsourcing Software Projects,†Int. J. Adv. Sci. Eng. Inf. Technol., vol. 6, no. 6, 2016.

H. Lei, F. Ganjeizadeh, P. K. Jayachandran, and P. Ozcan, “A statistical analysis of the effects of Scrum and Kanban on software development projects,†Robot. Comput. Integr. Manuf., vol. 43, pp. 59–67, 2017.

D. I. K. Sjøberg, A. Johnsen, and J. Solberg, “Quantifying the effect of using kanban versus scrum: A case study,†IEEE Softw., vol. 29, no. 5, pp. 47–53, 2012.

S. Govindaraj and S. Tadipatri, “Use of Kanban in distributed offshore environments,†Viral Growth Kanban Enterp. Cut. IT J., 2011.

V. T. Heikkila, M. Paasivaara, and C. Lassenius, “Scrumbut, but does it matter? a mixed-method study of the planning process of a multi-team scrum organization,†in Empirical Software Engineering and Measurement, 2013 ACM/IEEE International Symposium on, 2013, pp. 85–94.

S. Ashraf and S. Aftab, “Latest Transformations in Scrum: A State of the Art Review,†Int. J. Mod. Educ. Comput. Sci., vol. 9, no. 7, pp. 12–22, 2017.

C. Kaur1st and V. Kumar 2nd, “Product Backlog Prioritization in Scrum: A Review,†Int. J. Mod. Comput. Sci., vol. 3, no. 2, 2015.

V. Moskalenko, “Scrum vs. Kanban: Which to Choose for Agile Development?†2015. [Online]. Available:

Y. Andriyani, “Knowledge Management and Reflective Practice in Daily Stand-Up and Retrospective Meetings,†in International Conference on Agile Software Development, 2017, pp. 285–291.

V. G. Stray, Y. Lindsjorn, and D. I. K. Sjoberg, “Obstacles to efficient daily meetings in agile development projects: A case study,†in Empirical Software Engineering and Measurement, 2013 ACM/IEEE International Symposium on, 2013, pp. 95–102.

A. Khosravi, T. J. Gandomani, and H. Fahimian, “Introduction of a scrum in an elite team: A case study,†J. Softw., vol. 12, no. 3, pp. 173–180, 2017.

M. Alqudah, Y. Yusof, S. A. M. Noah, and A. Almabhouh, “Incorporating Prioritized User Preferences in Search System,†Int. J. Adv. Sci. Eng. Inf. Technol., vol. 2, no. 5, pp. 401–404, 2012.

M. K. Al-Qudah, “A Weighted-Based Approach To Prioritize User Preferences In Information Retrieval,†Universiti Utara Malaysia, 2008.

A. Bolaji, “A cross-disciplinary systematic literature review on Kanban,†Master’s Thesis. The University of Oulu. 62 p. Available at: http://jultika. oulu. fi/files/nbnfioulu-201502111073. pdf, 2015.

T. Skeie, “Does Limit on Work-In-Progress (WIP) in Software Development Matter?†2014.

M. O. Ahmad, J. Markkula, and M. Oivo, “Kanban in software development: A systematic literature review,†in Software Engineering and Advanced Applications (SEAA), 2013 39th EUROMICRO Conference on, 2013, pp. 9–16.

B. Estácio, R. Prikladnicki, M. Morá, G. Notari, P. Caroli, and A. Olchik, “Software kaizen: Using agile to form high-performance software development teams,†in Agile Conference (AGILE), 2014, 2014, pp. 1–10.

O. Badreddin, “Empirical evaluation of research prototypes at variable stages of maturity,†2013 2nd Int. Work. User Eval. Softw. Eng. Res. USER 2013 - Proc., pp. 1–4, 2013.

G. S. Matharu, A. Mishra, H. Singh, and P. Upadhyay, “Empirical study of agile software development methodologies: A comparative analysis,†ACM SIGSOFT Softw. Eng. Notes, vol. 40, no. 1, pp. 1–6, 2015.

C. Ladas, “Scrumban,†Lean Softw. Eng. Contin. Deliv. High Qual. Inf. Syst., 2008.

M. Yilmaz and R. O’Connor, “A scrumban integrated gamification approach to guide software process improvement: a Turkish case study,†The. Vjesn. (Technical Gazette), vol. 23, no. 1, pp. 237–245, 2016.

A. Reddy, The Scrumban [r] evolution: Getting the Most Out of Agile, Scrum, and Lean Kanban. Addison-Wesley Professional, 2015.

H. Dunsky, A case for Scrumban. 2014, pp. 1–10.

J. Similä, M. Oivo, and K. Liukkunen, “Empirical Investigation of Scrumban in Global Software Development,†in Model-Driven Engineering and Software Development: 4th International Conference, MODELSWARD 2016, Rome, Italy, February 19-21, 2016, Revised Selected Papers, 2017, vol. 692, p. 229.

Aniruddha Joshi and M. Sandeep, “Our Journey into Scrumban,†2014. [Online]. Available: [Accessed: 20-Jul-2017].

S. Pahuja, “What is Scrumban,†Agile Alliance, 2015. [Online]. Available: [Accessed: 20-Jul-2017].

A. Banijamali, R. Dawadi, M. O. Ahmad, J. Similä, M. Oivo, and K. Liukkunen, “An empirical study on the impact of Scrumban on geographically distributed software development,†in Model-Driven Engineering and Software Development (MODELSWARD), 2016 4th International Conference on, 2016, pp. 567–577.

K. Krippendorff, Content analysis: An introduction to its methodology. Sage, 2012.

M. O. Ahmad, P. Kuvaja, M. Oivo, and J. Markkula, “Transition of software maintenance teams from Scrum to Kanban,†in System Sciences (HICSS), 2016 49th Hawaii International Conference on, 2016, pp. 5427–5436.

P. Brodzinski, “When Kanban is the Best Choice,†2010. [Online]. Available:

S. W. Ambler and M. Lines, “Going Beyond Scrum: Disciplined Agile Delivery,†Discip. Agil. Consortium. White Pap. Ser., 2013.

A. Bolboaca, “Agile Challenge: Adopting Technical Practices,†Mozaic works, 2013. [Online]. Available: [Accessed: 01-Mar-2016].

M. Alqudah and R. Razali, “Key factors for selecting an Agile method: A systematic literature review,†Int. J. Adv. Sci. Eng. Inf. Technol., vol. 7, no. 2, 2017.

F. Kanwal, K. Junaid, and M. A. Fahiem, “A hybrid software architecture evaluation method for fdd-an agile process model,†in Computational Intelligence and Software Engineering (CiSE), 2010 International Conference on, 2010, pp. 1–5.

M. Alqudah and R. Razali, “A comparison of scrum and Kanban for identifying their selection factors,†in Electrical Engineering and Informatics (ICEEI), 2017 6th International Conference on, 2017, pp. 1–6.



  • There are currently no refbacks.

Published by INSIGHT - Indonesian Society for Knowledge and Human Development