{"id":161030,"date":"2019-09-02T13:50:14","date_gmt":"2019-09-02T11:50:14","guid":{"rendered":"https:\/\/zenkit.com\/blog\/kanban-vs-scrum\/"},"modified":"2025-10-10T11:02:38","modified_gmt":"2025-10-10T09:02:38","slug":"kanban-vs-scrum","status":"publish","type":"post","link":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/","title":{"rendered":"Kanban vs Scrum"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-91109 size-full\" src=\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum-Header.jpg\" alt=\"Kanban vs Scrum\" width=\"1140\" height=\"400\" srcset=\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum-Header.jpg 1140w, https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum-Header-300x105.jpg 300w, https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum-Header-1024x359.jpg 1024w, https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum-Header-768x269.jpg 768w\" sizes=\"auto, (max-width: 1140px) 100vw, 1140px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Kanban and Scrum are two <a href=\"https:\/\/zenkit.com\/en\/blog\/10-most-popular-project-management-methodologies\/\">popular project management methodologies<\/a> that are commonly used by teams looking for an <a href=\"https:\/\/zenkit.com\/blog\/agile-methodology-an-overview\/\">agile<\/a> approach to delivering a product. <\/span>But do you know when to use which?<img loading=\"lazy\" decoding=\"async\" class=\"wp-image-30985 size-full\" src=\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/KanbanvsScrum.jpeg\" alt=\"\" width=\"1236\" height=\"827\" srcset=\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/KanbanvsScrum.jpeg 1236w, https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/KanbanvsScrum-300x201.jpeg 300w, https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/KanbanvsScrum-768x514.jpeg 768w, https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/KanbanvsScrum-1024x685.jpeg 1024w\" sizes=\"auto, (max-width: 1236px) 100vw, 1236px\" \/><\/p>\n<p>While this article is titled &#8220;Kanban vs Scrum&#8221;, 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<p>So, without further ado&#8230;<\/p>\n<hr \/>\n<h2 style=\"text-align: center;\"><strong>What Is Kanban?<\/strong><\/h2>\n<p><a href=\"https:\/\/zenkit.com\/blog\/kanban-explained-what-youve-always-wanted-to-know\/\"><span style=\"font-weight: 400;\">Kanban<\/span><\/a><span style=\"font-weight: 400;\"> is a scheduling system that visualizes the workflow process and the work passing through. Part of <a href=\"https:\/\/en.wikipedia.org\/wiki\/Lean_manufacturing\">Lean<\/a> and <a href=\"https:\/\/en.wikipedia.org\/wiki\/Just-in-time_manufacturing\">Just-in-time (JIT) manufacturing<\/a> was derived from the manufacturing industry by Toyota employee, <a href=\"https:\/\/en.wikipedia.org\/wiki\/Taiichi_Ohno\">Taiichi Ohno<\/a>, in the 1940s. <\/span><span style=\"font-weight: 400;\">Since then, Kanban has evolved into the visual scheduling system that many of us are familiar with today.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The Kanban method aims to reduce waste, continuously improve the process, and increase overall productivity. <\/span><span style=\"font-weight: 400;\">While there are no established rules of how Kanban works, there are <\/span><a href=\"https:\/\/en.wikipedia.org\/wiki\/Kanban_%28development%29#Principles\"><span style=\"font-weight: 400;\">six general practices<\/span><\/a><span style=\"font-weight: 400;\"> that should be applied to ensure optimized Kanban use. They are:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Visualization<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Limit work in progress<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Flow management<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Make policies explicit<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Use feedback loops<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Collaborative or experiment evolution<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">The visual nature of Kanban allows you to identify any<\/span><span style=\"font-weight: 400;\"> bottlenecks early on in the development process, enabling you to deliver a higher-quality product. <\/span><span style=\"font-weight: 400;\">It does this with the help of Kanban tools such as a Kanban board, Kanban cards, and sometimes even Kanban swimlanes.<\/span><\/p>\n<h3><strong>Kanban board<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">A <a href=\"https:\/\/zenkit.com\/blog\/how-kanban-boards-can-benefit-your-team\/\">Kanban board<\/a> is what is used to visualize the development process. A typical board features at least three columns, titled \u201cTo Do\u201d, \u201cDoing\u201d, and \u201cDone\u201d, which represent various stages of the process.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The board can either be made with a whiteboard, sticky notes, and markers, or you could use an online Kanban board, for which there are endless software options.<\/span><\/p>\n\n\n\n\n    \n<h3><strong>Kanban cards<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Kanban cards are what are used to depict a work item or task within the work process. It can also represent information such as the item\/task\u2019s status, cycle time, and deadline.<\/span><\/p>\n<h3><strong>Kanban swimlanes<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Not every Kanban board uses swimlanes. <a href=\"https:\/\/zenkit.com\/blog\/dive-into-better-task-management-with-kanban-swimlanes\/\">Swimlanes<\/a> are a visual element on the board that flows horizontally and are used for added organization. They categorize items or tasks and enable you to further distinguish them.<\/span><\/p>\n<hr \/>\n<h2 style=\"text-align: center;\"><strong>What Is Scrum?<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\"><a href=\"https:\/\/zenkit.com\/blog\/scrum-101-an-introduction-to-scrum-project-management\/\">Scrum<\/a> is an agile framework which focuses on developing, delivering, and sustaining complex products through collaboration, accountability, and iterative progress. It encourages collaborative decision-making and constructive feedback so a higher quality product can result.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Scrum is known for its defined team roles which are self-organizing and cross-functional, and designed to optimize flexibility, creativity, and productivity. They are:<\/span><\/p>\n<h3><strong>Product Owner<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">The first role is the Product Owner who is the product expert. They represent the stakeholders and the voice of the customer. They are solely responsible and accountable for managing the Product Backlog.<\/span><\/p>\n<h3><strong>Development Team<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">The Development Team is a group of professionals who deliver the product and create the Increment which is the working product functionality that is presented to the stakeholders and the of the sprint and could potentially be given to the customer. It is usually comprised of developers, programmers, or designers.<\/span><\/p>\n<h3><strong>Scrum Master<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">The Scrum Master facilitates a scrum project. Their core duty is to ensure the team successfully executes the project according to the principles and practices of scrum methodology, and that everyone on the team understands the core aim of scrum.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">They are responsible for making sure the development team is on track by providing necessary resources and blocking out any distractions that may hinder the development process.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-31022\" src=\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/scrum.gif\" alt=\"\" width=\"400\" height=\"225\" \/><\/p>\n<p><span style=\"font-weight: 400;\">A scrum workflow is made up of <\/span><i><span style=\"font-weight: 400;\">events<\/span><\/i><span style=\"font-weight: 400;\">. Each event is time-boxed, meaning they hold a maximum duration time that cannot be exceeded.<\/span><\/p>\n<hr \/>\n<h2 style=\"text-align: center;\"><strong>Scrum events<\/strong><\/h2>\n<h3><b>Sprint<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Sprints are iterative time boxes in which a goal is accomplished. The time frame doesn\u2019t surpass one calendar month and is consistent throughout the development process.<\/span><\/p>\n<h3><b>Spring planning<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">This event happens at the beginning of every sprint, and it\u2019s when the scrum team gets together to plan the upcoming sprint.<\/span><\/p>\n<h3><b>Daily Scrum<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A Daily Scrum is a 15-minute time-boxed meeting that happens at the same time, every day of the Sprint. The team discusses the previous day\u2019s achievements as well as the expectations for the next day.<\/span><\/p>\n<h3><b>Sprint review<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A review is an informal meeting held at the end of every Sprint. This is where the Scrum team present their Increment to the stakeholders and discusses feedback.<\/span><\/p>\n<h3><b>Sprint retrospective<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The Sprint Retrospective occurs after the Sprint Review and before the next Sprint Planning. It\u2019s a meeting where the team consider the steps and actions of the previous Sprint and set up improvements for the next Sprint.<\/span><\/p>\n<hr \/>\n<h2 style=\"text-align: center;\"><strong>Scrum Artifacts<\/strong><\/h2>\n<h3><b>Product backlog<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">This is where all the requirements needed for a viable product are listed in order of priority. It includes features, functions, requirements, enhancements, and fixes that authorize any changes to be made to the product in future releases. It\u2019s managed by the product owner.<\/span><\/p>\n<h3><b>Sprint backlog<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">This backlog is a list of the tasks and requirements that need to be achieved during the next Sprint. It is sometimes accompanied by a Scrum task board that is used to visualize the progress of the current Sprint.<\/span><\/p>\n<h3><strong>User story<\/strong><\/h3>\n<p>A user story is a tool used to describe a software feature from an end-user perspective. They help to imagine the type of people that would use the product. The common format that is used to initiate discussion and thought is:<\/p>\n<p><em>As a [role], I want [feature], because [reason].\u00a0<\/em><\/p>\n<h3><strong>Product increment<\/strong><\/h3>\n<p>The product increment is the result of all the product backlog items accomplished during a sprint. It&#8217;s the working product that is presented at the end of the sprint to stakeholders and potential customers.<\/p>\n<hr \/>\n<h2 style=\"text-align: center;\"><strong>Kanban vs Scrum<\/strong><\/h2>\n<p>Kanban and Scrum are work methods that aim to reduce waste. While they both adhere to the <a href=\"https:\/\/zenkit.com\/blog\/uncovering-the-agile-manifesto\/\">agile principles<\/a> of collaboration, continuous improvement, and flexibility, you can see that Kanban and Scrum are their own methodologies. Their main differences include:<\/p>\n\n<table id=\"tablepress-4\" class=\"tablepress tablepress-id-4\">\n<thead>\n<tr class=\"row-1\">\n\t<td class=\"column-1\"><\/td><th class=\"column-2\">Kanban<\/th><th class=\"column-3\">Scrum<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Roles<\/td><td class=\"column-2\">No fixed roles<\/td><td class=\"column-3\">Scrum master, Product, Owner, Development Team<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Cadence<\/td><td class=\"column-2\">Continuous flow<\/td><td class=\"column-3\">Fixed<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Changes<\/td><td class=\"column-2\">Not restricted, allowed to happen at any time<\/td><td class=\"column-3\">Not recommended during the sprint<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Key metrics<\/td><td class=\"column-2\">Cycle time<\/td><td class=\"column-3\">Velocity<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Delegation &amp; Prioritization<\/td><td class=\"column-2\">Pull system workflow where items\/tasks can only be \"pulled\" once previous has been completed<\/td><td class=\"column-3\">Pull system also used, but a whole bunch of items\/tasks are pulled for each iteration<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<p><span style=\"font-weight: 400;\">To dive deeper into the last point, a<\/span><span style=\"font-weight: 400;\">\u00a0key difference between Kanban and Scrum is the workflow and how items are managed. In Scrum, the work you do during a sprint is determined before the sprint starts. Then you do all the work during the sprint and after a few weeks (no longer than a month), your queue is empty.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In Kanban, only the size of the queues is limited, known as the WIP (work in progress) limit. This means there are no time restrictions as to when you are able to change the items in the queue, and there\u2019s no such thing as a \u201csprint end\u201d. This allows the work to continue flowing.<\/span><\/p>\n<p>Kanban is a tool that can be used to visualize project workflows to improve performance and quality. It doesn&#8217;t have a strict set structure in place, so it can be used with whatever process your team has already implemented. It can even be applied to <a href=\"https:\/\/zenkit.com\/blog\/how-to-be-productive-a-guide-to-personal-kanban\/\">personal productivity purposes<\/a>.<\/p>\n<p>Scrum, on the other hand, is iterative and incremental which means it&#8217;s ideal for teams who want a more enforced method of working. It&#8217;s also more suitable for teams with less than seven people.<\/p>\n<hr \/>\n<h2 style=\"text-align: center;\"><strong>Can Kanban and Scrum Be Used at the Same Time?<\/strong><\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-31032\" src=\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/answerisyes.gif\" alt=\"\" width=\"371\" height=\"289\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Kanban and Scrum can be used at the same time, most commonly by Scrum teams using Kanban. This method is known as \u201cScrumban\u201d.<\/span><\/p>\n<p><a href=\"https:\/\/en.wikipedia.org\/wiki\/Scrumban\"><span style=\"font-weight: 400;\">Scrumban<\/span><\/a><span style=\"font-weight: 400;\"> is a workflow management approach that takes the structure of Scrum and combines it with the flexibility and the visual representation of Kanban. It can be used for teams who want to apply Scrum project management as a way of working and adopt the Kanban method as a way to visualize and continuously improve.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This method can also be used as an avenue for teams seeking to transition from Scrum to Kanban. Software development teams who may find an immediate shift too extreme can turn to Scrumban as it offers an easier transition period for teams. An example of the kind of projects Scrumban could work well for is maintenance ones such as a help desk or support assistance.<\/span><\/p>\n<hr \/>\n<h2 style=\"text-align: center;\"><strong>Final Thoughts<\/strong><\/h2>\n<p>In conclusion to the Kanban vs Scrum discussion, it&#8217;s safe to say that they are different methodologies that appeal to different audiences. Where Scrum favours a more prescriptive process, Kanban leaves room for a more flexible workflow.<\/p>\n<p>They both comply with agile principles but also have their own individual values and practices. Which side of the fence you sit on when it comes to Kanban vs Scrum really comes down to the kind of project your team has and what type of product you wish to deliver.<\/p>\n<p>Have you used either Kanban or Scrum lately? If so, don&#8217;t forget to share your experiences in our comment section. We appreciate any feedback we get as it helps us to deliver the kind of content our readers wish to see!<\/p>\n<p>Cheers,<\/p>\n<p><strong>Dinnie and the Zenkit Team<\/strong><\/p>\n<hr \/>\n<p>Image Credits: <a href=\"https:\/\/unsplash.com\/@punttim\">Tim Gouw<\/a> via <a href=\"https:\/\/unsplash.com\/photos\/-gjHizUfFlM\">Unsplash<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Kanban and Scrum are two popular project management methodologies that are commonly used by teams looking for  [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":91119,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"yasr_overall_rating":0,"yasr_post_is_review":"","yasr_auto_insert_disabled":"","yasr_review_type":"","sub_heading":"Both adhere to agile principles, but they are different methodologies in their own right","time_to_read":0,"zenkit_blog_star_rating_disabled":false,"zenkit_blog_ad_has_sticky_bottom_bar":true,"zenkit_blog_ad_sticky_bottom_bar_text":"Whether Kanban or Scrum, manage your agile project in Zenkit!","zenkit_blog_ad_sticky_bottom_bar_link_text":"Create my free account","zenkit_blog_ad_sticky_bottom_bar_link_url":"https:\/\/app.zenkit.com\/register","zenkit_blog_ad_sticky_bottom_bar_custom_class":"","zenkit_blog_ad_has_sticky_top_bar":false,"zenkit_blog_ad_sticky_top_bar_text":"","zenkit_blog_ad_sticky_top_bar_link_text":"","zenkit_blog_ad_sticky_top_bar_link_url":"","zenkit_blog_ad_has_modal_popup":false,"zenkit_blog_ad_modal_popup_image":0,"zenkit_blog_ad_modal_popup_heading":"","zenkit_blog_ad_modal_popup_subheading":"","zenkit_blog_ad_modal_popup_link_text":"","zenkit_blog_ad_modal_popup_link_url":"","zenkit_blog_ad_modal_popup_close_text":"","zenkit_blog_ad_has_slidein":false,"zenkit_blog_ad_slidein_heading":"","zenkit_blog_ad_slidein_link_text":"","zenkit_blog_ad_slidein_link_url":"","zenkit_blog_ad_has_google_banner":false,"zenkit_blog_ad_google_banner_heading":"","zenkit_blog_ad_google_banner_subheading":"","zenkit_blog_ad_google_banner_button_text":"","zenkit_blog_ad_google_banner_button_link":"","zenkit_blog_ad_deactivate_global_ad":false,"super_override_sticky_bottom":false,"toc__deactivate":false,"toc__show_carets":false,"toc__expand_all":false,"zenkit_blog_override_update":"","de_activate_sitebar_cta_on_this_post":false,"zenkit_blog_sidebar_cta":"","super_override_sidebar_cta":false,"de_activate_end_cta_on_this_post":false,"zenkit_end_cta_type":"","zenkit_blog_exit_cta_type":"","footnotes":""},"categories":[16661,16663],"tags":[54,74,62,23,135],"class_list":["post-161030","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to","category-project-management","tag-agile","tag-agile-methodology","tag-kanban","tag-project-management","tag-scrum"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Kanban vs Scrum | Zenkit<\/title>\n<meta name=\"description\" content=\"This Kanban vs Scrum discussion looks\u00a0at the similarities and differences between the two popular agile methodologies, and\u00a0when to use them.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Kanban vs Scrum | Zenkit\" \/>\n<meta property=\"og:description\" content=\"This Kanban vs Scrum discussion looks\u00a0at the similarities and differences between the two popular agile methodologies, and\u00a0when to use them.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/\" \/>\n<meta property=\"og:site_name\" content=\"Zenkit\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/ZenkitHQ\" \/>\n<meta property=\"article:published_time\" content=\"2019-09-02T11:50:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-10-10T09:02:38+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"628\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Asmo\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@ZenkitHQ\" \/>\n<meta name=\"twitter:site\" content=\"@ZenkitHQ\" \/>\n<meta name=\"twitter:label1\" content=\"\u57f7\u7b46\u8005\" \/>\n\t<meta name=\"twitter:data1\" content=\"Asmo\" \/>\n\t<meta name=\"twitter:label2\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data2\" content=\"8\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/\"},\"author\":{\"name\":\"Asmo\",\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/#\\\/schema\\\/person\\\/a9ea9a4b8ef8fb42cbec748d3c3ee29b\"},\"headline\":\"Kanban vs Scrum\",\"datePublished\":\"2019-09-02T11:50:14+00:00\",\"dateModified\":\"2025-10-10T09:02:38+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/\"},\"wordCount\":1534,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/zenkit.com\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/Kanban-vs-Scrum.jpg\",\"keywords\":[\"Agile\",\"Agile Methodology\",\"Kanban\",\"Project Management\",\"Scrum\"],\"articleSection\":[\"How to\",\"Project Management\"],\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/\",\"url\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/\",\"name\":\"Kanban vs Scrum | Zenkit\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/zenkit.com\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/Kanban-vs-Scrum.jpg\",\"datePublished\":\"2019-09-02T11:50:14+00:00\",\"dateModified\":\"2025-10-10T09:02:38+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/#\\\/schema\\\/person\\\/a9ea9a4b8ef8fb42cbec748d3c3ee29b\"},\"description\":\"This Kanban vs Scrum discussion looks\u00a0at the similarities and differences between the two popular agile methodologies, and\u00a0when to use them.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/#primaryimage\",\"url\":\"https:\\\/\\\/zenkit.com\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/Kanban-vs-Scrum.jpg\",\"contentUrl\":\"https:\\\/\\\/zenkit.com\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/Kanban-vs-Scrum.jpg\",\"width\":1200,\"height\":628},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/kanban-vs-scrum\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Kanban vs Scrum\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/#website\",\"url\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/\",\"name\":\"Zenkit\",\"description\":\"Zenkit Tagline\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/#\\\/schema\\\/person\\\/a9ea9a4b8ef8fb42cbec748d3c3ee29b\",\"name\":\"Asmo\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0ccc9983fcb42443ee55d994b5c426040f1c1ad7e3cfb591d010134d2e246e45?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0ccc9983fcb42443ee55d994b5c426040f1c1ad7e3cfb591d010134d2e246e45?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0ccc9983fcb42443ee55d994b5c426040f1c1ad7e3cfb591d010134d2e246e45?s=96&d=mm&r=g\",\"caption\":\"Asmo\"},\"url\":\"https:\\\/\\\/zenkit.com\\\/ja\\\/blog\\\/author\\\/zenkit\\\/\"},false]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Kanban vs Scrum | Zenkit","description":"This Kanban vs Scrum discussion looks\u00a0at the similarities and differences between the two popular agile methodologies, and\u00a0when to use them.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/","og_locale":"ja_JP","og_type":"article","og_title":"Kanban vs Scrum | Zenkit","og_description":"This Kanban vs Scrum discussion looks\u00a0at the similarities and differences between the two popular agile methodologies, and\u00a0when to use them.","og_url":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/","og_site_name":"Zenkit","article_publisher":"https:\/\/www.facebook.com\/ZenkitHQ","article_published_time":"2019-09-02T11:50:14+00:00","article_modified_time":"2025-10-10T09:02:38+00:00","og_image":[{"width":1200,"height":628,"url":"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum.jpg","type":"image\/jpeg"}],"author":"Asmo","twitter_card":"summary_large_image","twitter_creator":"@ZenkitHQ","twitter_site":"@ZenkitHQ","twitter_misc":{"\u57f7\u7b46\u8005":"Asmo","\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"8\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/#article","isPartOf":{"@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/"},"author":{"name":"Asmo","@id":"https:\/\/zenkit.com\/ja\/#\/schema\/person\/a9ea9a4b8ef8fb42cbec748d3c3ee29b"},"headline":"Kanban vs Scrum","datePublished":"2019-09-02T11:50:14+00:00","dateModified":"2025-10-10T09:02:38+00:00","mainEntityOfPage":{"@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/"},"wordCount":1534,"commentCount":0,"image":{"@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/#primaryimage"},"thumbnailUrl":"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum.jpg","keywords":["Agile","Agile Methodology","Kanban","Project Management","Scrum"],"articleSection":["How to","Project Management"],"inLanguage":"ja","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/","url":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/","name":"Kanban vs Scrum | Zenkit","isPartOf":{"@id":"https:\/\/zenkit.com\/ja\/#website"},"primaryImageOfPage":{"@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/#primaryimage"},"image":{"@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/#primaryimage"},"thumbnailUrl":"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum.jpg","datePublished":"2019-09-02T11:50:14+00:00","dateModified":"2025-10-10T09:02:38+00:00","author":{"@id":"https:\/\/zenkit.com\/ja\/#\/schema\/person\/a9ea9a4b8ef8fb42cbec748d3c3ee29b"},"description":"This Kanban vs Scrum discussion looks\u00a0at the similarities and differences between the two popular agile methodologies, and\u00a0when to use them.","breadcrumb":{"@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/"]}]},{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/#primaryimage","url":"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum.jpg","contentUrl":"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/09\/Kanban-vs-Scrum.jpg","width":1200,"height":628},{"@type":"BreadcrumbList","@id":"https:\/\/zenkit.com\/ja\/blog\/kanban-vs-scrum\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/zenkit.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Kanban vs Scrum"}]},{"@type":"WebSite","@id":"https:\/\/zenkit.com\/ja\/#website","url":"https:\/\/zenkit.com\/ja\/","name":"Zenkit","description":"Zenkit Tagline","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/zenkit.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Person","@id":"https:\/\/zenkit.com\/ja\/#\/schema\/person\/a9ea9a4b8ef8fb42cbec748d3c3ee29b","name":"Asmo","image":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/secure.gravatar.com\/avatar\/0ccc9983fcb42443ee55d994b5c426040f1c1ad7e3cfb591d010134d2e246e45?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/0ccc9983fcb42443ee55d994b5c426040f1c1ad7e3cfb591d010134d2e246e45?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0ccc9983fcb42443ee55d994b5c426040f1c1ad7e3cfb591d010134d2e246e45?s=96&d=mm&r=g","caption":"Asmo"},"url":"https:\/\/zenkit.com\/ja\/blog\/author\/zenkit\/"},false]}},"yasr_visitor_votes":{"stars_attributes":{"read_only":false,"span_bottom":false},"number_of_votes":0,"sum_votes":0},"_links":{"self":[{"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/posts\/161030","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/comments?post=161030"}],"version-history":[{"count":2,"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/posts\/161030\/revisions"}],"predecessor-version":[{"id":167482,"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/posts\/161030\/revisions\/167482"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/media\/91119"}],"wp:attachment":[{"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/media?parent=161030"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/categories?post=161030"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zenkit.com\/ja\/wp-json\/wp\/v2\/tags?post=161030"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}