Kanban and Lean

Kanban & Lean: The Traffic Flow of Project Management

The Big Picture Analogy

Imagine you’re managing a busy kitchen in a restaurant. Orders come in, chefs cook, food goes out. If too many orders pile up, the kitchen gets chaotic. If chefs stand idle, you’re losing money. The secret? Control the flow.

That’s exactly what Kanban and Lean do for projects!

What is the Kanban Method?

Think of Kanban like a traffic control system for work.

Simple Example:

• Cars (tasks) enter the highway (your workflow)
• Traffic lights (WIP limits) prevent jams
• Everyone keeps moving smoothly!

The 4 Core Principles:

1. Start with what you have - No big changes needed at first
2. Agree to improve gradually - Small steps, big results
3. Respect current roles - Keep your team structure
4. Encourage leadership at all levels - Everyone can suggest improvements

Real Life:

• A software team uses Kanban to track bugs from “Found” → “Fixing” → “Testing” → “Done”
• A marketing team moves campaigns from “Ideas” → “Creating” → “Review” → “Published”

The Kanban Board

This is your visual control center - like a scoreboard for work!

Basic Structure:

┌─────────────┬─────────────┬─────────────┐
│   TO DO     │   DOING     │    DONE     │
├─────────────┼─────────────┼─────────────┤
│ Task A      │ Task C      │ Task E      │
│ Task B      │             │ Task F      │
│ Task D      │             │             │
└─────────────┴─────────────┴─────────────┘

What Makes Cards Move?

Each card (sticky note) represents ONE piece of work:

• Task name - What needs doing
• Who’s working - The person responsible
• Priority - How urgent it is

Example - Pizza Shop Kanban:

• Column 1: Orders Received (dough prep)
• Column 2: Toppings Added
• Column 3: In the Oven
• Column 4: Ready for Pickup

The board shows EVERYTHING at a glance. No surprises!

Work in Progress (WIP) Limits

Here’s the magic rule: Don’t start new work until current work is done!

Why Limits Matter:

Without WIP Limits (Chaos):

• 10 tasks started, 0 finished
• Team stressed and confused
• Quality drops

With WIP Limits (Flow):

• 3 tasks max in “Doing”
• Finish before starting new
• Quality stays high

graph TD
    A["New Task Arrives"] --> B{WIP Limit Reached?}
    B -->|Yes| C["Wait - Help Others First"]
    B -->|No| D["Start Working"]
    C --> E["Finish Current Task"]
    E --> D
    D --> F["Move to Done"]

Simple Example: Imagine you can only juggle 3 balls. If someone throws a 4th ball, you’ll drop them all. WIP limits = knowing your juggling limit!

Real PMP Scenario:

• “Testing” column has WIP limit of 4
• 4 items already in testing
• New item must WAIT
• Testers finish one item first
• Now new item can enter

Cumulative Flow Diagram (CFD)

This chart shows how work flows over time - like a weather map for your project!

What It Shows:

Tasks
  ↑
100│        ████████████████ DONE
   │    ████████████████████
 75│    ████████████████████
   │  ██████████████████████ IN PROGRESS
 50│  ██████████████████████
   │████████████████████████
 25│████████████████████████ TO DO
   │████████████████████████
  0└────────────────────────────→ Time
     Week 1   Week 2   Week 3

How to Read It:

Simple Example: Think of water flowing through a pipe:

• Water entering = new tasks
• Pipe size = team capacity
• Water exiting = completed work

If more water enters than exits, the pipe will burst!

Lean Principles

Lean is about removing waste - doing more with less!

The 5 Core Lean Principles:

graph TD
    A["1. Define Value"] --> B["2. Map the Stream"]
    B --> C["3. Create Flow"]
    C --> D["4. Establish Pull"]
    D --> E["5. Seek Perfection"]
    E --> A

Breaking It Down:

1. Define Value Ask: “What does the customer actually want?”

• Example: Customer wants working software, not long documents

2. Map the Value Stream Find every step from start to finish

• Example: Idea → Design → Code → Test → Deploy

3. Create Flow Remove bottlenecks and delays

• Example: Automate testing instead of waiting for manual reviews

4. Establish Pull Only make what’s needed, when it’s needed

• Example: Don’t write 100 requirements if you’ll only build 10 this month

5. Seek Perfection Always look for ways to improve

• Example: Monthly retrospectives to find better ways

The 7 Wastes (What Lean Eliminates):

Value Stream Mapping

This is like drawing a map of your work journey - every step, every delay!

What It Looks Like:

┌───────────┐    ┌───────────┐    ┌───────────┐
│  REQUEST  │ →  │  DEVELOP  │ →  │   TEST    │
│           │    │           │    │           │
│ Wait: 2d  │    │ Work: 3d  │    │ Work: 1d  │
│ Work: 1hr │    │ Wait: 1d  │    │ Wait: 2d  │
└───────────┘    └───────────┘    └───────────┘
                                       ↓
                               ┌───────────┐
                               │  DEPLOY   │
                               │ Work: 2hr │
                               │ Wait: 0   │
                               └───────────┘

Key Measurements:

• Lead Time = Total time from request to delivery
• Process Time = Actual time spent working
• Wait Time = Time doing nothing (the waste!)

Example Calculation:

• Lead Time: 2d + 1hr + 3d + 1d + 1d + 2d + 2hr = ~9 days
• Process Time: 1hr + 3d + 1d + 2hr = ~4 days
• Wait Time: 2d + 1d + 2d = 5 days

Insight: More than HALF the time is just waiting! That’s where to improve!

How to Create a Value Stream Map:

1. Walk the process - Follow one work item from start to finish
2. Record every step - Include the boring waiting parts
3. Measure times - How long does each step really take?
4. Find the waste - Where are the long waits?
5. Improve - Remove bottlenecks one by one

Putting It All Together

Kanban and Lean work together like peanut butter and jelly:

The PMP Connection:

For your exam, remember:

• Kanban = Visual workflow management
• Lean = Eliminate waste, maximize value
• Both = Continuous improvement (Kaizen!)

Quick Memory Tricks

K.A.N.B.A.N:

• Keep work visible
• Always limit WIP
• Never ignore bottlenecks
• Board shows everything
• Act on data (CFD)
• Nonstop improvement

L.E.A.N:

• Less waste
• Eliminate delays
• Add only value
• Never stop improving

You’ve Got This!

You now understand how to:

• Set up a Kanban board to see all work
• Use WIP limits to prevent chaos
• Read a Cumulative Flow Diagram to spot problems
• Apply Lean principles to cut waste
• Create a Value Stream Map to find improvements

These aren’t just exam topics - they’re real tools used by teams worldwide. Master them, and you’ll manage projects like a pro!