LKNL12: Kanban for the whole value stream
56
Visualize the work – Kanban for the whole value stream @duarte_vasco and @lasseziegler
-
Upload
vasco-duarte -
Category
Documents
-
view
634 -
download
0
description
You’ve been there before. You know better, you have a good idea to support your agile transition. Work starts, things work well at first, but then you bump against organizational barriers. Sales, Marketing, Support all have a different language and a different view into the value stream. How can we start an organizational change without a shared model of how the company should be organized? Those are all symptoms of a gap in our Agile community: we lack a organizational model for company-wide Agile adoption and company-wide continuous improvement. Examples of this include: no company-wide flow-model (kanban) from idea to sales to idea and so on; we have no way to evaluate where the bottlenecks are the moment they are not in “our silo”. We lack a theoretical model for designing software organizations. A theory is something that informs day-to-day decisions and experiments (e.g. PDCA). In this talk we will explain an organizational design concept developed over several years, and use concrete examples to describe a model that you can use in support of - not only your agile adoption - but your company improvement process and your new organizational design.
Transcript of LKNL12: Kanban for the whole value stream
Visualize the work – Kanban
for the whole value stream
@duarte_vasco and @lasseziegler
Tambako @ flickr
• Add buzzwords of failed models
V-Model
Rapid Software Development
Rational Unified Process
Chaotic development
FDD
DSDM
Spiral MOdel
Danisarda @ flickr
Ericcastro @ flickr
http://www.agilecollab.com/interview-with-ken-schwaber
Ken Schwaber: 75% of
organizations fail to benefit
from Agile/Scrum as expected
Cayusa @ flickr
Would you go back to the old way of working?
Large hardware + software company in nordics
NSN, presentation at JAOO/2010
Matley0 @ flickr
Act II – developing the action
Louish @ flickr
What is the biggest problem in
your organization?
Zenera @ flickr
• Overburdden or Muri
Topgold @ flickr
Skuds @ flickr
There’s a
bottleneck
in R&DHire more
peopleSalaries
here are
too high!
It is hard
and slow to
hire good
people
Work with
off-shore
and near-
shore
Communication
problems emerge
Travel and
communication
costs increase
Need to
spend time
with off-
shore
teams
And then we get faster
R&D!!! Oh wait...
Ma
rke
t
Here be
dragons
You are here You are here
(R&D / IT)
Here be
dragons
Ma
rket
1. Why do we have so many
features in the backlog?
2. What are the value stream
steps that we don’t know
about yet? Or don’t even
understand?
Ma
rke
t
Here be
dragons
You are here You are here
(R&D / IT)
Here be
dragons
Ma
rket
To do Doing Doneidea experiment valid
Pre-
prodcution Production
Revenue
generated
Ma
rke
t
Here be
dragons
You are here You are here
(R&D / IT)
Here be
dragons
Ma
rket
Fea
ture
s le
ft t
o c
om
ple
te
Time
Release date
Likely progress at current pace
Likely release date some
where there...
...
Company
acquired
Need to add
more features
Lack of scrutiny
by Product
Manager or
other
All new
features are
addedIncrease
pressure on
teams
<exercise for
the audience>
Make information about the
system visibile
... And that’s just the start...
Time
Fea
ture
s in
th
e B
ack
log
End of
strategy
cycle
End of
Roadmap
cycle End of
strategy
cycle
Stay tuned for an example...
Jduty @ flickr
<PDCA Concentric circles>
Papalars @ flickr
Gertcha @ flickr
Example 1: Why do we have so
little througput?
Stuff that is going on
Development
Stuff that is
going on
Stuff in
production
Where are all these projects
coming from?
Development
Stuff that is
going on
Stuff in
production
Development
Stuff that is
going on
Stuff in
production
Project
evaluation
Development
Stuff in
production
Project
evaluation
Wish
List
Production
Life-cycle
Development
Stuff in
production
Project
evaluation
Wish
List
Production
Life-cycle
Pro
du
ctio
nLi
ve M
ain
ten
an
ce
Example 2: The Feature Team
Development TestingQueue
Component A
Development Testing
Component B
Development Testing
Component A
Queue Development Testing
Component B
Development Testing
Feature Team
(A + B)
Queue
Development Testing
Feature Team
(A + B)
Post-production
Loca
liza
tio
nD
ocu
me
nta
tio
n
Queue
Example 3: What happens on the
Product Management part of the
chain?
Development Testing
Feature Team
(A + B)
Post-production
Loca
liza
tio
nD
ocu
me
nta
tio
n
Queue
MVP
Filtering
Validated
ideasT
he
CT
O p
oo
lA
cqu
isit
ion
/ In
teg
rati
on
Cu
sto
me
r
Re
qu
est
sDevelopment
This *was* the queue!
Example 5: Why do we get such a
big queue at specific intervals?
Development TestingQueue
Development Testing
Roadmap
Process
Output
Happens in Spring and Autumn
Development Testing
Roadmap
Process
Output
Happens in Spring and is
”reviewed” in Autumn
Strategy
Process
One more thing...
Newfrontiersmedia @ flickr
Act III – Turning point
Bazzadarambler @ flickr
Normanbleventhalmapcenter @ flickr
Zeptonn @ flickr
