Skip to main content

What does the Kanban board do?

Is it just about placing post its all over the wall?

Core of lean is visual management which is seen as having a board and placing all the open tasks on that. But there is more to visual management.  Visual management also means;


  • information exchange
  • improve transparency
  • surface problems faster

Typically Kanban board helps;
  1. Visualization of tasks of a team; task state and impediments
  2. Regular update and share of information during daily stand-up
  3. Reflection of process
Team should try to teach a state where rate of "inflow of tasks" matches rate of outflow. Else tasks will keep on piling in different states (i.e. ready, in-work etc) and create an inventory which team will not be able to resolve quickly.

Always high priority tasks are closed faster. So you will speed up results and identify and resolve impediments faster.

But often people ask one question, why working with paper when modern electronic equipment and tools are available?

The answer is "brain friendly".
  • Information provided visually are processed faster. People are more likely not to open and see excel sheet or web pages.
  • When people touch and write using pen/paper, they tend to receive information from several senses. Brain absorbs more information.
  • Physical activity supports cerebral activities. So meetings standing at the board create emotional identification and lead to higher level of involvement.

This all together results in greater intellectual and emotional involvement and a more effective communication between team members.

Nevertheless, you still need digital support when teams are not co-located.

There is no perfect solution. You need to inspect and adapt the process around all the time to make it for for your team. Never stop innovating.


Comments

Popular posts from this blog

Where do Scrum and Kanban fit?

I hear a question more often if agile is under the Lean umbrella, "so what is Kanban, and how does it compare to Scrum?” Scrum and Kanban are similar in certain aspects. In some others ways they are different. I am not talking about the similarity/differences here. Let's keep them aside for the time being. But lets understand under what circumstances how we can make best use of one over the other. Also can we combine them? If so, when? The image below is more of self explanatory. The axes represent how much risk involved in the project versus the focus. Here risk emphasizes the exploratory of innovative nature of the work. More exploratory, more the risk of failure and thus risk appetite of organisation is on the higher side.

Ask yourself, Are you a Scrum Master ???

A scrum master can make or break an agile transformation. Often asked what is the role of a conductor in an orchestra. Answer is simple (as once explained by Jobs). Members are good at playing their instruments. But the conductor plays the orchestra. So be careful when you are the scrum master. What you are supposed to do; A Servant Leader : empathetic listener and healer. This self-aware steward is committed to the growth of people.  A Coach can coach the other team members on how to use Scrum in the most effective manner.  Also to coach the PO and organization. The Framework Champion is an expert on how Scrum works and how to apply it.  The Problem Solver protects the team from organizational disruptions or internal distractions or helps remove them.  The Facilitator is a neutral participant who helps a group of people understand their common objectives and assists them to achieve these objectives. And if you are indulged in below activities, realize yo...