This article has been conducted according to “The Proposed L-Scrumban Methodology to Improve the Efficiency of Agile Software Development” by Aysha Abdullah Albarqi & Rizwan Qureshi.

We wanted to share with you what we’ve learnt from a beginner’s point of view i.e., my point of view! Sometimes it’s easier to understand a topic removing the complexity that experts bring with their extensive knowledge… 🥱

Either if you are leading a team, or part of it, you know about Scrum and Kanban for sure. But, have you ever heard of Scrumban? Have you ever imagined what could happen if we mix both of them? Do you know what benefits could it bring for your team? Keep reading and we’ll tell you!

As you may know, Scrum and Kanban are two Agile methodologies. Both address primarily the continuous improvement, with basis on the iterative and progressive development to strengthen teams’ response to change and uncertainties.

Let’s get straight to the point : Scrumban = Best of Scrum + Best of Kanban. Unexpected right? Let’s deepen into it. 😉

What are each methodology’s strengths?

The best of SCRUM:

  • Lighting fast. Fastest time-to-market of all Agile approaches.
  • Flexible in action. Allows flexibility to adjust to the plans while in the sprint.
  • Efficient. Works well with complex projects and uncertainty.
  • Defined. Delivering value is easy thanks to be timeboxed.
  • Predictability. Clear vision of the scope of work in the next 2-4 weeks.

The best of KANBAN:

  • Individually flexible. Completely flexible with individual tasks, which end up in fast work.
  • Anti-time waste. Faster processes without idle time.
  • The more the better. Appropriate for larger teams.
  • All for one. Allows focus on one task at a time.
We’re sorry, dino!

So, Scrum is popular for its prescriptive nature and the way in which it helps team to work together, right? Well, on to the blender. Kanban is known for its process of improvement and focus on workflow? On to the blender too. Would be nice to mix the previous strengths of each one. Let’s see what we got from there.

Scrumban: The Agile Fusion

According to the survey conducted by Abdullah, A. & Qureshi, R. (2018), the 73% of the participants were highly agreed that Scrum is insufficient in regard to the management of daily tasks and visualizing workflow. Also, they found out that 89% of the respondants emphasized that Kanban is limited to being a management tool for nothing more than visualizing the work. As both Scrum and Kanban have their limitations, Corey Ladas,came up with this mixture to complement their unique characteristics.

Scrumban methodology has been born as a hybrid of the agile frameworks Scrum and Kanban. It consists of the best aspects of both parts. Scrumban represents the balance between effectiveness and efficiency. In Scrumban, customers are set as the basis. It takes Scrum’s constant need of being close to the customers and be offering value, and it takes Kanban’s focus in process efficiency.

Main benefits of SCRUMBAN ⭐

  • It increases productivity overall, especially with complex projects.
  • It improves interaction between team members at meetings.
  • It allows a better analysis of the performed tasks.
  • It allows to know the actual status of the project process.

Simple guide for implementing Scrumban

As in User-Centered Design, customers are the basis in this process of building the right product.

For performing Scrumban accordingly, we’ll need two types of boards. The general board is managed by the Product Owner and reflects the progress of the work by showing the advance for the whole project. The Scrumban board, is designed to follow the work of the sprint, being managed by both team master and developers.

General & Scrumban boards

🚀 The process starts with the Product Owner speaking to the customer and gathering customer requirements. They’ll be used to create a customer demand list, sorted by its priority based on the customer value. Then, the entire team will meet in order to create the product backlog out of the customer demand list, by filtering waste from it.

The next step is for the Product Owner to move the backlog to the “TO DO” column in the general board. At the same time, the team starts the sprint planning deciding which issues will be completed in that sprint. They will note down the selected issues in the “READY” column in their Scrumban board. After that, the Product Manager will write the issues selected by the team in the “DOING” column in the general board. Now is time for the team to start working on their issues moving them to the “DOING” column on their board.

After finishing the sprint, the team will start testing the new features, moving them to the “TESTING” column in their board. In case they achieved the goal, they’ll move it to “DONE”, and deliver the work to the Product Owner and the customer.

Now it’s time for the Product Owner to move the issues to the “DONE” column in the general board, and to gather feedback from the customer after testing the features. After this, the Product Owner will finally deliver the features to the customer and move the sprint and their issues to the “DELIVERED” column in the general board.

🏁 This is the end of the sprint. Get ready to prepare the next one!

Types of meetings

There are several types of meetings for the different phases of the process (except the Daily meeting):

  • Waste-eliminating meeting: The product manager, team master and developers have to attend this meeting. It has to occur after the product manager has met the customer and created the customer demand list. This meeting allows the team to discard non-important features from the product to focus on the real value. The result is the Product Backlog.
  • Sprint Planning: All team members should attend this meeting. After creating the Backlog, the tasks to be accomplished during the sprint have to be discussed, as well as the sprint time.
  • Daily meeting: 15-minute meeting in which the team master and the developers follow their work by answering: What did we work in yesterday? What are we working on today? What are we going to do tomorrow?
  • Quality-Test meeting: After the sprint, the team master and developers test the produces features before delivering them.
  • Sprint Review: All the team members meet with the customer to deliver the product in order to gather feedback “Customer test”.
  • Sprint Retrospective: Before starting a new sprint, the team master and the developers meet to discuss the last sprint collecting points to improve or experiences on how to overcome mistakes.


Albarqi, Aysha & Qureshi, M. Rizwan. (2018). The Proposed L-Scrumban Methodology to Improve the Efficiency of Agile Software Development. International Journal of Information Engineering and Electronic Business. 10. 10.5815/ijieeb.2018.03.04.

Last updated: 2022-09-22

Recent resources

Back to Top