Which agile development framework to choose AKA from Scrum to Scrumban

In 2024, over 86% of software development companies use an agile approach for developing their products and services. The method is also quickly expanding into other areas – for example, marketing, healthcare, education, and even construction – where there is a need to efficiently execute different projects.

The agile approach differs from a traditional one in its values, which are listed in the Agile manifesto compiled in 2001. A summary of it would be that the method is based on flexibility, quickly reacting to changes, and collaboration between teams. Implementing the method helps to create different solutions more efficiently, of a better quality, and to ensure that the end results better meets the customer or user needs.

There are various frameworks that use this mindset in the agile world. The most popular ones are Scrum, Kanban, and their hybrid form Scrumban. Each framework has its own approach that is suitable for realising different kinds of projects based on their nature. In this post, we will describe the three most popular frameworks and their properties to help you make the best decision for your project.

What is Scrum?

Scrum is one of the very first agile frameworks, which is based on the teams’ close cooperation with the users. The first version of the Scrum framework was developed in the 1980s – so even before the agile method was defined. It is currently the most popular agile framework and used by about 66% of companies that implement an agile approach. The main principles of Scrum are cooperation, the project’s iterative progress, and adapting to changes.

The Scrum framework

Scrum is a clearly defined project management framework that consists of the following parts:

It should be said that, as with a lot of other popular frameworks, the Scrum framework also does not define how the project tasks should be divided up or evaluated.

To prove a person’s knowledge of the Scrum framework, various accredited institutions also give out appropriate certificates. You can read more about how Trinidad Wiseman’s specialists acquired their Scrum Master certificates from our article “What is a Scrum Master certificate and how can you get one?”. 

What is Kanban?

Kanban principles and components

At the core of Kanban is a visual board where all of the tasks are displayed in columns on cards with various details on them – name, person responsible for the task, deadline etc. The columns reflect the different statuses of the project task, for example selected for development, in progress, on hold, and done. The cards move across the board according to their current status.

Boards like this are also used by various project management softwares, such as Atlassian Jira. The purpose of this kind of board is to create transparency in the work being done, to help keep track of how the project tasks are progressing, and to identify any bottlenecks and opportunities for improving the workflow.

Every column on a Kanban board is limited to a specific number of cards to limit the amount of functionalities being worked on at a time (Work in Progress, WIP). This is necessary for creating a smooth workflow and for ensuring that the team is not overwhelmed by tasks.

Kanban supports continuous delivery of tasks or releases. As soon as tasks are completed, they are also released. They are considered ready once they meet the Definition of Done AKA everything meets the quality standard. This helps to also avoid the accumulation of incomplete tasks in a workflow.

The Kanban framework emphasises continuous improvement, tracking and optimisation. Teams meet on a regular basis to discuss how they could improve their workflows, use their resources more efficiently, and learn from their experiences. User-centered design is also very important in this framework and helps the teams to focus on the most important tasks that create the most value.

The Kanban framework also utilises the Product Backlog and task ordering. Tasks are selected for development from the backlog by placing them on the Kanban board. The developers then choose which tasks to work on from that list (pull system).

Kanban vs Scrum

The Kanban and Scrum frameworks have a lot in common. The processes of both emphasise user-centricity, the constant improvement of teams and their work, and transparency in the project. Both frameworks also place importance on task ordering to create maximum value.

The advantage of Kanban is that it is easy for the development team to adapt to since it uses visual tools and is not limited to different roles, events or time limits. It does not involve complex rules or strict process descriptions. Every team can adapt the framework to the needs of their product/service or team.

It is also possible to choose between Scrum and Kanban dependent on what phase the project is currently in. During the active development phase, Scrum could be used, and for the maintenance and smaller follow-up developments phase, the team can switch over to Kanban.

Scrumban – the best combination of the two

In software development, Kanban is often used with Scrum, a hybrid called Scrumban. Implementing the Scrumban framework has become increasingly popular in various organisations.

Scrumban principles and components

Scrumban combines the advantages of both approaches, which means that its implementation brings both flexibility and structure to a project – the workflow is managed in a flexible manner, it is visualised on a board, but there are also work cycles (Sprints) and planning events.

Scrumban is suitable for projects where the requirements and priorities are constantly changing, but it is still important to have a regular overview of all the processes, which enables preventing any possible issues. If needed, tasks can be added to a cycle or existing ones changed, and the team does not need to wait for the end of a cycle to take on new tasks. Regular meetings help ensure that there are no shortcomings in the communication.

Work cycles are managed by limiting tasks (WIP). Once the number of “selected for development” tasks falls below a set limit, it is time for a new planning meeting. Work cycles are kept short to be able to adapt to any changes. Ideally, they are 2 weeks long.

Ordering tasks is still important within the Scrumban framework as is their level of detail in the Product Backlog. The pull system is used, meaning that the development team chooses their own tasks to work on from the “selected for development” column.

Examples of how the different frameworks are used

Scrum may be most suitable in a situation where it is necessary to create a business critical information system based on specific business needs and the Product Owner’s clear vision.

For example, the plan is to release a new product on the market in one year and it is necessary to create a self-service environment that enables the user to create regular and complex order plans.

Or maybe the company wishes to create a new technology or improve an existing one – for example, a drone that needs to be able to fly twice as higher and further than currently and be capable of taking high-quality photos.

At Trinidad Wiseman, we have used the Scrum framework when working on huge information systems and self-service environments. For example, we helped create the self-service environment of the Labour Inspectorate, which is used internally by the Labour Inspectorate to conduct proceedings, and which also includes a client portal and tools meant for employers.

Kanban is suitable for systems where the product vision is still hazy and will become clearer as the work is being done.

For example, there is an existing information system for which a regular continued development cycle is planned. User feedback is collected for a new functionality to be created, requirements are defined based on the wishes expressed, and the application is then developed iteratively. While adding new features to the product is the broader goal and creates a regular rhythm, there is no specific time criticality nor a precisely defined goal.

At Trinidad Wiseman, we have done additional developments for various projects. For example, we created the Digital Traffic Accident Notification System for the Estonian Motor Insurance Bureau. Once the project was completed, it moved on into the additional developments phase.

Sometimes, the framework may need to change based on the development phase. For example, we used the Scrumban approach when creating the Haldusnet information system for Kvatro. Once the active development phase was over, the project switched over to Kanban for the maintenance phase. After a while, new needs for the information system became apparent and, based on their business criticality, the works that needed to be done for those needs to be met were done using Scrumban once again.

Conclusion

Scrum, Kanban, and their hybrid Scrumban are the most popular frameworks based on the agile methodology. These frameworks do not compete with one another and each create a different kind of value. Every team can choose the framework that is most suitable for their goal, the project requirements, the nature of the work, and the team’s habits. It is important to understand the advantages and disadvantages of each framework to be able to make the right decision when choosing a framework to achieve the best possible result when creating a product or service.

This quiz can help you find the most suitable framework for your project.