{"id":30976,"date":"2019-09-02T15:50:14","date_gmt":"2019-09-02T13:50:14","guid":{"rendered":"https:\/\/zenkit.com\/?p=30976"},"modified":"2023-07-18T14:14:56","modified_gmt":"2023-07-18T12:14:56","slug":"kanban-vs-scrum","status":"publish","type":"post","link":"https:\/\/zenkit.com\/en\/blog\/kanban-vs-scrum\/","title":{"rendered":"Kanban vs Scrum"},"content":{"rendered":"
<\/p>\n
Kanban and Scrum are two popular project management methodologies<\/a> that are commonly used by teams looking for an agile<\/a> approach to delivering a product. <\/span>But do you know when to use which? While this article is titled “Kanban vs Scrum”, our intention is not to battle the two methods up against each other, but instead, to detail the similarities and differences so you understand the best circumstances of when to use either method.<\/p>\n So, without further ado…<\/p>\n Kanban<\/span><\/a> is a scheduling system that visualizes the workflow process and the work passing through. Part of Lean<\/a> and Just-in-time (JIT) manufacturing<\/a> was derived from the manufacturing industry by Toyota employee, Taiichi Ohno<\/a>, in the 1940s. <\/span>Since then, Kanban has evolved into the visual scheduling system that many of us are familiar with today.<\/span><\/p>\n The Kanban method aims to reduce waste, continuously improve the process, and increase overall productivity. <\/span>While there are no established rules of how Kanban works, there are <\/span>six general practices<\/span><\/a> that should be applied to ensure optimized Kanban use. They are:<\/span><\/p>\n The visual nature of Kanban allows you to identify any<\/span> bottlenecks early on in the development process, enabling you to deliver a higher-quality product. <\/span>It does this with the help of Kanban tools such as a Kanban board, Kanban cards, and sometimes even Kanban swimlanes.<\/span><\/p>\n<\/p>\n
\nWhat Is Kanban?<\/strong><\/h2>\n
\n
Kanban board<\/strong><\/h3>\n