Kanban for skeptics

How lucky are we, to be working in a field that has so many new interesting evolutions?

beware that the difference between theory and practice is significant

In many cases, experiencing delivered features gives them new ideas and insights

concept of a Minimum Viable Product (MVP) can offer a solution.
An MVP is not a minimal product, it is a strategy for creating and selling a product to customers. It is an iterative learning process until the product fits the market, or is cancelled.

The purpose of WIP limits is to make it easier to work in a pull system that is more effective from start to end. The WIP limits will signal an uneven balance in your flow. From that point, you can start working on improving it

Many Kanban implementations use an expedite lane to deal with emergencies. This is a horizontal lane that spreads across all workflow stages and has a WIP limit of it’s own. When an emergency arrives, it is pulled through the expedite lane with priority over all other work items.

Reality proves to be different, even in Kanban land. When an emergency arrives, it needs to be dealt with, immediately! This means WIP limits can be broken. However, the decision needs to be made very consciously because of the impact.

In Kanban bugs cause the flow to be interrupted and people to get stuck because of WIP limits that are reached. It’s no longer possible to sweep this under the carpet. If quality is not reaching our defined standards, it must be fixed immediately

In Kanban bugs cause the flow to be interrupted

Thanks to the clear focus on end to end flow, the team makes sure they keep working in a pull system, driven by customer demand.