A little more about Kanban

Thinkers had already changed the way of thinking of certain profit-seeking organizations and used employees only as labor. It was then that thinkers, like Edward Deming, saw that these principles of organization were no longer enough. Changing this way of thinking, he saw productivity increase in companies where employees worked for a common good.

From this principle of working for a common good, processes were made for better productivity. Among them, one that we will talk about in this post: Kanban.

Is Kanban really useful?

Kanban was a process created in the late 1940s that was initially implemented by Toyata, initially in a supermarket. In which some flaws in its process were identified, such as waste and poor process visualization. From these failures, it was seen that one way of organizing the functions would be through a well structured framework with well defined functions and times, organized by fields like “To do”, “doing” and “done”. Principles such as real-time delivery and other tools that would be well-defined for the software market with the Kanban manifesto were also created.

Kanban in Software development

From the manifesto created, it is important to keep the principles in mind: explicit conversations, small steps, quality systems, and principles that everyone can understand. Kanban is a process that you must understand when you visualize the Dashboard, having this structure well organized we will easily identify bottlenecks and waste that without organization would not be possible easily.

Kanban is a process that involves more people than processes, you need to have some caution when you want to implement and make changes. To better flow the process, some rules are created. An example of such rules is WIP, which identifies to the team how many tasks can be in one field at a time. This way you do not have overloaded people inside the team, causing in the delay of delivery and less quality.

An important thing to note is that these rules are not set at the beginning of the process and should remain until the end, Kanban is flexible!

With the process adapting to your business it is much easier to organize, but beware, use with caution. Tools are only important if they fit your business and are well managed. Remember that Agile are principles rather than practices.

A little summary

We conclude that kanban is a process that must be understood quickly by technicians and not technicians. A well-structured Dashboard solves problems like waste, overhead in sectors. Its main advantages are fast delivery, flexibility and learning by metrics.

Use whit moderation!