{"id":90,"date":"2013-02-11T18:27:51","date_gmt":"2013-02-11T18:27:51","guid":{"rendered":"http:\/\/agilerasmus.com\/wordpress\/?p=90"},"modified":"2016-12-18T18:29:28","modified_gmt":"2016-12-18T18:29:28","slug":"toyotas-six-rules","status":"publish","type":"post","link":"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/","title":{"rendered":"Toyota’s six rules"},"content":{"rendered":"

In order to have a well-functioning Kanban setup one must agree on a basic set of rules of usage. The mother of all Kanban implementors is Toyota who, guided by the father of Kanban – Taiichi Ohno, outlined 6 basic rules that should be strictly followed.<\/p>\n

    \n
  1. Do not send defective products to the subsequent process<\/li>\n
  2. The subsequent process withdraws only what is needed<\/li>\n
  3. Produce only the exact quantity withdrawn by the subsequent process<\/li>\n
  4. Level the production<\/li>\n
  5. Kanban is a means of fine tuning<\/li>\n
  6. Stabilize and rationalize the process<\/li>\n<\/ol>\n

    These rules were defined for use at Toyota in 1953, so they may not entirely meet the requirements in todays software development. However, I still find it valuable to start up new teams using these rules for their Kanban setup.<\/p>\n

    When coaching new teams I interpret the 6 rules into the following software development statements:<\/p>\n

    Do not send defective products to the subsequent process<\/strong><\/p>\n

    Always conform to the defined policies for each phase. Define efficient and sufficient policies to make sure quality is kept at appropriate level. Example: If the analysis phase has a policy that all design decisions must be reviewed by lead architect and business representatives – then this must be followed.<\/p><\/blockquote>\n

    The subsequent process withdraws only what is needed<\/strong><\/p>\n

    In production environments such as Toyota, this is pretty straight forward – only process ordered items that is needed further down the line. In software development this is analogy is a bit off and should be rephrased. My interpretation is two-fold: 1) only work on items that are prioritized and ordered by the customer and 2) all ways work on tasks from right to left on the board with respect to policies and limits, i.e. favor getting things done over starting new tasks.<\/p><\/blockquote>\n

    Level the production<\/strong><\/p>\n

    Working at the assembly line all units must produce exactly the amount of items needed by the weakest contributor, i.e. if machine A is able to spit out 1000 items per hour but machine B is only able to process 500 items per hour – machine A should be limited to 500 to minimize waste. The flow of tasks on the Kanban board should be meassured and bottlenecks should be identified to level the production. Resolving a bottleneck can be done by scaling up the problem ressource or limiting the number of tasks for review to the meassured capacity.<\/p><\/blockquote>\n

    Kanban is a means of fine tuning<\/strong><\/p>\n

    Kanban is meant as a non-intrusive framework that build on top of whatever defined\/undefined process a team is following. Once Kanban has been initialized in a team meassurements and retrospective meetings should focus on fine tuning the flow of tasks on the Kanban board. Using the WIP-limits, policies and visual overview of tasks in the team to escalate pain points or reduce the number of active tasks in order to turn the team into a lean and mean task solving team.<\/p><\/blockquote>\n

    Stabilize and rationalize the process<\/strong><\/p>\n

    One of the objectives I hear from managers when assisting them in introducing Kanban, is to have a comon shared – stable – process for the team to follow. I aid the team to identify \u201call\u201d their processes using process flow modelling and expand to one overall process. Process deviations for different types of tasks is handled within policies, i.e. each state on the Kanban board has policies covering \u201call\u201d process deviations. This make a solid foundation for a sane and rational process within the team. A periodical retrospective meeting where the Kanban board is reviewed and updated, the team will have a rational process where each state that a task follows is within reason.<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

    In order to have a well-functioning Kanban setup one must agree on a basic set of rules of usage. The mother of all Kanban implementors is Toyota who, guided by the father of Kanban –…<\/p>\n","protected":false},"author":1,"featured_media":91,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true},"categories":[3],"tags":[20,19],"yoast_head":"\nToyota's six rules - @agilerasmus<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Toyota's six rules - @agilerasmus\" \/>\n<meta property=\"og:description\" content=\"In order to have a well-functioning Kanban setup one must agree on a basic set of rules of usage. The mother of all Kanban implementors is Toyota who, guided by the father of Kanban –...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/\" \/>\n<meta property=\"og:site_name\" content=\"@agilerasmus\" \/>\n<meta property=\"article:published_time\" content=\"2013-02-11T18:27:51+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2016-12-18T18:29:28+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/i0.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/toyta.jpg?fit=500%2C375&ssl=1\" \/>\n\t<meta property=\"og:image:width\" content=\"500\" \/>\n\t<meta property=\"og:image:height\" content=\"375\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/#website\",\"url\":\"https:\/\/agilerasmus.com\/wordpress\/\",\"name\":\"@agilerasmus\",\"description\":\"agile coach, trainer and scrum master\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/agilerasmus.com\/wordpress\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/i0.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/toyta.jpg?fit=500%2C375&ssl=1\",\"contentUrl\":\"https:\/\/i0.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/toyta.jpg?fit=500%2C375&ssl=1\",\"width\":500,\"height\":375},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#webpage\",\"url\":\"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/\",\"name\":\"Toyota's six rules - @agilerasmus\",\"isPartOf\":{\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#primaryimage\"},\"datePublished\":\"2013-02-11T18:27:51+00:00\",\"dateModified\":\"2016-12-18T18:29:28+00:00\",\"author\":{\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/#\/schema\/person\/cc0de41731dfcf8697fd64dadadcf096\"},\"breadcrumb\":{\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/agilerasmus.com\/wordpress\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Toyota’s six rules\"}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/#\/schema\/person\/cc0de41731dfcf8697fd64dadadcf096\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/agilerasmus.com\/wordpress\/#personlogo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/024753e28bdb374a97740a4d5572755e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/024753e28bdb374a97740a4d5572755e?s=96&d=mm&r=g\",\"caption\":\"admin\"},\"url\":\"https:\/\/agilerasmus.com\/wordpress\/author\/admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Toyota's six rules - @agilerasmus","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:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/","og_locale":"en_GB","og_type":"article","og_title":"Toyota's six rules - @agilerasmus","og_description":"In order to have a well-functioning Kanban setup one must agree on a basic set of rules of usage. The mother of all Kanban implementors is Toyota who, guided by the father of Kanban –...","og_url":"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/","og_site_name":"@agilerasmus","article_published_time":"2013-02-11T18:27:51+00:00","article_modified_time":"2016-12-18T18:29:28+00:00","og_image":[{"width":500,"height":375,"url":"https:\/\/i0.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/toyta.jpg?fit=500%2C375&ssl=1","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Written by":"admin","Estimated reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebSite","@id":"https:\/\/agilerasmus.com\/wordpress\/#website","url":"https:\/\/agilerasmus.com\/wordpress\/","name":"@agilerasmus","description":"agile coach, trainer and scrum master","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/agilerasmus.com\/wordpress\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-GB"},{"@type":"ImageObject","@id":"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#primaryimage","inLanguage":"en-GB","url":"https:\/\/i0.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/toyta.jpg?fit=500%2C375&ssl=1","contentUrl":"https:\/\/i0.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/toyta.jpg?fit=500%2C375&ssl=1","width":500,"height":375},{"@type":"WebPage","@id":"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#webpage","url":"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/","name":"Toyota's six rules - @agilerasmus","isPartOf":{"@id":"https:\/\/agilerasmus.com\/wordpress\/#website"},"primaryImageOfPage":{"@id":"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#primaryimage"},"datePublished":"2013-02-11T18:27:51+00:00","dateModified":"2016-12-18T18:29:28+00:00","author":{"@id":"https:\/\/agilerasmus.com\/wordpress\/#\/schema\/person\/cc0de41731dfcf8697fd64dadadcf096"},"breadcrumb":{"@id":"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/agilerasmus.com\/wordpress\/toyotas-six-rules\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/agilerasmus.com\/wordpress\/"},{"@type":"ListItem","position":2,"name":"Toyota’s six rules"}]},{"@type":"Person","@id":"https:\/\/agilerasmus.com\/wordpress\/#\/schema\/person\/cc0de41731dfcf8697fd64dadadcf096","name":"admin","image":{"@type":"ImageObject","@id":"https:\/\/agilerasmus.com\/wordpress\/#personlogo","inLanguage":"en-GB","url":"https:\/\/secure.gravatar.com\/avatar\/024753e28bdb374a97740a4d5572755e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/024753e28bdb374a97740a4d5572755e?s=96&d=mm&r=g","caption":"admin"},"url":"https:\/\/agilerasmus.com\/wordpress\/author\/admin\/"}]}},"jetpack_featured_media_url":"https:\/\/i0.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/toyta.jpg?fit=500%2C375&ssl=1","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8dzln-1s","jetpack-related-posts":[{"id":369,"url":"https:\/\/agilerasmus.com\/wordpress\/history-of-kanban\/","url_meta":{"origin":90,"position":0},"title":"History of Kanban","date":"December 19, 2016","format":false,"excerpt":"Kanban, as we know it in Software Development and LEAN terminology, originates from the Toyota Production System and was developed by Taiichi Ohno to improve and maintain a high level of production. The word Kanban originates from Japanese where \u201cKan\u201d means \u201cvisual\u201d and \u201cban\u201d means \u201csignal\u201d. 1700 The word \u201cKanban\u770b\u677f\u201d\u2026","rel":"","context":"In "English"","img":{"alt_text":"","src":"https:\/\/i1.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/kanban.png?fit=756%2C338&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":969,"url":"https:\/\/agilerasmus.com\/wordpress\/transparent-operation-and-service-management\/","url_meta":{"origin":90,"position":1},"title":"Transparent operation and service management","date":"January 8, 2021","format":false,"excerpt":"Kanban has proven to be a valuable tool for introducing and performing operations management in self-organizing service, development and maintenance teams throughout many organizations The history of operations management started over 7,000 years ago. In 5,000 B.C. the priests of Sumer (today southern part of Iraq) invented a system for\u2026","rel":"","context":"In "English"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2021\/01\/electrician-2755683_960_720.jpg?fit=960%2C638&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":145,"url":"https:\/\/agilerasmus.com\/wordpress\/jeg-koerer-sav\/","url_meta":{"origin":90,"position":2},"title":"“Jeg k\u00f8rer sav”","date":"November 28, 2014","format":false,"excerpt":"Kanban er en gammel teknik der stammer fra Japan. Ordet betyder noget i retning af \"skilt\" eller \"signal\". I 1700-tallet brugte japanske producenter Kanban til at markedsf\u00f8re sig, i det de placerede sm\u00e5 logoer udsk\u00e5ret i tr\u00e6 p\u00e5 deres varer, s\u00e5 folk kunne se hvilken smed eller snedker der havde\u2026","rel":"","context":"In "Dansk"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":96,"url":"https:\/\/agilerasmus.com\/wordpress\/3-step-adoption-pattern-for-kanban\/","url_meta":{"origin":90,"position":3},"title":"3-step adoption pattern for Kanban","date":"October 12, 2012","format":false,"excerpt":"Starting up a new team is alway a fun and exciting challenge. During my time as agile coach I have found a nice pattern that most team follows which breaks down to the following phases: 1. Please give me the book and we\u2019ll get started The authors of Kanban books\u2026","rel":"","context":"In "English"","img":{"alt_text":"","src":"https:\/\/i2.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/lys.jpg?fit=406%2C750&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":363,"url":"https:\/\/agilerasmus.com\/wordpress\/kanban-from-different-perspectives\/","url_meta":{"origin":90,"position":4},"title":"Kanban from different perspectives","date":"December 26, 2016","format":false,"excerpt":"To put it short \u2013 Kanban is a way of visualizing pending work, work in progress, prioritization and status of work tasks. \u00a0The process for each work task is normally illustrated by having vertical separators on the Kanban board, each representing state. Priority of each work task is illustrated by\u2026","rel":"","context":"In "English"","img":{"alt_text":"","src":"https:\/\/i1.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/road-sign-63983_1920.jpg?fit=1200%2C900&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":93,"url":"https:\/\/agilerasmus.com\/wordpress\/key-motivators-for-failing-at-kanban\/","url_meta":{"origin":90,"position":5},"title":"Key motivators for failing at kanban","date":"February 6, 2013","format":false,"excerpt":"Working with a wide range of teams adopting Kanban, I\u2019ve looked into what are the common pitfalls or caveats for a coach when starting up. The information I present here is mainly gathered from system maintenance teams; i.e. teams that are focused on day-to-day handling of system failures, feature requests\u2026","rel":"","context":"In "English"","img":{"alt_text":"","src":"https:\/\/i2.wp.com\/agilerasmus.com\/wordpress\/wp-content\/uploads\/2016\/12\/fail.jpg?fit=500%2C302&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/posts\/90"}],"collection":[{"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/comments?post=90"}],"version-history":[{"count":1,"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/posts\/90\/revisions"}],"predecessor-version":[{"id":92,"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/posts\/90\/revisions\/92"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/media\/91"}],"wp:attachment":[{"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/media?parent=90"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/categories?post=90"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilerasmus.com\/wordpress\/wp-json\/wp\/v2\/tags?post=90"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}