Introductions
• Name
• Current job role
• Experience with Kanban
• Expectations of this class
3
Slide 4
Slide 4 text
Course Objectives and Style
4
Slide 5
Slide 5 text
Course Objectives
• Upon completion of this course you will be able to
• Describe Kanban.
• Apply principles to solve workflow problems.
• Describe various tools.
• Choose the right tools for your team.
5
Practitioner
“Excellence is an art won by
training and habituation…We
are what we repeatedly do.
Excellence, then, is not an
act but a habit.”
!
— Aristotle
11
Slide 12
Slide 12 text
Case 1
12
Slide 13
Slide 13 text
Team 1
• small
• semi-siloed from development and qe
• ~10 dev, ~3 qe, ~2 se, 1 product manager, 100s of
customers
13
Slide 14
Slide 14 text
Goal
• Effective use of time
• No duplication of effort
• Improve customer experience
• Promotion to larger projects
14
Slide 15
Slide 15 text
Solution
• Personal Kanban
• Dashboards
• Influence through visuals
15
Slide 16
Slide 16 text
Factors for Success
• Trust
• Visual dashboards
16
Slide 17
Slide 17 text
Case 2
17
Slide 18
Slide 18 text
Team 2
• Small
• Siloed from development and qe
• ? dev, ? qe, 10 se, 1 product manager, 3 project
manager, open source, 100s of customers
18
Slide 19
Slide 19 text
Goal
• Break down rigid single points of knowledge failure
• Reduce development friction
• Eliminate duplicate efforts
19
Slide 20
Slide 20 text
Solution
• Team Kanban
• Incremental improvements
20
Slide 21
Slide 21 text
Factors for Success
• Management buy in
• Training
• Effort to minimize “pushing”
• Weekly team syncs
• Proximity of team
21
Slide 22
Slide 22 text
Workflow
22
Slide 23
Slide 23 text
Workflow
Work that is ..
• orchestrated
• repeatable
• organized
• moving from one state to another.
23
Slide 24
Slide 24 text
WIP
• Work in progress
• work that has had resources applied to it
!
• Resources are ..
• people, money,..
24
Slide 25
Slide 25 text
Properties of Tasks
• name
• start date
• end date
• current state
• description
• priority
• owner
25
Slide 26
Slide 26 text
TIP: Sample Task Handling
• What is it?
• Can you do anything with it?
• What is the next step?
26
Slide 27
Slide 27 text
Properties of Projects
• same requirements as a task and are larger in
scope.
• may be comprised of more than one task.
27
Slide 28
Slide 28 text
Task vs Project
Group Exercise
• What is the difference between a task and a
project?
28
Slide 29
Slide 29 text
Additional property
• Size
29
Slide 30
Slide 30 text
Interrupts
• Non planned work that comes in
• customer request
• incident
• request for help from coworker
• single point of knowledge (you) work
• high priority task push from manager
30
Slide 31
Slide 31 text
Blocked work
• Work that can progress no further:
• dependent teams
• blocked by external team
• insufficiently qualified request
• blocked by requester
• dependent on SPOK
• blocked by team
• time dependent
31
Slide 32
Slide 32 text
Work
Team Exercise
Time: 5 minutes
What does a typical work day look like for work that
you do specifically that is non-interrupt based?
Choose a speaker for the group to share summary.
32
Slide 33
Slide 33 text
Interrupts
Team Exercise
Time: 5 minutes
Do you have interrupts and what are they?
!
Choose a (different) speaker for the group to share
summary.
33
Slide 34
Slide 34 text
Done?
Group Exercise
• When is work done?
34
Slide 35
Slide 35 text
Prepping for Success
35
Slide 36
Slide 36 text
Environment
36
Slide 37
Slide 37 text
Values
37
Slide 38
Slide 38 text
Desire
38
Slide 39
Slide 39 text
Motivation
39
Slide 40
Slide 40 text
Connectedness
40
Slide 41
Slide 41 text
Team Vs Individual
41
Slide 42
Slide 42 text
Objectives
• Defined by the team. Not management.
• Defined by the team. Not individuals.
• Everyone has voice, opportunity to speak.
42
Slide 43
Slide 43 text
Tip: Implement as a Team
Communication. Collaboration.
• Discuss objectives.
• Describe work.
• Define lanes.
• Define a task.
• Define a project.
43
Slide 44
Slide 44 text
Tip: Elect a Champion
44
Slide 45
Slide 45 text
Intro to Kanban
45
Slide 46
Slide 46 text
Kanban
• “visual card”
46
Slide 47
Slide 47 text
Kanban - Unit of work
• request
• issue
• defect
unit of work - specific to environment
47
Slide 48
Slide 48 text
What is it ? A System.
• visual process management
• what to do
• when to do it
• how much to do
48
Slide 49
Slide 49 text
What is it ? A Method.
• incremental, evolutionary process improvement
49
Slide 50
Slide 50 text
3 Principles
• Current Process.
• Incremental, Evolutionary Change.
• Respect current process, roles, responsibilities and
titles.
50
Manage flow
• Measure flow of work items through states.
• How fast are we creating value, minimizing risk, and
avoiding cost of delay in predictable manner?
78
Make policies explicit.
80
Story In Progress:
Acceptance criteria are identified. The
story has been divided into tasks. The
“started” date has been recorded.
Review Questions
• Give me an example of the most basic kanban
board.
• Why do we need to make policies explicit?
• Why do we make incremental changes?
85
Slide 86
Slide 86 text
Meetings with Kanban
86
Slide 87
Slide 87 text
Lean Coffee
• Draw “To Do, Doing, Done” on white board.
• Spend 5 minutes to write topics on sticky notes.
• Vote on topics with stickers. Each person gets 2
votes.
• Prioritization of topics based on votes.
87
Slide 88
Slide 88 text
Metrics
88
Slide 89
Slide 89 text
Metrics
• Why?
89
Slide 90
Slide 90 text
Metrics
• What?
• cumulative flow
• type distribution
• efficiency
• average cycle times
90
Slide 91
Slide 91 text
Cumulative Flow Diagram
count of cards in particular state/lane for each day in
a specific time interval.
91
Slide 92
Slide 92 text
Cumulative Flow Diagram
92
Slide 93
Slide 93 text
Distribution
• Count of cards organized by state, task type, or
owner.
93
Slide 94
Slide 94 text
Card Distribution
94
Slide 95
Slide 95 text
Card Distribution
95
Slide 96
Slide 96 text
Efficiency
• relative status (in process, waiting, completed..) of
WIP over time.
• % of work
• gauge efficiency trends
• reduce ratio of work items waiting to be queued
versus items actively processed
96
Slide 97
Slide 97 text
Efficiency Diagram
97
Slide 98
Slide 98 text
Average Cycle Time
• cycle time - time take to move a task from start to
finish including wait time.
• average cycle time - specific to an interval of time
98
Slide 99
Slide 99 text
Little’s Law
N = XR
• N - number in system
• X - Throughput
• R - average time in system
99
Slide 100
Slide 100 text
Utilization Law
U = XS
• U - % of time processing tasks
• X - Output Rate Tasks/Unit of time
• S - Mean service time
100