{"id":12200,"date":"2019-04-10T14:38:04","date_gmt":"2019-04-10T19:38:04","guid":{"rendered":"https:\/\/blog.planview.com\/?p=12200"},"modified":"2020-07-23T11:56:45","modified_gmt":"2020-07-23T16:56:45","slug":"measuring-batch-size-wip-and-throughput","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/","title":{"rendered":"Measuring Batch Size, WIP, and Throughput"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-12201\" src=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput.jpg\" alt=\"\" width=\"800\" height=\"427\" srcset=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput.jpg 800w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput-300x160.jpg 300w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput-768x410.jpg 768w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput-750x400.jpg 750w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><\/p>\n<p style=\"font-weight: 300;\">The part 1 of this series,\u00a0<a href=\"\/5-lean-and-agile-metrics-to-track-with-your-team\/\" data-ol-has-click-handler=\"\">5 Lean and Agile Metrics to Measure Track with Your Team: Lead Time and Cycle Time<\/a>, I shared two of the five Lean and Agile metrics to track. In this blog, we\u2019ll talk about measuring batch size, WIP, and throughput. Let\u2019s get started.<\/p>\n<p style=\"font-weight: 300;\">The goal for any Agile team is to reach a state of continuous delivery. This requires teams to eliminate the traditional start-stop-start project initiation and development process, and the mentality that goes along with it. How do teams accomplish this? By actively controlling their batch sizes.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 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\/measuring-batch-size-wip-and-throughput\/#BATCH_SIZE_HOW_MUCH_WORK_ARE_WE_AIMING_TO_COMPLETE_DURING_THIS_SPRINT\" >BATCH SIZE: HOW MUCH WORK ARE WE AIMING TO COMPLETE DURING THIS SPRINT?<\/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\/measuring-batch-size-wip-and-throughput\/#WIP_HOW_MUCH_ARE_WE_WORKING_ON_RIGHT_NOW\" >WIP: HOW MUCH ARE WE WORKING ON\u00a0RIGHT NOW?<\/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\/measuring-batch-size-wip-and-throughput\/#THROUGHPUT_VELOCITY_AND_LITTLES_LAW\" >THROUGHPUT (VELOCITY) AND LITTLE\u2019S LAW:<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/#ONWARDS_AND_UPWARDS\" >ONWARDS AND UPWARDS!<\/a><\/li><\/ul><\/nav><\/div>\n<h2 style=\"font-weight: 600;\"><span class=\"ez-toc-section\" id=\"BATCH_SIZE_HOW_MUCH_WORK_ARE_WE_AIMING_TO_COMPLETE_DURING_THIS_SPRINT\"><\/span>BATCH SIZE: HOW MUCH WORK ARE WE AIMING TO COMPLETE DURING THIS SPRINT?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p style=\"font-weight: 300;\"><b><strong>What It Is:<\/strong><\/b>\u00a0How many work items, or the total size of work, being pulled in at the start of each sprint.<\/p>\n<p style=\"font-weight: 300;\"><b><strong>How It\u2019s Measured:<\/strong><\/b>\u00a0Estimated level of effort, measured by story point sizes, number of work items, etc.<\/p>\n<p style=\"font-weight: 300;\"><b><strong>What It Tells Us:<\/strong><\/b>\u00a0What we think our capacity is for any given period, which is valuable for creating realistic estimates during roadmap planning.<\/p>\n<p style=\"font-weight: 300;\">Batch size is a measure of how much work\u2014the requirements, designs, code, tests, and other work items\u2014is pulled into the system during any given sprint. In Agile, batch size isn\u2019t just about maintaining focus\u2014it\u2019s also about managing cost of delay. Small batches go through the system faster and with less variability than larger batches. They also foster faster learning\u2014the faster you can get something out the door and see how your customer reacts to it, the faster you can incorporate those learnings into future work.<\/p>\n<h2 style=\"font-weight: 600;\"><span class=\"ez-toc-section\" id=\"WIP_HOW_MUCH_ARE_WE_WORKING_ON_RIGHT_NOW\"><\/span>WIP: HOW MUCH ARE WE WORKING ON\u00a0<em>RIGHT NOW?<\/em><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p style=\"font-weight: 300;\"><b><strong>What It Is:\u00a0<\/strong><\/b>A snapshot metric that shows how many work items are actively being worked on at any given time.<\/p>\n<p style=\"font-weight: 300;\"><b><strong>How It\u2019s Measured:<\/strong><\/b>\u00a0Teams using Kanban boards can see WIP by counting how many cards are currently in their active\/in process\/doing board lanes (digital boards are able to measure this automatically).<\/p>\n<p style=\"font-weight: 300;\"><b><strong>What It Tells Us:<\/strong><\/b>\u00a0Knowing this number over time helps to highlight whether a team is starting work items before finishing existing WIP (aka creating a push-based system instead of the desired pull-based system).<\/p>\n<p style=\"font-weight: 300;\">While batch size tells us how much work we\u2019re trying to do in a sprint, WIP (work in progress) tells us how much work we\u2019re actively working on at any given moment.<\/p>\n<p style=\"font-weight: 300;\">Why does this matter? If the goal of any team is to work together to get things done, but everyone is working on different things, collaboration becomes a competitive sport. Rather than working collaboratively to move tasks through the system as quickly as possible, team members compete for each other\u2019s time, energy, and attention, creating a system that becomes stuck in its own inefficiency.<\/p>\n<p style=\"font-weight: 300;\">Having too much work in progress can lead to handoff delays, excessive meetings, context switching, duplicate work, and other wastes that can be avoided with just a little more discipline (learn more about\u00a0<u><a title=\"\" href=\"https:\/\/www.planview.com\/resources\/articles\/wip-limits\/\" target=\"_blank\" rel=\"noopener noreferrer\" data-ol-has-click-handler=\"\">why we need WIP limits here<\/a><\/u>). Actively, as a team, reviewing how much work is in progress, and discussing what can be done to move that work through\u00a0<em>before\u00a0<\/em>pulling new work in can help to alleviate a lot of the tension that many teams experience.<\/p>\n<p style=\"font-weight: 300;\">Like with batch sizes, finding an \u2018optimal\u2019 level of WIP for each team is a process. There\u2019s no formula to determine the precise number of WIP that is appropriate for any team\u2014it varies depending on the size and speed of your team, the efficiency of your process, the complexity and variability inherent to the work, etc.<\/p>\n<p style=\"font-weight: 300;\">Once you determine a realistic, but challenging goal for your team\u2019s current WIP, you can set a WIP limit. Setting WIP limits can be especially helpful for teams who tend to feel overwhelmed, overworked, or disconnected from each other.<\/p>\n<p style=\"font-weight: 300;\">Setting WIP limits forces teams to talk about not only the work itself, but when and how you pull new work into the system and how each team member\u2019s actions affect the system as a whole. It\u2019s a challenging but transformative practice that can greatly impact a team\u2019s performance over time (here\u2019s an\u00a0<u><a title=\"\" href=\"https:\/\/www.planview.com\/resources\/articles\/lkdc-getting-started-wip-limits\/\" target=\"_blank\" rel=\"noopener noreferrer\" data-ol-has-click-handler=\"\">exercise for getting started with WIP limits<\/a><\/u>\u00a0on your team).<\/p>\n<h2 style=\"font-weight: 600;\"><span class=\"ez-toc-section\" id=\"THROUGHPUT_VELOCITY_AND_LITTLES_LAW\"><\/span>THROUGHPUT (VELOCITY) AND LITTLE\u2019S LAW:<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p style=\"font-weight: 300;\"><b><strong>What It Is:<\/strong><\/b>\u00a0A measure of how many work items are completed in a particular time unit.<\/p>\n<p style=\"font-weight: 300;\"><b><strong>How It\u2019s Measured:<\/strong><\/b>\u00a0On a Kanban board\u2014cards per day, cards, per week, etc.<\/p>\n<p style=\"font-weight: 300;\"><b><strong>What It Tells Us:<\/strong><\/b>\u00a0How efficiently the team is completing work; demonstrates how adding more work to the system might impact cycle time.<\/p>\n<p style=\"font-weight: 300;\">Throughput (sometimes called\u00a0<em>velocity)\u00a0<\/em>is the average number of units processed per time unit. In an Agile system, examples can include \u201ccards per day,\u201d \u201ccards per week,\u201d or \u201cstory points per iteration.\u201d<\/p>\n<p style=\"font-weight: 300;\">Measuring throughput can be very useful for forecasting, especially after a fair amount of data has been collected (over several sprints). Since throughput reports track the forecasted and completed work over several iterations, the more iterations, the more accurate the forecast.<\/p>\n<p style=\"font-weight: 300;\">Product managers\/owners can use throughput to predict how quickly a team can work through its current backlog (e.g., \u201cAre we going to finish the items on the board by the end of the current sprint?\u201d).<\/p>\n<p style=\"font-weight: 300;\">Since development work includes plenty of variability, throughput is important to track and define according to what impacts\u00a0<em>your<\/em>\u00a0workflows. Take a moment to consider what your definition of throughput\u2014cards per day, cards per week, etc.\u2014means in the context of your team\u2019s work. Don\u2019t forget to consider the effect of outliers in your measurement, as one significant event can drastically change the entire average. It is most effective to view throughput either as a trend or by combining it with other metrics,\u00a0<a title=\"\" href=\"\/5-lean-and-agile-metrics-to-track-with-your-team\/\" target=\"_blank\" rel=\"noopener noreferrer\" data-ol-has-click-handler=\"\">such as cycle time and lead time<\/a>, to get a holistic picture of your team&#8217;s capacity and productivity.<\/p>\n<p style=\"font-weight: 300;\">Related to throughput is Little&#8217;s Law, a hypothetical formula that can be used to demonstrate how changes made to the system&#8217;s input can impact the system&#8217;s output.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-12202\" src=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/cycle-time.png\" alt=\"\" width=\"800\" height=\"168\" srcset=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/cycle-time.png 800w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/cycle-time-300x63.png 300w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/cycle-time-768x161.png 768w, https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/cycle-time-750x158.png 750w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><\/p>\n<p><em>Cycle time formula.<\/em><\/p>\n<p style=\"font-weight: 300;\">For example, if a team has 25 cards in process (i.e., their total WIP) and a throughput of 1.5 cards\/day, then the average cycle time is 16.66 days. If the same team maintains the same throughput but increases its total WIP to 40 cards, the average cycle time becomes 26.66 days. Little\u2019s Law can be valuable to show how reducing WIP can reduce cycle time. You can also improve cycle time by increasing throughput, although this is much more difficult to do than reducing the total WIP.<\/p>\n<h2 style=\"font-weight: 600;\"><span class=\"ez-toc-section\" id=\"ONWARDS_AND_UPWARDS\"><\/span>ONWARDS AND UPWARDS!<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p style=\"font-weight: 300;\">It\u2019s worth mentioning once more that metrics are not universally helpful\u2014whenever you decide to start reporting on any metric, be sure to ask yourself:\u00a0<em>Why? Why does this metric matter?\u00a0<\/em><b><strong>What goal is this helping us achieve?<\/strong><\/b><\/p>\n<p style=\"font-weight: 300;\">Aim to always approach reporting with openness and curiosity\u2014looking to learn new things, not confirming what you already know.<\/p>\n<p style=\"font-weight: 300;\">Use Lean and Agile metrics to identify issues and highlight opportunities for improvement, not to punish anyone, prove a point, or achieve any other personal ambitions. Lean and Agile metrics should be your friends, tools to help your team evolve into a more efficient, more collaborative, and ultimately, healthier system. Use Lean and Agile metrics for good, not evil, and you\u2019ll see your team achieve great things.<\/p>\n<p style=\"font-weight: 300;\">Luckily, if you\u2019re already practicing Kanban, you are already generating data that will give you insights into how to improve your Lean and Agile workflow. If you aren\u2019t, I encourage you to go through the exercises in the\u00a0<u><a title=\"\" href=\"https:\/\/info.planview.com\/kanban-roadmap-_ebook_lad_en_reg.html\" target=\"_blank\" rel=\"noopener noreferrer\" data-ol-has-click-handler=\"\">Kanban Roadmap<\/a><\/u>\u00a0with your team. Once you have a board that accurately reflects your current process, you\u2019ll have everything you need to begin your team\u2019s evolution. Introducing Lean and Agile metrics can breathe new life into a team, rallying everyone around the opportunity to work smarter, get more done, and stress less. Happy reporting!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The part 1 of this series,\u00a05 Lean and Agile Metrics to Measure Track with Your Team: Lead Time and Cycle Time, I shared two of the five Lean and Agile metrics to track. In this blog, we\u2019ll talk about measuring batch size, WIP, and throughput. Let\u2019s get started. The goal for any Agile team is&#8230;<\/p>\n","protected":false},"author":147,"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":[521,38],"tags":[511],"class_list":["post-12200","post","type-post","status-publish","format-standard","hentry","category-lean-agile","category-work-collaboration","tag-leankit"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.4 (Yoast SEO v27.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Measuring Batch Size, WIP, and Throughput - Blog | Planview<\/title>\n<meta name=\"description\" content=\"In this blog, we\u2019ll talk about measuring batch size, WIP, and throughput. Let\u2019s get started.\" \/>\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\/measuring-batch-size-wip-and-throughput\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Measuring Batch Size, WIP, and Throughput\" \/>\n<meta property=\"og:description\" content=\"In this blog, we\u2019ll talk about measuring batch size, WIP, and throughput. Let\u2019s get started.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/\" \/>\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=\"2019-04-10T19:38:04+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-07-23T16:56:45+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput.jpg\" \/>\n<meta name=\"author\" content=\"Alex Glabman\" \/>\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=\"Alex Glabman\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/\"},\"author\":{\"name\":\"Alex Glabman\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#\\\/schema\\\/person\\\/7a8b1cd2eff26363d838defbb7ed2e45\"},\"headline\":\"Measuring Batch Size, WIP, and Throughput\",\"datePublished\":\"2019-04-10T19:38:04+00:00\",\"dateModified\":\"2020-07-23T16:56:45+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/\"},\"wordCount\":1326,\"publisher\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.planview.com\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/Measuring-Batch-Size-WIP-and-Throughput.jpg\",\"keywords\":[\"LeanKit\"],\"articleSection\":[\"Enterprise Agile Planning\",\"Work Management for Teams\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/\",\"url\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/\",\"name\":\"Measuring Batch Size, WIP, and Throughput - Blog | Planview\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.planview.com\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/Measuring-Batch-Size-WIP-and-Throughput.jpg\",\"datePublished\":\"2019-04-10T19:38:04+00:00\",\"dateModified\":\"2020-07-23T16:56:45+00:00\",\"description\":\"In this blog, we\u2019ll talk about measuring batch size, WIP, and throughput. Let\u2019s get started.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/#primaryimage\",\"url\":\"https:\\\/\\\/blog.planview.com\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/Measuring-Batch-Size-WIP-and-Throughput.jpg\",\"contentUrl\":\"https:\\\/\\\/blog.planview.com\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/Measuring-Batch-Size-WIP-and-Throughput.jpg\",\"width\":800,\"height\":427},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/measuring-batch-size-wip-and-throughput\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blog.planview.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Measuring Batch Size, WIP, and Throughput\"}]},{\"@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\\\/7a8b1cd2eff26363d838defbb7ed2e45\",\"name\":\"Alex Glabman\",\"description\":\"As Planview LeanKit's Product Manager, Alex enjoys simplifying the complex for prospects and customers. With hands-on experience implementing Lean and Agile across organizations and a passion for surfacing data, Alex is a champion for continuous improvement, eating elephants one bite at a time. Vanderbilt alum; dog lover; bourbon nerd.\",\"url\":\"https:\\\/\\\/blog.planview.com\\\/author\\\/alex-glabman\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Measuring Batch Size, WIP, and Throughput - Blog | Planview","description":"In this blog, we\u2019ll talk about measuring batch size, WIP, and throughput. Let\u2019s get started.","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\/measuring-batch-size-wip-and-throughput\/","og_locale":"en_US","og_type":"article","og_title":"Measuring Batch Size, WIP, and Throughput","og_description":"In this blog, we\u2019ll talk about measuring batch size, WIP, and throughput. Let\u2019s get started.","og_url":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/","og_site_name":"Planview Blog","article_publisher":"http:\/\/www.facebook.com\/pages\/Planview-Inc\/89422974772","article_published_time":"2019-04-10T19:38:04+00:00","article_modified_time":"2020-07-23T16:56:45+00:00","og_image":[{"url":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput.jpg","type":"","width":"","height":""}],"author":"Alex Glabman","twitter_card":"summary_large_image","twitter_creator":"@Planview","twitter_site":"@Planview","twitter_misc":{"Written by":"Alex Glabman","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/#article","isPartOf":{"@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/"},"author":{"name":"Alex Glabman","@id":"https:\/\/blog.planview.com\/#\/schema\/person\/7a8b1cd2eff26363d838defbb7ed2e45"},"headline":"Measuring Batch Size, WIP, and Throughput","datePublished":"2019-04-10T19:38:04+00:00","dateModified":"2020-07-23T16:56:45+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/"},"wordCount":1326,"publisher":{"@id":"https:\/\/blog.planview.com\/#organization"},"image":{"@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput.jpg","keywords":["LeanKit"],"articleSection":["Enterprise Agile Planning","Work Management for Teams"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/","url":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/","name":"Measuring Batch Size, WIP, and Throughput - Blog | Planview","isPartOf":{"@id":"https:\/\/blog.planview.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/#primaryimage"},"image":{"@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput.jpg","datePublished":"2019-04-10T19:38:04+00:00","dateModified":"2020-07-23T16:56:45+00:00","description":"In this blog, we\u2019ll talk about measuring batch size, WIP, and throughput. Let\u2019s get started.","breadcrumb":{"@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/#primaryimage","url":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput.jpg","contentUrl":"https:\/\/blog.planview.com\/wp-content\/uploads\/2020\/02\/Measuring-Batch-Size-WIP-and-Throughput.jpg","width":800,"height":427},{"@type":"BreadcrumbList","@id":"https:\/\/blog.planview.com\/measuring-batch-size-wip-and-throughput\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.planview.com\/"},{"@type":"ListItem","position":2,"name":"Measuring Batch Size, WIP, and Throughput"}]},{"@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\/7a8b1cd2eff26363d838defbb7ed2e45","name":"Alex Glabman","description":"As Planview LeanKit's Product Manager, Alex enjoys simplifying the complex for prospects and customers. With hands-on experience implementing Lean and Agile across organizations and a passion for surfacing data, Alex is a champion for continuous improvement, eating elephants one bite at a time. Vanderbilt alum; dog lover; bourbon nerd.","url":"https:\/\/blog.planview.com\/author\/alex-glabman\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/posts\/12200","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\/147"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/comments?post=12200"}],"version-history":[{"count":0,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/posts\/12200\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/media?parent=12200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/categories?post=12200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/tags?post=12200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}