Kanban
Introduction
Kanban is a very flexible and easy to implement method for process improvement.
The idea of Kanban is visualising the workflow to achieve process improvement.
                 Finding Inefficiencies/ Issues in the Process
Fun fact
One of the main differences of Kanban compared to other processes is that it explicitly establishes
an upper limit to work in progress inventory to prevent overcapacity.
Less is more to get results (Remember how the Google landing page looks like).
However, as human beings, we are tempted to get trapped with Complexity Bias.
While other tasks have moved, task 3 is yet to move and after some days, it still hasn’t move. This
suggests that the task is taking longer time than it should or a longer time than a task usually takes.
For Kanban to work properly, it should be ensured that all task takes nearly the same amount of
time and flow at a similar rate.
This means that if there is a big tasks that has to be broken down into smaller sized tasks, a common
practice adopted is to add a new column at the beginning with the step named as
‘scoping/analysing/specifying’ where the main agenda is to create task of equal size for the rest of
the flow.
alwasys
Always remember that in kanban, tasks shoulf be of equal soze.
Kanban Board Template Example
The Kanban board template depicted below represents a software delivery process on a Kanban board.
Let's pay attention to the following characteristics of this Kanban board example:
• It highlights the tasks of the software development team including epics and user stories.
• The values circled below column headings specify the maximum number of Kanban cards (Work In
Progress Limit, WIP Limit) that can be simultaneously processed in a given phase.
• Below certain columns, it specifies explicit policies, which are also known as done rules.
• It encompasses a Kanban workflow management feature to divide certain columns as "Ready" and
"In Progress". The WIP limit applies to both sub-columns to ensure that the associated teams and
workflow stages are not overwhelmed due to excessive number of tasks (Kanban cards) on a single
column (phase of workflow).
MVP is based on lean start-up philosophy which implies iterative process of building, measuring and
learning loop until the product meets the market need completely.