Scrum, Kanban & Scrumban – What’s the difference?

Agile is a big umbrella that covers a number of different approaches, and there is always scope for more. There are so many flavors because agile is a mindset that allows flexibility in its processes. Two of the more popular approaches are Scrum and Kanban.

Scrum and Kanban apply agile principles in their own way to empower effective delivery cycles. “Scrumban” is a term coined for a hybrid approach making use of both Scrum and Kanban principles.

In my article published at Testrail , I have explore the differences among the three methodologies – Scrum , Kanban and Scrumban. Check it out and see which of these methodologies may be right for you. https://blog.gurock.com/scrum-kanban-scrumban/

Here is a brief about the 3 methodologies –

SCRUM

Scrum is the most popular agile framework. It is iterative and incremental in nature and focuses on tight delivery timelines. The release time frame is split into small iterations called sprints. Work items are planned for each sprint in the form of user stories and tasks, which are prioritized based on value. Teams are small, cross-functional and self-organizing, with a product owner, a ScrumMaster and the development team.

Scrum provides channels for communication through ceremonies such as the sprint planning meeting, the daily standup meeting, the sprint demo, and the sprint retrospective, all of which contribute to the overall pace and a flexible approach to software development.

Scrum Task board

KANBAN

Kanban is focused on continuous delivery based on lean principles. It’s based on the flow of work and just-in-time delivery and promotes process improvement. Kanban aims to eliminate waste, increase productivity and efficiency, and have flexibility in production. The main goals are to limit work in progress (WIP), avoid multitasking and recognize bottlenecks.

The Kanban board essentially consists of three phases: Input, Work in Progress and Output. Columns under each designation can be used to signify more important tasks and priorities. The tasks in backlog are added to the board with small descriptions and are assigned to team members using the “pull” principle, based on priorities.

Here is a useful sketch I found to illustrate the difference between Scrum & Kanban–

Differences- Scrum vs Kanban

SCRUMBAN

First introduced a decade ago by Corey Ladas, Scrumban was intended as a transitional state for Scrum teams moving to Kanban but later emerged as a framework of its own. It now leverages elements of Scrum and Kanban and focuses on continuous work with short cycles for planning.

Fundamentally, Scrumban is a management framework that emerges when teams employ Scrum as their chosen way of working but use Kanban as a way to view and understand work and continuously improve their processes.

Tasks are taken up using the “pull” principle from the backlog of items on the board, so people can decide to take up the task they want. WIP limits are used to avoid bottlenecks and delays. Once all current backlog items are done and the backlog column is empty, it is a trigger for the next planning, so planning happens on-demand as needed.

Scrumban board

Please click here to read the full article — > on the Gurock TestRail blog site.

Please like, comment and follow the blog for more interesting articles!

Thanks

Nishi