5: Kanban, Flow, and Visual Management
- Page ID
- 135060
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)Kanban, Flow, and Visual Management
In Chapter 4, we studied Scrum as an iteration-based framework, one that helps teams work in short time-boxes, create usable increments, inspect progress, gather feedback, and adapt. This chapter shifts the focus from iteration rhythm to flow. Where Scrum organizes work into fixed cycles, Kanban and Lean thinking ask a different set of questions entirely: Where does work wait? Where does it pile up? Where are people overloaded? Where does rework happen? Where are customers left waiting for value, and where are we starting too much while finishing too little? These questions move us beyond the rhythm of iterations and toward a deeper understanding of how work actually moves, or fails to move, through a system.
At its core, this chapter is about learning to see the system as it truly operates, rather than as it appears on the surface. A team may look busy and still deliver slowly. A kitchen may look full and still be inefficient. A process may have many approvals and still produce poor quality. A backlog may contain hundreds of items and still fail to deliver meaningful customer value. Lean and Kanban give us the vocabulary and visual tools to move past the illusion of activity and focus instead on the flow of value, exposing the waste, delays, and bottlenecks that busyness so often conceals.
A simple phrase captures the spirit of this chapter: stop starting and start finishing. Starting work creates activity, but finishing work creates value, and this distinction lies at the heart of everything Lean and Kanban set out to teach. This chapter builds that understanding from the ground up, tracing Lean's roots in the Toyota Production System, introducing pull systems and Kanban boards, and connecting these ideas to practical, everyday examples that make flow-based thinking intuitive rather than abstract.
By the end of this chapter, you should be able to:
- Explain how Lean thinking grew from the Toyota Production System.
- Describe pull systems using the supermarket replenishment story.
- Explain how Kanban supports flow-based work.
- Identify Muda, Mura, and Muri in everyday work.
- Describe common types of waste in Lean.
- Explain why WIP limits improve flow.
- Use 5S or 7S to organize workspaces and workflows.
- Connect Lean thinking to everyday examples such as Lean Kitchen, pre-vacation flow, and Miyawaki forests.
- Explain how the Kanban Pizza Game teaches flow, WIP limits, bottlenecks, and pull.
- Choose between Scrum, Kanban, Lean, and Scrumban based on the nature of the work.
- 5.1: Mapping to Exam Content Outline
- This page connects Kanban and Lean methodologies to PMI-ACP exam themes, emphasizing work visualization, flow management, and waste reduction for better value delivery and continuous improvement. It covers domains like Value-Driven Delivery and Adaptive Planning, and discusses tools such as Kanban boards and WIP limits. Effective exam responses align with core principles like respect for people and systemic issues, while poor responses may lead to team overload and misapplied Lean principles.
- 5.2: Kanban and Flow Guide
- This page discusses Lean Thinking, originating from Toyota's quest for production quality amid post-war constraints, advocating for waste reduction and respectful systems rather than workforce cuts. The principles include "pull" production, continuous improvement, and employee insights, applicable in various settings.
- 5.3: Chapter Summary
- This page explains how Kanban, Lean, and Scrum frameworks assist teams in optimizing work systems. Kanban focuses on managing workflow, Lean on reducing waste while maximizing value, and Scrum on organizing tasks into iterations. It emphasizes Toyota's pull system to prevent overloading, alongside key concepts like waste (Muda), unevenness (Mura), and overburden (Muri). Practical tools from Kanban are presented for better visibility and system enhancement.
- 5.4: PMI-ACP Style Sample Questions
- This page covers Agile and Lean methodologies, emphasizing the visualization of work, limiting WIP, and managing unpredictable workloads with Kanban. It identifies waste in processes and highlights Lean principles focused on system improvement and individual respect. Practical applications of the 5S methodology are included, along with real-world examples like the Kanban Pizza Game, which provides insights into workflow optimization and reinforces the learning outcomes.