Beruflich Dokumente
Kultur Dokumente
KANBAN
v
Useful and Inspiring Words
By Practitioners of
v
On the occasion of the 2011 Kanban
Leadership Retreat in Reykjavik, Iceland
David J Anderson
& Associates, Inc.
Management Solutions for Knowledge Workers
Davidhere
The opinions expressed J Anderson
are the authors
and contributors
& and do not expressInc.
Associates, a
position on the subject from David J.
Management Solutions for Knowledge Workers
Anderson and Associates, Inc.
B L U E
H O L E
PRESS
Sequim, WA
Contents
This commentary on
Foundations
Transitioning
Visibility
Limited WIP
Measurement
Flow
Policies
Quality
Improvement
is presented to you by
LeanKit
and by
Contributed Articles
Why Lean-Kanban?
No Board Without a Verb!
Kanban and the Focus on
Fundamentals
Estimates Are Overrated
Kanban and Lean Development
with GreenHoppers Rapid Board
Products and Services
SwiftKanban by Digite
GreenHopper by Atlassian
Lean/Kanban materials
by Blue Hole Press
Foreword
David J. Anderson
Foundations
Foundations
Kanbans 5 core properties (Visualize,
WIP Limits, Policies, Measure, Improve)
include basic, intermediate, and
advanced practices.
Rick Simmons
(United States)
Alisson Vale
(Brazil)
Foundations
People ask me, What is the difference
between lean and kanban? Answer: lean
is a destination; kanban is a means to get
there.
David J. Anderson
(United States)
Karl Scotland
(United Kingdom)
Foundations
Kanbans value is providing insight. Use
it and think of other visualizations and
metrics frameworks to provide different
insight.
Larry Maccherone
(United States)
Jesper Boeg
(Denmark)
Foundations
Card walls are not inherently kanban
systems. They are merely visual control
mechanisms. They allow teams to
visually observe work-in-progress and to
self-organize, assign their own tasks, and
move work from a backlog to complete
without direction from a project or
line manager. However, if there is no
explicit limit to work-in-progress and no
signaling to pull new work through the
system, it is not a kanban system.
David J. Anderson
(United States)
Hillel Glazer
(United States)
Foundations
Demand analysis is the backbone of
the Kanban Method and lies at the
basis of decision making. Youll see that
organizations not studying their demand
are also not implementing Classes of
Service which means they are not able
to allocate against shifting variability
and more likely to end up with a static
Kanban Board.
Maarten Volders
(Belgium)
Chris Hefley
(United States)
Foundations
Our efforts with point estimating and
task breakdown/hours sizing were never
as accurate or useful to us as were our
efforts with focusing on cycle times,
delays, limiting WIP, and swarming.
Frank Vega
(United States)
alyst
Vendor Developer Business An
CIO
Support
er Customer
Project Manag
Working with your distributed team like they were right next to you?!
It's gotta be Swift-Kanban!!
Kanban
Digit, Inc. 82 Pioneer Way, Suite 102, Mountain View, CA 94041 | Contact us: sales@digite.com / 1-650-210-3929
Transitioning
Transitioning
If so few people really get Lean and
Agile, then we should be looking at
those doing the explaining. That would
be us.
Marius de Beer
(South Africa)
Ketil Jensen
(Norway)
Transitioning
Context is relevant, so Kanban allows
you to design processes that fit to the
context, instead of manipulating the
context to fit a specific process
Allison Vale
(Brazil)
David J. Anderson
(United States)
Transitioning
IMO the decisions made at different
levels in the org differ in detail, but the
same heuristics apply if principles are
valid.
John Clifford
(United States)
Rick Simmons
(United States)
Transitioning
If you want to sell kanban to senior
management, learn about their pressures
and needs.
Simon Marcus
(United States)
Maarten Volders
(Belgium)
Transitioning
Your situation is unique and you deserve
to develop a unique process definition
tailored and optimized to your domain,
your workflow, the risks that you
manage, the skills of your team, and the
demands of your customers.
David J. Anderson
(United States)
Hillel Glazer
(United States)
Transitioning
So you can start with doing a lean
transformation and thats always a good
way to go especially if youve got top-
down buy-in from all the executives,
but oftentimes thats not the case. Even a
small team, even one that doesnt have a
whole lot of power in your organization
can start by visualizing their work with
a kanban system and use that to drive
change and to drive improvement, to
drive the beginnings of a lean journey.
Chris Hefley
(United States)
LeanKit Kanb
an
Easy to Use
LeanKit is as simple as sticky notes on a whiteboard with
all the power of Kanban to instantly communicate status.
Global Availability
We're cloud-hosted, supporting your teams wherever
they may be - PCs, touch screens, and iPhones &
iPads via our new iOS app.
Flexible Design
Our board editor allows you to quickly and easily map even the most complex
workflow with an unlimited number of vertical and horizontal lanes and sub-lanes.
Powerful Metrics
Every card move is tracked to generate metrics on cycle time,
variability, efficiency, workload distribution, and what-if forecasting.
WIP Projects
Into Shape!
LeanKit.com
Visibility
Visibility
One of Kanban rules is visualization.
This is one I like the most since I
just cant sit at ease next to the clear
whiteboard. I have that urge to grab
a marker, a bunch of sticky notes and
make the board a little less white.
Pawel Brodzinski
(Poland)
Markus Andrezak
(Germany)
Visibility
By calling something an impediment,
we are making a judgment, which could
create conflict. Instead, visualise the
data.
Karl Scotland
(United Kingdom)
Olav Maassen
(Netherlands)
Visibility
My approach now, to give us better
predictions of lead/cycle times, is to
even further visualize the value stream
and apply improvements to the actual
uncertainty in our process. We have
surely a lot of possible bottlenecks not
visualized or identified.
Mats Yforgs
(Sweden)
Joshua Bloom
(United States)
Visibility
Kanban
for projects
www.TeamProsource.eu
TeamProsourceEU
Limited WIP
Limited WIP
A Kanban pull system cannot be
overloaded if capacity has been set
appropriately.
Dominica DeGrandis
(United States)
Ketil Jensen
(Norway)
Limited WIP
Littles Law means that WIP is a leading
indicator for cycle time, whereas things
like velocity or throughput are trailing
indicators (metrics).
Daniel Vacanti
(United States)
Yuval Yeret
(Israel)
Dai Inglfsson
(Iceland)
Limited WIP
Once you balance demand against
throughput and limit the work-in-
progress within your workflow, magic
will happen. Only the bottleneck
resources will remain fully loaded.
David J. Anderson
(United States)
Measurement
Measurement
Metrics can pull or be pulled. Metrics
should be backed with a theory or be
used as canaries.
Joshua Bloom
(United States)
Larry Maccherone
(United States)
Measurement
Define measures that create knowledge
about whether the current Kanban
system design is meeting its purpose.
Hermanni Hyytil
(Finland)
Dominica DeGrandis
(United States)
Kanban with GreenHopper for JIRA
GreenHopper adds agile project management to any JIRA project. Whether you're a seasoned expert or
just getting started with Lean and Kanban concepts, GreenHopper is perfect for visualizing your existing
process and stimulating incremental improvement.
Principles of Kanban
Kanban is a catalyst for change through small, incremental improvements to your existing process be it
scrum or otherwise. Rooted in Lean manufacturing, Kanban is a signaling system that can be effectively
applied to software development, DevOps, IT Operations, and many other processes.
Horizontal Swimlanes
Separate work items on your Rapid Board using Swimlanes to
help map out your value stream by team, class of service, or any
other categorization. Swimlanes are creating using JQL similar to
Quick Filters.
Jesper Boeg
(Denmark)
Patrick Steyaert
(Belgium)
Flow
A lot of small tasks are failure demand,
i.e., they are tasks created because we
have failed to deliver the actual value in
some way. If we can collect data on this
and analyze it we might be able to get rid
of the root cause of the failure demand
and remove it, freeing up resources that
instead can be focused on delivering
value.
Joakim Sundn
(Sweden)
Policies
Policies
Thinking of a process as a set of policies
is a key element of the Kanban Method.
David J. Anderson
(United States)
Klaus Leopold
(Austria)
Janice Linden-Reed
(United States)
Policies
Customer satisfaction is king. Policies on
cadence-based continuous flow delivery
are a golden gift to the king.
Masa Maeda
(United States)
Policies
The kanban system relies on the policies
being explicit, and the board should
certainly reflect those policies, but I
have never seen a board that by itself
completely defines the policies. I have
seen many come close by posting the
working agreements for each phases
ready and acceptance criteria on (or
next to) the board, and by hanging
each roles pick order near the board,
but I cant think of any teams that use
only the board to make the policies
explicit. Remember that the board is a
visualization and a model, it is not the
system.
Eric Willeke
(United States)
Policies
Today we squeezed 24 priorities that
nobody understood into 3 classes of
service that everybody understood
within a minute! Yes we Kanban :-)
Mike Burrows
(United Kingdom)
Quality
Quality
Defect estimation is waste. Either you
have to fix them, so it doesnt matter, or
you dont so it doesnt matter.
John Clifford
(United States)
Hillel Glazer
(United States)
Pawel Brodzinski
(Poland)
Quality
Probably Deming would have said: Its
nonsense to blame testers for the quality
of the software. Quality starts at the
board of directors.
Klaus Leopold
(Austria)
Reducing work-in-progress, or
shortening the length of an iteration,
will have a significant impact on initial
quality. It appears that the relationship
between quantity of work-in-progress
and initial quality is non-linear; that is,
defects will rise disproportionately to
increases in quantity of WIP.
David J. Anderson
(United States)
Improvement
Improvement
Initially it is called continuous irritation,
eventually continuous improvement.
Katherine Kirk
(United Kingdom)
Eric Willeke
(United States)
Improvement
I have seen teams that adopt Kanban and
then stop innovating. They go through
the mechanics but miss the drive to
challenge their own process any further.
What results is only minor steps.
Olav Maassen
(Netherlands)
Hkan Forss
(Sweden)
Improvement
The slack capacity created by the act of
limiting work-in-progress and pulling
new work only as capacity is available
will enable improvement no one thought
was possible.
David J. Anderson
(United States)
Simon Marcus
(United States)
Improvement
Kanban allows leadership to flourish in
every mind. It is permaculture applied
to knowledge workers. Kanban helps
management to switch to distributed
leadership.
Alexis Nicolas
(France)
Hkan Forss
(Sweden)
xoxo
Waiting for bus to airport. Goodbye
Reykjavik, thanks for all the fish! Had a
great time at #klris. Met amazing people.
Love this community!
Joakim Sundn
(Sweden)
Why Lean-Kanban?
By Alan Shalloway and Jim Trott,
Net Objectives
Why Lean-Kanban?
By Alan Shalloway and Jim Trott, Net Objectives , 2011
product development. Technical, process,
management, value stream, portfolio,
Why Lean-Kanban?
By Alan Shalloway and Jim Trott, Net Objectives , 2011
Scrum offered a middle path between the two.
And it has indeed proven to be extremely suc-
cessful in many organizations for many teams.
And yet, as good as it was at the team level, it
has rarely scaled throughout the organization.
Where it has scaled well, it required an exter-
nal force such as a CEO mandate.
Why Lean-Kanban?
By Alan Shalloway and Jim Trott, Net Objectives , 2011
It has worked successfully at all sizes of or-
ganizations. And putting them together has
been a journey of discovery.
Why Lean-Kanban?
By Alan Shalloway and Jim Trott, Net Objectives , 2011
No Board Without a Verb!
By Arne Roock, IT Agile
Evolutionary change
Improvement of existing processes
B L U E
H O L E
PRESS