Scrum vs Kanban | 6 differences

Показать описание

In this video, you will get 6 main differences between Scrum and Kanban.
Agree, everyone, who knows the word agile has somehow come across such concepts as Kanban or Scrum. And a lot of people have always wondered what is better to use in their work: Scrum or Kanban. In this article, I will try to explain in as much detail as possible, but at the same time briefly explain and show the main differences between these two agile streams.

00:01 Introduction
00:58 What is Scrum?
01:30 What is Kanban?
02:46 Difference between Kanban and Scrum
05:55 Scrumban

Before we talk about the differences, let's briefly (just very briefly) brush up on what Scrum is and what Kanban is.

According to the Scrum Guide (the holy book for all Scrum fans), Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems. In other words, Scrum requires detailed and restrictive planning and has predefined processes and accountabilities. In Scrum, the work is divided into smaller tasks that must be completed in a predefined period (Sprint). Also, adding new work items during a Sprint is highly discouraged, making new work waiting for a new Sprint and reducing the team's ability to react to change. The Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts. These events are specifically designed to enable the transparency required. Failure to operate any events as prescribed results in lost opportunities to inspect and adapt. Events are used in Scrum to create regularity and minimize the need for meetings not defined in Scrum.

Kanban is a method (if you want) or a visual system for optimizing and managing workflows, which lets you visualize processes on a Kanban board and continuously process work items. Kanban's goal is that workflow should proceed smoothly at an optimal speed. The work in progress limits at each workflow stage allows your team to use its capacity optimally. In other words, Kanban helps you optimize your existing process with a set of principles. The main objective of implementing Kanban is to identify potential bottlenecks in the process and fix them.

Let’s compare Scrum and Kanban and understand the main difference between these 2 techniques. There are many similarities and many differences between Kanban and Scrum. I am not sure it is correct to publish all of them.

At least it will not be informative. So, I’ve decided to add the six most important differences between Kanban and Scrum to help you understand the real difference.

The first is Roles or accountabilities. In Kanban there are no pre-defined roles for a team. Although there may still be a Project Manager or even the Product Owner, the team is encouraged to collaborate and chip in when anyone becomes overwhelmed.
In Scrum there are following accountabilities: Scrum Master, Product Owner, and Developers. Each Scrum Team member has a predefined accountability

Then Delivery cycle
In Kanban products and processes are delivered continuously on an as-needed basis (with due dates determined by the business as needed).
In Scrum Regular, fixed-length Sprints. The Sprint cycle lasts one to four weeks (or a maximum month)

The next is Change policy
In Kanban it can be incorporated at any time. Allows for changes to be made to a project mid-stream, allowing for iterations and continuous improvement before completing a project.
In Scrum it is generally not made during the Sprint, but it is ok to add new items into the Sprint Backlog (without contradiction to the Sprint Goal). If required, A Sprint could even be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.

Then Delegation & Prioritization
Kanban uses a “pull system,” or a systematic workflow that allows team members to only “pull” new tasks once the previous task is complete.
Scrum also uses a “pull system”; however, an entire batch is pulled for each iteration.

Artifacts
There is one well one known artefact in Kanban - the Kanban board. In Scrum there are 3 products: Product Backlog, Sprint Backlog, Increment.

And the last is measurement of Productivity
Kanban measure productivity using “cycle time,” or the time it takes to complete one entire piece of a project from beginning to end.
Scrum measures productivity using velocity through sprints. Each sprint is laid out back-to-back and/or concurrently so that each additional sprint relies on the success of the one before it.

Tips to pass Scrum Master exam:
►Try our Scrum Master exam simulator with 320 questions with detailed explanations and professional references for every question.