{"id":78765,"date":"2026-07-12T02:25:27","date_gmt":"2026-07-12T02:25:27","guid":{"rendered":"http:\/\/bangla.sitestree.com\/?p=78765"},"modified":"2026-07-12T02:25:28","modified_gmt":"2026-07-12T02:25:28","slug":"scrum-board-vs-kanban-board","status":"publish","type":"post","link":"http:\/\/bangla.sitestree.com\/?p=78765","title":{"rendered":"Scrum board vs Kanban board"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A <strong>Scrum board<\/strong> and a <strong>Kanban board<\/strong> may look similar, but they manage work differently.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Area<\/th><th>Scrum board<\/th><th>Kanban board<\/th><\/tr><\/thead><tbody><tr><td><strong>Work cycle<\/strong><\/td><td>Work is organized into fixed-length sprints<\/td><td>Work moves continuously<\/td><\/tr><tr><td><strong>Board scope<\/strong><\/td><td>Usually shows work selected for the current sprint<\/td><td>Shows the ongoing workflow<\/td><\/tr><tr><td><strong>Planning<\/strong><\/td><td>Sprint Planning selects work before the sprint begins<\/td><td>Work is pulled when capacity becomes available<\/td><\/tr><tr><td><strong>Changes<\/strong><\/td><td>Sprint scope is normally protected during the sprint<\/td><td>New work can be added and prioritized continuously<\/td><\/tr><tr><td><strong>WIP limits<\/strong><\/td><td>Helpful but not required by Scrum<\/td><td>A central Kanban practice<\/td><\/tr><tr><td><strong>Board reset<\/strong><\/td><td>Usually starts fresh for each sprint<\/td><td>Continues without resetting<\/td><\/tr><tr><td><strong>Main metrics<\/strong><\/td><td>Velocity, sprint burndown, sprint goal progress<\/td><td>Lead time, cycle time, throughput, WIP<\/td><\/tr><tr><td><strong>Roles<\/strong><\/td><td>Product Owner, Scrum Master, Developers<\/td><td>No required Kanban-specific roles<\/td><\/tr><tr><td><strong>Delivery<\/strong><\/td><td>Often reviewed at the end of the sprint<\/td><td>Items may be delivered whenever they are ready<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Scrum board example<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">During a two-week sprint:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">Sprint Backlog \u2192 To Do \u2192 In Progress \u2192 Review \u2192 Done<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Only the stories selected for that sprint normally appear on the board.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At the end of the sprint:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>completed stories are reviewed,<\/li>\n\n\n\n<li>incomplete stories return to the Product Backlog,<\/li>\n\n\n\n<li>a new Sprint Backlog is created.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Kanban board example<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For a support team:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">Requested \u2192 Ready \u2192 In Progress <strong>(WIP 3)<\/strong> \u2192 Review <strong>(WIP 2)<\/strong> \u2192 Done<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">When one item moves to Done, the team pulls another item into the available space.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There is no need to wait for the next sprint.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Important similarity<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Both boards:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>visualize work,<\/li>\n\n\n\n<li>show progress,<\/li>\n\n\n\n<li>reveal blockers,<\/li>\n\n\n\n<li>support collaboration,<\/li>\n\n\n\n<li>can use columns such as To Do, In Progress, Review, and Done.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The difference is not mainly the appearance of the board. The difference is <strong>how work is planned and controlled<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Teaching line<\/h3>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>A Scrum board manages work inside a sprint. A Kanban board manages the continuous flow of work.<\/strong><\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">A Scrum team can also use Kanban practices such as WIP limits. This hybrid use is sometimes called <strong>Scrumban<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>REF<\/strong>: AI Tools\/ChatGPT<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A Scrum board and a Kanban board may look similar, but they manage work differently. Area Scrum board Kanban board Work cycle Work is organized into fixed-length sprints Work moves continuously Board scope Usually shows work selected for the current sprint Shows the ongoing workflow Planning Sprint Planning selects work before the sprint begins Work &hellip; <\/p>\n<p><a class=\"more-link btn\" href=\"http:\/\/bangla.sitestree.com\/?p=78765\">Continue reading<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1661],"tags":[],"class_list":["post-78765","post","type-post","status-publish","format-standard","hentry","category-agile-","item-wrap"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":78715,"url":"http:\/\/bangla.sitestree.com\/?p=78715","url_meta":{"origin":78765,"position":0},"title":"Kanban Cadences","author":"Sayed","date":"June 24, 2026","format":false,"excerpt":"Kanban cadences are the regular meetings or feedback loops used in Kanban to manage flow, improve delivery, and remove blockers. Kanban does not require fixed sprints like Scrum. Instead, work flows continuously, and cadences help the team inspect and improve that flow. Your slides describe Kanban using visual workflow, pull\u2026","rel":"","context":"In &quot;Project Management : General&quot;","block_context":{"text":"Project Management : General","link":"http:\/\/bangla.sitestree.com\/?cat=1982"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":78763,"url":"http:\/\/bangla.sitestree.com\/?p=78763","url_meta":{"origin":78765,"position":1},"title":"throughput is it used in scrum as a metric or only for kanban","author":"Sayed","date":"July 12, 2026","format":false,"excerpt":"Throughput can be used in Scrum too. It is not only for Kanban. However: Throughput is more strongly associated with Kanban and flow-based systems.Velocity is more commonly used in Scrum. In Kanban Throughput means: Number of work items completed during a period, such as 12 tickets per week. Because Kanban\u2026","rel":"","context":"In &quot;Agile | \u098f\u099c\u09be\u0987\u09b2&quot;","block_context":{"text":"Agile | \u098f\u099c\u09be\u0987\u09b2","link":"http:\/\/bangla.sitestree.com\/?cat=1661"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":78707,"url":"http:\/\/bangla.sitestree.com\/?p=78707","url_meta":{"origin":78765,"position":2},"title":"Sprint","author":"Sayed","date":"June 24, 2026","format":false,"excerpt":"Sprint length \/ iteration length by methodology MethodologyCorrect termTypical lengthExplanationAgileIteration \/ sprint, depending on frameworkUsually 1\u20134 weeksAgile is a broad mindset, not one fixed process. Different Agile frameworks use different time-boxes.ScrumSprintUsually 1\u20134 weeksScrum uses a fixed-length sprint to plan, build, review, and improve. Your slides define a sprint as a\u2026","rel":"","context":"In &quot;Project Management : General&quot;","block_context":{"text":"Project Management : General","link":"http:\/\/bangla.sitestree.com\/?cat=1982"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":78713,"url":"http:\/\/bangla.sitestree.com\/?p=78713","url_meta":{"origin":78765,"position":3},"title":"Scrum events, XP events, Kanaban Events, Agile Events","author":"Sayed","date":"June 24, 2026","format":false,"excerpt":"From AI Tools\/ChatGPT as is: Key idea Scrum has formal events.XP has practices\/activities more than formal events.Kanban has cadences\/meetings, not required sprints.Agile itself is an umbrella approach, so it does not prescribe one fixed set of events. Your Scrum slides identify the five Scrum events as Sprint, Sprint Planning, Daily\u2026","rel":"","context":"In &quot;Project Management : General&quot;","block_context":{"text":"Project Management : General","link":"http:\/\/bangla.sitestree.com\/?cat=1982"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":78777,"url":"http:\/\/bangla.sitestree.com\/?p=78777","url_meta":{"origin":78765,"position":4},"title":"pull system","author":"Sayed","date":"July 12, 2026","format":false,"excerpt":"Pull system in Kanban means: Work is started only when the next person or stage has capacity. It is the opposite of a push system, where managers or upstream teams keep assigning work even when people are already overloaded. Simple explanation SystemMeaningProblem \/ BenefitPush systemWork is pushed to people whether\u2026","rel":"","context":"In &quot;Agile | \u098f\u099c\u09be\u0987\u09b2&quot;","block_context":{"text":"Agile | \u098f\u099c\u09be\u0987\u09b2","link":"http:\/\/bangla.sitestree.com\/?cat=1661"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":78775,"url":"http:\/\/bangla.sitestree.com\/?p=78775","url_meta":{"origin":78765,"position":5},"title":"kanban? Where would you set the limit: In Progress or Review??","author":"Sayed","date":"July 12, 2026","format":false,"excerpt":"In Kanban, you can set WIP limits on both: In Progress and Review They should have separate limits, because they control different types of work. Your slide says WIP limits are the maximum number of items allowed in each workflow stage, used to prevent overload and identify bottlenecks early. Simple\u2026","rel":"","context":"In &quot;Agile | \u098f\u099c\u09be\u0987\u09b2&quot;","block_context":{"text":"Agile | \u098f\u099c\u09be\u0987\u09b2","link":"http:\/\/bangla.sitestree.com\/?cat=1661"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/posts\/78765","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=78765"}],"version-history":[{"count":1,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/posts\/78765\/revisions"}],"predecessor-version":[{"id":78766,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/posts\/78765\/revisions\/78766"}],"wp:attachment":[{"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=78765"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=78765"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=78765"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}