Post on 02-Jan-2016
Practical Kanbanfor Individuals
and Small Teams
( or All I Really Need to Know, I Learned from a Mickey Mouse
PEZ Dispenser )
Mike DuskisTestbot WranglerWeb DevelopmentOFI Tech Dojo
July 23, 2015
PRESENTATION MAP
Why it Works
Example for an individual
Introductions
Kanban in60 Seconds
Example for a small team
KANBAN IN 60 SECONDS
Ach! The boss
sent us
another
rush job.
Priority 1!
Which of the 27 rush jobs in progress should we suspend?
WHY IT WORKS
Ready Single pull queue
➔ Exactly one way to request service
➔ Exactly one answer to “what should I do next?”
WHY IT WORKS
Ready Single pull queue
➔ Exactly one way to request service
➔ Exactly one answer to “what should I do next?”
➔ Naturally balances load within the team
WHY IT WORKS
Ready Single pull queue
➔ Exactly one way to request service
➔ Exactly one answer to “what should I do next?”
➔ Naturally balances load within the team
➔ Simple for management to prioritize
WHY IT WORKS
Ready Single pull queue
➔ Exactly one way to request service
➔ Exactly one answer to “what should I do next?”
➔ Naturally balances load within the team
➔ Simple for management to prioritize
➔ Queue length indicates unmet demand
WHY IT WORKS
Work-in-progress (WIP) limit
➔ Shortens cycle time
➔ Reduces clutter
➔ Eliminates status ambiguity
In Progress
WHY IT WORKS
Work-in-progress (WIP) limit
➔ Shortens cycle time
➔ Reduces clutter
➔ Eliminates status ambiguity
➔ Forces management to make the hard choices
In Progress
WHY IT WORKS
Work-in-progress (WIP) limit
➔ Shortens cycle time
➔ Reduces clutter
➔ Eliminates status ambiguity
➔ Forces management to make the hard choices
➔ Boosts team morale (really!)
In Progress
Feature Team
dev test
Maintenance Team
dev test
Feature Team
dev test
Integration Team
test
UAT
Deployment Team
test
More roles than individuals
Radically varying skill levels
Uneven workloads
11.5 hour time zone
difference
A COMPLEX TEAM PROBLEM
ANATOMY OF A SIMPLE SOLUTION
Step 1: Map your (actual!) process
user story
ATDD definitions
feature
test plan
exploratory test
scripted test
automated test
test results
risk assessment
process metrics
ANATOMY OF A SIMPLE SOLUTION
Step 2: Abstract your workflow
user story
ATDD definitions
feature
test plan
exploratory test
scripted test
automated test
test results
risk assessment
process metrics
Planning
Development
Execution
Analysis
ANATOMY OF A SIMPLE SOLUTION
Step 3: Translate your workflow to pull queues
Planning Exploration and Development Execution Analysis
Ready Doing Blocked Ready Doing Blocked Ready Doing Ready Doing Done!
ANATOMY OF A SIMPLE SOLUTION
Step 4: Set initial WIP limits
Planning Exploration and Development Execution Analysis
Ready Doing Blocked Ready Doing Blocked Ready Doing Ready Doing Done!
ANATOMY OF A SIMPLE SOLUTION
Execute, Learn, Adjust
Planning Exploration and Development Execution Analysis
Ready Doing Blocked Ready Doing Blocked Ready Doing Ready Doing Done!
ANATOMY OF A SIMPLE SOLUTION
Execute, Learn, Adjust
Planning Exploration and Development Execution Analysis
Ready Doing Blocked Ready Doing Blocked Ready Doing Ready Doing Done!
ANATOMY OF A SIMPLE SOLUTION
Execute, Learn, Adjust
Planning Exploration and Development Execution Analysis
Ready Doing Blocked Ready Doing Blocked Ready Doing Ready Doing Done!
ANATOMY OF A SIMPLE SOLUTION
Execute, Learn, Adjust
Planning Exploration and Development Execution Analysis
Ready Doing Blocked Ready Doing Blocked Ready Doing Ready Doing Done!
ANATOMY OF A SIMPLE SOLUTION
Execute, Learn, Adjust
Planning Exploration and Development Execution Analysis
Ready Doing Blocked Ready Doing Blocked Ready Doing Ready Doing Done!
ANATOMY OF A SIMPLE SOLUTION
Execute, Learn, Adjust
Planning Exploration and Development Execution Analysis
Ready Doing Blocked Ready Doing Blocked Ready Doing Ready Doing Done!