Presentation of Kanban

2. Kanban :
Is a scheduling system for lean and Just-in-time ( JIT ) production.
Kanban is a system to control the logistical chain from a production point of view,
and is an inventory control system.
Kanban was developed by Taiichi Ohno, an industrial engineer at Toyota,
as a system to improve and maintain a high level of production.
Kanban is one method to achieve JIT.
Kanban became an effective tool to support running a production system as a whole,
and an excellent way to promote improvement.

3. Just-in-time
also known as just-in-time production or the Toyota production system (TPS),
is a methodology aimed primarily at reducing flow times within production as well as response times from
suppliers and to customers.
Following its origin and development in Japan, largely in the 1960s and 1970s and particularly at Toyota,
JIT migrated to Western industry in the 1980s,
where its features were put into effect in many manufacturing companies—as is attested to in several books
and compendia of case studies and articles from the 1980s.

4. Just-in-Time (JIT) means to produce, deliver, or purchase
only the materials required,
only in the amounts required,
only when required.
If the JIT system is perfectly implemented, a perfect production system
(low inventory, minimum labor, smallest work space, etc.) can be achieved.
So, although implementation of the JIT methodology will necessarily differ depending on type of industry, size,
or company history, significant improvement will be realized in every situation.
To successfully adopt JIT, you must know what you need, how many, and when.
The best way to monitor these three elements of JIT is to ensure that each "next-process“
takes only the necessary items, in the necessary quantity and only when required, from the "previous-process".
This is called a "Pull" system.
When the "previous-process" manufactures only the number of items to be used in the "next-process",
it is called "Replenishment Production".
JIT is based on these two principles.

5. WIP (Work in progress )
are a company's partially finished goods waiting for completion and eventual sale or the value of these items.
These items are either just being fabricated or waiting for further processing in a queue or a buffer storage.
The term is used in production and supply chain management.

6. Kanban primarily follows four core principles:
1. Visualize work
Create a visual model of work and work flow, so as to observe the flow of work moving through the Kanban system.
Making the work visible, along with blockers, bottlenecks, and queues, instantly leads to increased communication
and collaboration.
2. Limit work in process
Limit how much unfinished work is in process and reduce the time it takes an item
to travel through the Kanban system. Problems caused by task switching and the need to constantly reprioritize
items can be reduced by limiting WIP.
3. Focus on flow
By using work in process (WIP) limits and developing team-driven policies,
the Kanban system can be optimized to improve the smooth flow of work,
collect metrics to analyze flow, and even get leading indicators of future problems by analyzing the flow of work.
4. Continuously improve
Once the Kanban system is in place, it becomes the cornerstone for a culture of continuous improvement.
Teams measure their effectiveness by tracking flow, quality, throughput, lead times, and more.
Experiments and analysis can change the system to improve the team's effectiveness.

7. With kanban boards, you can:
•Visually see work in progress
•Instantly understand impediments (things causing you to delay) and take steps to remove them
•Improve communication between yourself and others on your team
•Empower teams to self-manage visual processes and work flows
•Inspire team collaboration
•Kanban Boards are Visual

8. Visual management helps project managers and team members sort through moving parts and pieces by providing visual
cues for the team members doing the work.
Because kanban boards are visual, users don’t need to muddle through a correspondence thread
to find the piece of information they need to get started on a task.
You don’t have to decipher the information on a massive spreadsheet to determine whether a task
or project has been started or completed.
Using a kanban board, the answer to so many questions will become, “It’s on the board!”

9. Kanban Boards are Flexible
Above all else, Kanban boards are flexible.
Using a kanban board is as easy as writing a sticky note and pasting it
to a whiteboard, so anyone can use them for just about any purpose.
The Kanban method provides guidelines for how to use a kanban board,
however many people who use them do not follow this methodology.

10. Kanban Boards are Easy to Use
If you have ever used sticky notes on a whiteboard to plan and prioritize work,
then you can hit the ground running with an online kanban board.
online kanban boards can be configured any way you want to mirror your specific project.
Cards can be created within seconds and moved around the board by dragging and dropping anywhere.

11. Kanban Boards Help Teams Collaborate
Anyone who has ever managed a project can appreciate the effectiveness of using a kanban board
as the best way to collaborate.
Project managers can spend less time communicating status updates using kanban boards
because the boards create transparency.
Team members working either on-site or remotely can see the status or a project in real time.
So, instead of spending hours per day liaising, project managers can focus on the important stuff.

12. Kanban Boards Increase Efficiency and Help Reduce Waste
Kanban boards have proven to be the best solution for managers looking to cut waste and improve
overall efficiency. Waste in the business world can take on several forms, including:
•Overproduction
•Waiting
•Transportation
•Non-value-added processing
•Inventory
•Under-utilizing people
•Defects
•Motion
•Kanban Boards Lead to Increased Productivity
Kanban boards are effective at helping teams become more productive while reducing
the amount of work load stress many project managers, developers and team members feel during a project lifecycle.

13. Advantages of Scrum Advantages of Kanban
Transparency Flexibility
Improved credibility with clients Focus on continuous delivery
High product quality Increased productivity and quality
Product stability Increased efficiency
Team members reach sustainable pace Team members have ability to focus
Allows client to change priorities and
requirements quickly
Reduction of wasted work/wasted time

14. Create board Kanban

18. Workflow MDK

19. lBramoe
lBramantya.putra@ansvia.com