Study guide
10.2 Kanban Framework
PMI Agile Certified Practitioner PMI-ACP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & PMI-ACP Exam Overview
1.1 PMI-ACP Certification & Exam Facts 1.2 Overview of Agile Methodologies 1.3 How to Study for the PMI-ACP Exam
2 Chapter 2: Agile Mindset & Core Principles
2.1 The Agile Manifesto (4 Values & 12 Principles) 2.2 Lean Principles & Waste Elimination 2.3 Systems Thinking & Complexity Adaptation
3 Chapter 3: Agile Values, Culture & Mindset
3.1 Servant Leadership in Agile 3.2 Continuous Improvement & Learning Culture 3.3 Transparency, Inspection & Adaptation
4 Chapter 4: Agile Leadership & Team Dynamics
4.1 Team Formation & Dynamics 4.2 Emotional Intelligence & Adaptive Leadership 4.3 Coaching, Mentoring & Facilitation
5 Chapter 5: Stakeholder Engagement & Conflict Resolution
5.1 Stakeholder Engagement & Communication 5.2 Conflict Resolution in Agile 5.3 Establishing Team Charter & Rules of Engagement
6 Chapter 6: Product Value & Vision
6.1 Product Vision, Roadmap & Value Proposition 6.2 Customer-Centric Product Management 6.3 Value-Driven Delivery & ROI Metrics
7 Chapter 7: Product Backlog Management & Prioritization
7.1 Product Backlog Grooming & Refinement 7.2 Value Prioritization Techniques 7.3 Feedback Loops & Minimum Viable Product
8 Chapter 8: Iterative Delivery & Agile Estimation
8.1 Planning & Estimation Techniques 8.2 Velocity, Capacity & Release Planning 8.3 Timeboxing & Iteration Execution
9 Chapter 9: Quality, Engineering Practices & Risk Management
9.1 Agile Quality & Technical Excellence 9.2 Test-Driven Development & ATDD 9.3 Agile Risk Management
10 Chapter 10: Agile Frameworks Deep-Dive: Scrum, Kanban & XP
10.1 Scrum Framework 10.2 Kanban Framework 10.3 Extreme Programming (XP)
11 Chapter 11: Scaled Agile Frameworks & Enterprise Agile
11.1 Scaled Agile Frameworks 11.2 Hybrid & Tailoring Approaches 11.3 PMI-ACP Exam Review & Final Preparation
10.2 Kanban Framework
Key Takeaways Explain This Topic AI
Kanban is an evolutionary, flow-based management framework often taught through the Kanban Method's 6 Core Practices: Visualize workflow, Limit WIP, Manage flow, Make policies explicit, Implement feedback loops, and Improve collaboratively.
Little's Law relates averages in a stable system: average time in the chosen boundary equals average WIP divided by average throughput when units and the observation period are consistent.
Cumulative Flow Diagrams (CFDs) track cumulative work items across workflow stages over time; horizontal distance measures Lead Time, vertical distance measures WIP, and line slope indicates Throughput.
Service Level Expectations (SLE) provide probabilistic forecasts for completion (e.g., 85% of work items complete in 8 days or fewer) rather than deterministic target deadlines.
Classes of Service (Expedite, Fixed Date, Standard, Intangible) are explicit Kanban Method policies for different cost-of-delay profiles; teams must inspect their effect on flow.
Last updated: August 2026
10.2 Kanban Framework
Originating from the Toyota Production System (TPS) and adapted for knowledge work by David J. Anderson, Kanban is an evolutionary method for managing and improving work systems. Unlike Scrum, which relies on fixed timeboxed iterations, Kanban is a flow-based approach that emphasizes continuous delivery, workload optimization, and minimizing system friction.
The Core Philosophy & 6 Core Practices of Kanban
Kanban does not require altering existing roles or organizational structures immediately; instead, it starts with the current process and drives continuous incremental improvement (Kaizen). The Kanban Method is commonly taught through 6 Core Practices :
1. Visualize the Workflow
The first step is making invisible knowledge work visible. Using a Kanban Board , work items are represented as cards moving across vertical columns representing workflow stages (e.g., To Do , Analysis , Development , Testing , Deployment ). Visualizing work reveals hidden dependencies, queues, and operational bottlenecks.
2. Limit Work in Progress (WIP)
Imposing explicit WIP Limits on workflow columns prevents teams from taking on more work than their capacity allows. WIP limits transform a push system into a pull system , where team members pull new work into a column only when existing items move out, adhering to the principle: "Stop starting, start finishing."
3. Manage Flow
Flow refers to the movement of work items through the production system. Managing flow involves monitoring how smoothly work items progress, minimizing idle time, avoiding context switching, and proactively clearing blockers .
4. Make Policies Explicit
Make workflow definitions and operating policies explicit and accessible to the people managing the work. A physical display is not required, and the policy should fit the service. Explicit policies remove ambiguity and empower self-organizing teams to make consistent operational decisions.
5. Implement Feedback Loops
Kanban utilizes structured reviews (known as Kanban Cadences ) at operational, strategy, and service-delivery levels. Key feedback loops include the Daily Standup (Kanban Meeting), Strategy Review, Service Delivery Review, and Operations Review.
6. Improve Collaboratively, Evolve Experimentally
Kanban promotes scientific, empirical improvement. Teams use models (such as the Theory of Constraints or Lean waste principles) to form hypotheses, execute small process experiments, measure results, and evolve continuously.
Core Practice Operational Action PMI-ACP Exam Impact
Visualize Workflow Map all workflow stages on a visible board Exposes hidden work, queues, and process handoffs.
Limit WIP Define explicit WIP control, often numeric limits for states Constrains overloading and exposes flow problems; outcomes must be measured.
Manage Flow Measure cycle time and remove blockers Optimizes system throughput rather than individual resource utilization.
Make Policies Explicit Write clear entry/exit criteria for columns Ensures consistent quality and enables decentralized team decisions.
Implement Feedback Loops Hold regular operational cadences Fosters continuous alignment between operations and strategic goals.
Improve Collaboratively Use scientific method & flow metrics Drives sustainable, data-backed process evolution.
Flow Metrics, Little's Law & Service Level Expectations (SLE)
Quantitative measurement is central to Kanban. Rather than estimating work in relative story points or velocity, The current Kanban Guide identifies four required flow metrics:
Work in Progress (WIP) : The number of work items that have started but not finished.
Throughput : The number of work items finished per unit of time; count items rather than a story-point total.
Work Item Age : The elapsed time between an item's start and the current time while it remains unfinished.
Cycle Time : The elapsed time from when an item starts until it finishes.
A team may also measure broader lead time from request to delivery. State the start and finish boundaries whenever using either term. Customer Request Created
- │
- ├────────────────────── LEAD TIME ──────────────────────┐
- │ │
- ▼ ▼
- [Backlog Entry] ───► [Work Started] ───────────────► [Work Delivered]
- │ │
- └────────── CYCLE TIME ─────────────┘
- Little's Law in Flow Systems
For a stable system observed over a consistent boundary and period, Little's Law relates average WIP, average throughput, and average time in the system: Lead Time = WIP Throughput \text{Lead Time} = \frac{\text{WIP}}{\text{Throughput}} Lead Time = Throughput WIP
Alternatively, for active execution within team boundaries: Cycle Time = WIP Throughput \text{Cycle Time} = \frac{\text{WIP}}{\text{Throughput}} Cycle Time = Throughput WIP
Practical Example & Exam Math:
Suppose a software team maintains an average WIP of 24 work items across active columns, and their historical Throughput is 4 items per day .
Using Little's Law: Cycle Time = 24 items 4 items/day = 6 days \text{Cycle Time} = \frac{24\text{ items}}{4\text{ items/day}} = 6\text{ days} Cycle Time = 4 items/day 24 items = 6 days .
If a stable-system planning scenario targets an average Cycle Time of 4 days while Throughput remains 4 items/day, the corresponding target average WIP is: WIP = Cycle Time × Throughput = 4 days × 4 items/day = 16 items \text{WIP} = \text{Cycle Time} \times \text{Throughput} = 4\text{ days} \times 4\text{ items/day} = 16\text{ items} WIP = Cycle Time × Throughput = 4 days × 4 items/day = 16 items
A lower average WIP is associated with a lower average cycle time when throughput and system stability hold. Changing a board limit is an experiment, not a guarantee; monitor work-item age, blocked work, throughput, and cycle-time distribution to verify the effect.
Service Level Expectations (SLE)
A Service Level Expectation (SLE) is a probabilistic forecast based on historical Cycle Time data. An SLE consists of two components: a time duration and an associated probability (e.g., "85% of work items are completed in 10 days or fewer" ).
Unlike deterministic rigid deadlines, an SLE uses statistical distribution (often derived from a Cycle Time Scatterplot) to help teams manage customer expectations realistically and flag aging work items before they breach SLA thresholds.
Cumulative Flow Diagram (CFD) Analysis & Classes of Service
A Cumulative Flow Diagram (CFD) is a useful Kanban diagnostic. A CFD charts the cumulative total number of work items in each state of the workflow over time. Total Items
- ▲
- │ / Completed (Departure Line)
- │ /
- │ / <--- Slope = Throughput
- │ /
- │ /--------------/ Testing
- │ /--------------/ <--- Vertical Distance = WIP
- │ /--------------/ Development
- │ /--------------/ Analysis
- │ / (Arrival Line)
- └──────────────────────────────────────────► Time
- |<--- Horizontal Distance = Lead Time --->|
Key CFD Diagnostic Indicators:
Horizontal Distance : The horizontal gap between the top boundary (arrival) and the bottom boundary (departure) represents the Lead Time (or Cycle Time) for items entering the system at that time.
Vertical Distance : The vertical gap between two lines represents the total WIP present in that state or set of states.
Line Slope : The slope of the top line represents the Arrival Rate , while the slope of the bottom line represents the Departure Rate (Throughput) . Parallel lines indicate a stable system.
Widening Band : A widening section in a specific stage indicates a bottleneck —work is arriving faster than it can be processed, causing WIP to accumulate.
Narrowing Band : A narrowing section indicates starvation or capacity underutilization in that workflow stage.
Classes of Service
Not all work items carry equal risk or cost of delay. The Kanban Method commonly uses four Classes of Service to determine how they should be prioritized and pulled through the system:
Class of Service Priority / WIP Rules Cost of Delay Profile Typical Use Case
Expedite Urgent treatment under an explicit policy; often tightly limited and may exceed a normal WIP limit only if the policy permits Extreme and immediate financial/operational loss per hour Severe production outage, critical security patch
Fixed Date Scheduled based on deadline date; prioritized as target date approaches High penalty if missed, low cost of delay until near deadline Regulatory compliance deadline, trade show release
Standard Normal service policy; sequencing rule is explicit and context-specific Gradual, predictable increase in cost of delay over time Standard user feature, routine bug fix
Intangible Policy balances low immediate urgency against accumulating long-term risk Low cost of delay initially, potential long-term risk Technical debt refactoring, infrastructure upgrades
Explicit class-of-service and WIP policies help teams balance urgency with flow; inspect the data because no class policy guarantees stability.