Why use the Kanban method?
The main objective of the Kanban method is to avoid waste and therefore to produce as accurately as possible, up to and including on-demand production.
In summary, the final objective of the Kanban method is to produce when the customer request is identified.
The origin of the Kanban
Originally the Kanban method was created and adopted by Toyota to optimize its production system.
It is based on the principles of lean management, which aims to continuously improve production processes and therefore productivity.
Coupled with lean six sigma methodologies, kanban is currently being used in the industry for production management and pull stock management.
It is based on the principles of lean management, which aims to continuously improve production processes and therefore productivity. Coupled with lean six sigma methodologies, kanban is currently being used in the industry for production management and pull stock management.
Qu’est ce que la méthode Kanban en gestion de projet ?
In project management, Kaban is called structuring a project from a table with lists. This table is divided into lists of actions identified to carry out a project. For the planning of a web project for example, these tables are often broken down as such:
- the back end
- validated estimates
- les actions en cours
- completed productions to be audited
- the validated actions
- archived actions
The Kanban method today
Many companies, especially startups, have adopted this methodology to implement agile project management.
It allows both an innovative visual management while simplifying the understanding of the context for simplified decision-making. It has become an essential project method.
How to design your kanban with your project team?
The first list in your table consists of the customer request or requests.
The second last list will be the deliverable(s) and the last one the feedback. Between these lists, it is up to your team to define the key steps in the form of a list of actions. This step translates the workflow adapted for the production of your deliverable. It is therefore a question of defining all the key steps to produce the deliverable. These steps can/should take into account the customer’s feedback.
The principle is simple: each action or request is represented by a map, itself stored in a list. When its status changes, for example when the estimate is validated, this action moves to the next step. Thus it is now stored in the following list. You can test the Wekowork Kanban board.
Example of the use of a Kanban by a communication agency
Let’s take the example of a communication agency. This agency receives a request from a client. This customer wants to have a showcase site for his company. This customer request is divided into several sub-deliverables, the sub-deliverables being the functionalities that the customer would like to implement on his site. The customer has identified 5 features, but only has a budget for the first 3.
- The first column of the kanban corresponds to the customer’s requirements. In this example it consists of 5 cards each representing the 5 features.
- Column n°2 could be the estimate column, the estimate of decomposing into 5 under estimate.
- The n°3 collects the actions to be done: these are the 3 functionalities validated by the customer, which are broken down into actions to be produced.
- The fourth column lists the actions in progress: here developers, graphic designers detail the actions on which they are working, functionality by functionality.
- No. 5 is the list of actions taken: for example, the model of the first page of the website created by the graphic designer. This action done can generate a new action to be done by the developer, namely to integrate the first page.
- Column 6 is the list of actions to be validated. At this stage the customer checks and validates the productions carried out. He makes sure that this first page corresponds to his request. In case of validation, the action is moved to column 7, i.e. to the column of validated actions. If the customer requests a modification, the action starts again in the column to be done.
Synthesis: the advantages of the Kanban method for managing a project
The Kanban table today is mainly associated with a visual and agile project management methodology. It can be fully adapted to the different projects and workflows of a company or group.
It allows a clear distribution of roles and actions and thus allows a simplified project management.
Would you like to discover WeKowork?
Try betâ and free version of WeKowork at app.wekowork.com.
You will already be able to take advantage of many key features to manage your projects simply.
Or via our live chat at the bottom right of your screen.