5 reasons to use Kanban

Kanban is a popular agile framework based on the continuous flow model. But should you use it? Let’s have a look on five good reasons to do Kanban.

#1 Being able to release anytime

If you are using Scrum, you are not expected to make releases in the middle of an iteration. In Kanban, tasks are delivered continuously on an as-needed basis. When a User Story is done, you can make a release. Therefore, our customers will benefit from the new functionality as soon as possible. Of course, this doesn’t come for free. It is quite a challenge to setup the development process in this way. But it is worth it.

#2 Being able to change the priorities on the fly

In Scrum, you can’t add User Stories on the fly into the Sprint or at least it is not a simple process. In Kanban, if there is an urgent request to implement or an important new User Story, the team can just put it on the top of the queue. It will be taken care of as soon as a free slot is available.

#3 No need for iterations

Why do we need iterations? They are perfect for getting into a development rhythm and to establish rituals. However, after the point of having the flow established, iterations may become an unnecessary waste. 

#4 Productivity increase

Kanban is using lead time and cycle time to measure its productivity. Lead time is the time between receiving a request and delivering the ticket back to the customer. Cycle time measuring starts, when a ticket enters the “in progress” stage and ends at the delivery, too. Teams using Kanban are continuously trying to reduce both lead and cycle times and reach higher customer satisfaction. The key strategy to keep the cycle times down is using a limit on the work in progress. Another way to improve productivity is the “cycle time scatterplot”, which lets you quickly spot any impediments by analyzing tasks that have a much longer cycle time than the rest. Once identified, you can begin to tackle the root cause of the delays.

#5 Perfect flow visualization and management

Kanban board provides a very clear view of the current work in progress. It visualizes the development flow and supports fast planning and tracking. Kanban uses a “pull system” that allows team members to only pull new tasks once the previous tasks are done.

 

So, what do you think? Are these 5 reasons good enough for you to consider Kanban for your next (or current) project?

You may also like:

Our first Kanban meetup

On 29.4.2019, the RWS Group Scrum masters team got together in Mikulov for a rather unique meeting. One of the biggest advantages of our meetup, and…