{"id":12088,"date":"2014-06-17T08:40:05","date_gmt":"2014-06-17T13:40:05","guid":{"rendered":"https:\/\/blog.planview.com\/?p=12088"},"modified":"2020-02-20T08:46:33","modified_gmt":"2020-02-20T14:46:33","slug":"how-kanban-enables-continuous-delivery-leankits-perspective","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/","title":{"rendered":"How Kanban Enables Continuous Delivery: Planview AgilePlace\u2019s Perspective"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-12093\" src=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg\" alt=\"\" width=\"876\" height=\"493\" srcset=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg 800w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective-300x169.jpg 300w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective-768x432.jpg 768w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective-750x422.jpg 750w\" sizes=\"auto, (max-width: 876px) 100vw, 876px\" \/><\/p>\n<p>Kanban and continuous delivery are technical practices that go hand in hand.<\/p>\n<p>The goal of continuous delivery is to rapidly, reliably and repeatedly deliver new features and bug fixes at low risk and with minimal overhead. The goal of\u00a0<a title=\"What is Kanban?\" href=\"https:\/\/www.planview.com\/resources\/articles\/what-is-kanban\/\" target=\"_blank\" rel=\"noopener noreferrer\" data-ol-has-click-handler=\"\">Kanban<\/a>\u00a0is to optimize the flow of work through incremental change. Both approaches share the common objective of\u00a0<b>delivering value to the customer faster<\/b>.<\/p>\n<p>Kanban and continuous delivery also complement each other with their\u00a0<b>shared objective of process improvement<\/b>. Continuous delivery, which can be delayed by manual effort and human error, often uses automation to make processes more efficient.<\/p>\n<p>Ideally, automation will make a good process better; but, automating a bad process can have disastrous effects. Kanban steps in by helping you mirror your process, allowing you to instantly see where work flows and where work gets stuck. This, in turn, can show you which steps to automate and which steps to improve before they\u2019re automated.<\/p>\n<p>The combination of Kanban and continuous delivery causes a fundamental shift in how work is planned and managed. Instead of batching features in big releases, continuous delivery favors frequent, small releases. Kanban, as a\u00a0<b>continuous flow methodology,\u00a0<\/b>associates value with finishing. As a result, software development teams are encouraged to develop, test and release new features and fixes in a continuous manner, completing work in progress before starting new work.<\/p>\n<p>Here at Planview AgilePlace, we\u2019ve been practicing Kanban and continuous delivery from the get-go. Five years in \u2014 while we\u2019re not perfect \u2014 we thought it might be helpful to share what we\u2019ve learned along the way. We interviewed members of our software development team to understand how Kanban enables the practical implementation of continuous delivery.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_80 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#Kanban_and_Continuous_Delivery_CTO_View\" >Kanban and Continuous Delivery: CTO View<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#Kanban_and_Continuous_Delivery_Dev_Team_View\" >Kanban and Continuous Delivery: Dev Team View<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#Tips_for_Practicing_Kanban_and_Continuous_Delivery\" >Tips for Practicing Kanban and Continuous Delivery<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Kanban_and_Continuous_Delivery_CTO_View\"><\/span>Kanban and Continuous Delivery: CTO View<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3>Why did Planview AgilePlace decide to follow a continuous delivery approach?<\/h3>\n<p>Our top priority is delivering value to customers as quickly as possible, so it feels counter-intuitive to batch up new features and bug fixes and wait for the next big release. Why keep our customers waiting?<\/p>\n<p>Also, given that Kanban is in our DNA at Planview AgilePlace, we\u2019re always looking for ways to improve. One of my primary goals as CTO is to reduce the transaction cost \u2014 or overhead \u2014 associated with delivering new features.\u00a0Practicing Kanban and continuous delivery together supports that goal, constantly driving us to evaluate and improve our processes, tools, methods, architecture and culture to increase operational effectiveness.<\/p>\n<div><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-12089\" src=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Economic-Batch-Size-Reinertsen-1024x853.jpg\" alt=\"\" width=\"1024\" height=\"853\" srcset=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Economic-Batch-Size-Reinertsen-1024x853.jpg 1024w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Economic-Batch-Size-Reinertsen-1024x853-300x250.jpg 300w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Economic-Batch-Size-Reinertsen-1024x853-768x640.jpg 768w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Economic-Batch-Size-Reinertsen-1024x853-750x625.jpg 750w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/div>\n<div>\n<h3>On a business level, how does continuous delivery benefit Planview AgilePlace?<\/h3>\n<p>The main benefit is the reduced time it takes to build new features and deliver them to customers. As a result, our feedback loops are much faster, mitigating the risk of investing too much time in work that doesn\u2019t provide value. We\u2019re able to quickly adjust direction based on customer feedback.<\/p>\n<p>From a technical standpoint, delivering product updates more frequently also reduces the risk of something going wrong, since there is less surface area being deployed each time. And, if there are any issues, we can resolve them quickly with minimal inconvenience to our users. Overall, this results in more reliable and higher quality software.<\/p>\n<h3>How has continuous delivery changed the way Planview AgilePlace works as an organization?<\/h3>\n<p>It changes the outlook of the entire organization \u2014 especially for a product-focused company. At Planview AgilePlace, we have anywhere between two and 30 deployments per week. This pace impacts not only development, but also how we coordinate our marketing, sales, operations and delivery activities. Continuous delivery requires tight cross-team collaboration to stay informed and adjust accordingly.<\/p>\n<p>To this end, it helps that our entire organization practices Kanban. Everyone in the organization has visibility into what\u2019s being worked on and what\u2019s coming next at any given time. This ensures that we stay aligned and can adapt quickly to changing priorities.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-12090\" src=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/feedback-loops.jpg\" alt=\"\" width=\"800\" height=\"466\" srcset=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/feedback-loops.jpg 800w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/feedback-loops-300x175.jpg 300w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/feedback-loops-768x447.jpg 768w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/feedback-loops-750x437.jpg 750w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Kanban_and_Continuous_Delivery_Dev_Team_View\"><\/span>Kanban and Continuous Delivery: Dev Team View<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3>From a developer\u2019s viewpoint, what are the benefits of continuous delivery?<\/h3>\n<p>Continuous delivery makes us a lot more nimble as a team. We\u2019ve all had prior work experiences where we\u2019ve been on a rigid release schedule. The general consensus of the team is that continuous delivery is a much smoother \u2014 and less stressful \u2014 way of working.<\/p>\n<p>It\u2019s also easier to troubleshoot problems. There can be a lot of trepidation associated with a big release as there\u2019s so much more that can go wrong. When fewer changes are made to the code base, we can quickly find the root cause of issues, and if need be, rollback with minimal disruption to customers.<\/p>\n<p>We also don\u2019t have to relearn our process every time we deploy. If you\u2019re only releasing a few times a year, it\u2019s more likely that things will go wrong. For us, since we\u2019re releasing almost daily, deployments go a lot more smoothly.<\/p>\n<h3>What\u2019s the impact on team morale?<\/h3>\n<p>It\u2019s easy for teams to lose momentum when they spend time building features that no one sees for another six months. With continuous delivery, it\u2019s exciting to build something and immediately receive customer feedback. It\u2019s more rewarding and keeps us engaged with our customers. It\u2019s similar to the gratification we get from moving a card across a Kanban board. Moving things to \u201cdone\u201d gives everyone a sense of accomplishment.<\/p>\n<h3>How does continuous delivery work at Planview AgilePlace?<\/h3>\n<p>For us, continuous delivery starts with how we break down the work. We\u2019ve become adept at breaking it into small, releasable chunks that we can move through our process relatively quickly.<\/p>\n<p>Upcoming work and bug fixes are captured and prioritized on our team\u2019s Kanban board. Once the build and test work have been done, we release the code in our staged environment called \u201cdogfood.\u201d This enables us to test with our internal Planview AgilePlace users in a real-world scenario and address any bugs before we deploy. Once the new code is in production, we constantly monitor feedback so we can quickly respond to any issues.<\/p>\n<p>We also distinguish between continuous delivery and continuous deployment. At Planview AgilePlace, we have the flexibility to release code to production and control when it\u2019s accessible to users. We achieve this by building feature enablement capabilities into our core architecture so we can easily turn features on and off.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-12091\" src=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Screen-Shot-2014-06-17-at-12.08.54-PM.png\" alt=\"\" width=\"2278\" height=\"742\" srcset=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Screen-Shot-2014-06-17-at-12.08.54-PM.png 2278w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Screen-Shot-2014-06-17-at-12.08.54-PM-300x98.png 300w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Screen-Shot-2014-06-17-at-12.08.54-PM-768x250.png 768w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Screen-Shot-2014-06-17-at-12.08.54-PM-1024x334.png 1024w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Screen-Shot-2014-06-17-at-12.08.54-PM-750x244.png 750w\" sizes=\"auto, (max-width: 2278px) 100vw, 2278px\" \/><\/p>\n<h3>How much of Planview AgilePlace\u2019s software delivery process is automated?<\/h3>\n<p>We\u2019ve automated some aspects of our process \u2014 such as unit testing and deployment scripts \u2014 but for the most part, we\u2019re taking baby steps. We\u2019re always looking to automate parts of the process to make it more efficient; but, to keep our flow consistent, we move toward more automation in small, incremental steps.<\/p>\n<p>To us, it\u2019s more important to get the underlying process right before trying to automate everything. If the cost and effort required to automate a part of our process doesn\u2019t outweigh the transaction overhead associated with it, then we don\u2019t do it.<\/p>\n<h3>What\u2019s the biggest challenge associated with continuous delivery?<\/h3>\n<p>The main challenge is the pace of work. Things move quickly, which requires everyone to be in sync. If just one of us falls out of alignment, it can cause a lot of friction and slow the process down.<\/p>\n<h3>How does Kanban enable continuous delivery?<\/h3>\n<p>The ability to visualize all of our work on a\u00a0<a title=\"10 Kanban Board Examples\" href=https:\/\/www.planview.com\/resources\/guide\/kanban-project-management-virtual-teams\/kanban-board-examples\/ target=\"_blank\" rel=\"noopener noreferrer\" data-ol-has-click-handler=\"\">Kanban board<\/a>\u00a0and know the latest status at any given time makes a huge difference. It provides us with a signaling mechanism that lets us know what\u2019s coming so we can keep the work moving.<\/p>\n<p>Kanban also helps us create a steadier workflow, since we can absorb unplanned work (such as bug fixes) more easily. That, in turn, helps us avoid bottlenecks. We\u2019re constantly able to re-prioritize work and focus on finishing the work we\u2019ve started rather than switch between tasks.<\/p>\n<p>Kanban is a methodology that promotes incremental improvement, which is essential to success with continuous delivery. It takes time to figure out the best way to get things done as a team.<\/p>\n<h3>Can you provide an example of process improvement?<\/h3>\n<p>Our old process allowed developers to begin something new once they completed the build work and passed it off to QA for testing. If an issue was found in testing, then the work had to go back into the build queue to be resolved. Sometimes the work would be passed back and forth a number of times before it was finally production-ready.<\/p>\n<p>When we looked at our metrics, we saw that the back-and-forth work slowed down our process and caused inefficiencies. As a result, we changed our process. Now, the Director of QA has to release a developer from what he or she is currently working on before new work can be pulled. The result is a much faster resolution of issues. There\u2019s no wait time, so work is delivered more quickly, overall \u2014 even if it introduces some some slack time for the developers.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-12092\" src=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Analytics.png\" alt=\"\" width=\"792\" height=\"403\" srcset=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Analytics.png 792w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Analytics-300x153.png 300w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Analytics-768x391.png 768w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Analytics-750x382.png 750w\" sizes=\"auto, (max-width: 792px) 100vw, 792px\" \/><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Tips_for_Practicing_Kanban_and_Continuous_Delivery\"><\/span>Tips for Practicing Kanban and Continuous Delivery<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Based on our experience, we\u2019ve discovered that it\u2019s easier to practice Kanban and continuous delivery when you remember the following:<\/p>\n<ul>\n<li><b>Focus on your process first.<\/b>\u00a0Don\u2019t try to implement a new process and automate everything all at once. Take baby steps. Incremental improvement is the key to making continuous delivery work.<\/li>\n<li><b>Do what makes sense.<\/b>\u00a0Begin by addressing the parts of your process that incur the highest transaction cost. If the effort required to automate or change a part of your process doesn\u2019t outweigh the transaction cost associated with it, then don\u2019t do it. Constantly re-evaluate your decisions and make incremental improvements as you go.<\/li>\n<li><b>Make your work visible.\u00a0<\/b>It\u2019s easier to work effectively as a team when everyone knows what\u2019s going on. If nothing else, putting all of your work on a Kanban board helps you wrap your arms around the work that needs to be done. You can\u2019t leave it to chance with continuous delivery. Things just move too fast.<\/li>\n<li><strong>Make sure all stakeholders are involved.<\/strong>\u00a0With a continuous delivery model, the overall value stream typically includes stakeholders that are both upstream and downstream of the development process. It\u2019s important to make sure that the impact on the entire organizational system is considered and communicated. Otherwise, you\u2019ll find that you\u2019ve implemented only localized efficiencies, which may cause bottlenecks further downstream.<\/li>\n<\/ul>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Kanban and continuous delivery are technical practices that go hand in hand. The goal of continuous delivery is to rapidly, reliably and repeatedly deliver new features and bug fixes at low risk and with minimal overhead. The goal of\u00a0Kanban\u00a0is to optimize the flow of work through incremental change. Both approaches share the common objective of\u00a0delivering&#8230;<\/p>\n","protected":false},"author":47,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_editorskit_title_hidden":false,"_editorskit_reading_time":0,"_editorskit_is_block_options_detached":false,"_editorskit_block_options_position":"{}","footnotes":""},"categories":[38],"tags":[511],"class_list":["post-12088","post","type-post","status-publish","format-standard","hentry","category-work-collaboration","tag-leankit"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.8 (Yoast SEO v26.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>How Kanban Enables Continuous Delivery - Blog | Planview<\/title>\n<meta name=\"description\" content=\"The goal of continuous delivery is to rapidly, reliably and repeatedly deliver new features and bug fixes at low risk and with minimal overhead.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How Kanban Enables Continuous Delivery: Planview AgilePlace\u2019s Perspective\" \/>\n<meta property=\"og:description\" content=\"The goal of continuous delivery is to rapidly, reliably and repeatedly deliver new features and bug fixes at low risk and with minimal overhead.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/\" \/>\n<meta property=\"og:site_name\" content=\"Planview Blog\" \/>\n<meta property=\"article:publisher\" content=\"http:\/\/www.facebook.com\/pages\/Planview-Inc\/89422974772\" \/>\n<meta property=\"article:published_time\" content=\"2014-06-17T13:40:05+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-02-20T14:46:33+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg\" \/>\n<meta name=\"author\" content=\"Planview Blog\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Planview\" \/>\n<meta name=\"twitter:site\" content=\"@Planview\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Planview Blog\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/\"},\"author\":{\"name\":\"Planview Blog\",\"@id\":\"https:\/\/blog.planview.com\/#\/schema\/person\/fd58aa7028c738371555a4f6fe4032f4\"},\"headline\":\"How Kanban Enables Continuous Delivery: Planview AgilePlace\u2019s Perspective\",\"datePublished\":\"2014-06-17T13:40:05+00:00\",\"dateModified\":\"2020-02-20T14:46:33+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/\"},\"wordCount\":1740,\"publisher\":{\"@id\":\"https:\/\/blog.planview.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg\",\"keywords\":[\"LeanKit\"],\"articleSection\":[\"Work Management for Teams\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/\",\"url\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/\",\"name\":\"How Kanban Enables Continuous Delivery - Blog | Planview\",\"isPartOf\":{\"@id\":\"https:\/\/blog.planview.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg\",\"datePublished\":\"2014-06-17T13:40:05+00:00\",\"dateModified\":\"2020-02-20T14:46:33+00:00\",\"description\":\"The goal of continuous delivery is to rapidly, reliably and repeatedly deliver new features and bug fixes at low risk and with minimal overhead.\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#primaryimage\",\"url\":\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg\",\"contentUrl\":\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg\",\"width\":800,\"height\":450},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.planview.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How Kanban Enables Continuous Delivery: LeanKit\u2019s Perspective\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.planview.com\/#website\",\"url\":\"https:\/\/blog.planview.com\/\",\"name\":\"Planview Blog\",\"description\":\"Leading the conversation on digital connected work\",\"publisher\":{\"@id\":\"https:\/\/blog.planview.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.planview.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.planview.com\/#organization\",\"name\":\"Planview\",\"url\":\"https:\/\/blog.planview.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.planview.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.planview.com\/wp-content\/uploads\/2015\/06\/planview-logo-black.png\",\"contentUrl\":\"https:\/\/blog.planview.com\/wp-content\/uploads\/2015\/06\/planview-logo-black.png\",\"width\":280,\"height\":66,\"caption\":\"Planview\"},\"image\":{\"@id\":\"https:\/\/blog.planview.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"http:\/\/www.facebook.com\/pages\/Planview-Inc\/89422974772\",\"https:\/\/x.com\/Planview\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.planview.com\/#\/schema\/person\/fd58aa7028c738371555a4f6fe4032f4\",\"name\":\"Planview Blog\",\"url\":\"https:\/\/blog.planview.com\/author\/planviewblog\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"How Kanban Enables Continuous Delivery - Blog | Planview","description":"The goal of continuous delivery is to rapidly, reliably and repeatedly deliver new features and bug fixes at low risk and with minimal overhead.","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:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/","og_locale":"en_US","og_type":"article","og_title":"How Kanban Enables Continuous Delivery: Planview AgilePlace\u2019s Perspective","og_description":"The goal of continuous delivery is to rapidly, reliably and repeatedly deliver new features and bug fixes at low risk and with minimal overhead.","og_url":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/","og_site_name":"Planview Blog","article_publisher":"http:\/\/www.facebook.com\/pages\/Planview-Inc\/89422974772","article_published_time":"2014-06-17T13:40:05+00:00","article_modified_time":"2020-02-20T14:46:33+00:00","og_image":[{"url":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg","type":"","width":"","height":""}],"author":"Planview Blog","twitter_card":"summary_large_image","twitter_creator":"@Planview","twitter_site":"@Planview","twitter_misc":{"Written by":"Planview Blog","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#article","isPartOf":{"@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/"},"author":{"name":"Planview Blog","@id":"https:\/\/blog.planview.com\/#\/schema\/person\/fd58aa7028c738371555a4f6fe4032f4"},"headline":"How Kanban Enables Continuous Delivery: Planview AgilePlace\u2019s Perspective","datePublished":"2014-06-17T13:40:05+00:00","dateModified":"2020-02-20T14:46:33+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/"},"wordCount":1740,"publisher":{"@id":"https:\/\/blog.planview.com\/#organization"},"image":{"@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg","keywords":["LeanKit"],"articleSection":["Work Management for Teams"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/","url":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/","name":"How Kanban Enables Continuous Delivery - Blog | Planview","isPartOf":{"@id":"https:\/\/blog.planview.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#primaryimage"},"image":{"@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg","datePublished":"2014-06-17T13:40:05+00:00","dateModified":"2020-02-20T14:46:33+00:00","description":"The goal of continuous delivery is to rapidly, reliably and repeatedly deliver new features and bug fixes at low risk and with minimal overhead.","breadcrumb":{"@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#primaryimage","url":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg","contentUrl":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Kanban-and-continuous-delivery-leankit-perspective.jpg","width":800,"height":450},{"@type":"BreadcrumbList","@id":"https:\/\/blog.planview.com\/how-kanban-enables-continuous-delivery-leankits-perspective\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.planview.com\/"},{"@type":"ListItem","position":2,"name":"How Kanban Enables Continuous Delivery: LeanKit\u2019s Perspective"}]},{"@type":"WebSite","@id":"https:\/\/blog.planview.com\/#website","url":"https:\/\/blog.planview.com\/","name":"Planview Blog","description":"Leading the conversation on digital connected work","publisher":{"@id":"https:\/\/blog.planview.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.planview.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/blog.planview.com\/#organization","name":"Planview","url":"https:\/\/blog.planview.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.planview.com\/#\/schema\/logo\/image\/","url":"https:\/\/blog.planview.com\/wp-content\/uploads\/2015\/06\/planview-logo-black.png","contentUrl":"https:\/\/blog.planview.com\/wp-content\/uploads\/2015\/06\/planview-logo-black.png","width":280,"height":66,"caption":"Planview"},"image":{"@id":"https:\/\/blog.planview.com\/#\/schema\/logo\/image\/"},"sameAs":["http:\/\/www.facebook.com\/pages\/Planview-Inc\/89422974772","https:\/\/x.com\/Planview"]},{"@type":"Person","@id":"https:\/\/blog.planview.com\/#\/schema\/person\/fd58aa7028c738371555a4f6fe4032f4","name":"Planview Blog","url":"https:\/\/blog.planview.com\/author\/planviewblog\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/posts\/12088","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/comments?post=12088"}],"version-history":[{"count":0,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/posts\/12088\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/media?parent=12088"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/categories?post=12088"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/tags?post=12088"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}