introduction of kanban for large scale maintenance at mobile.international gmbh / oop 2010
DESCRIPTION
Presentation on the introduction of Kanban as the Maintenance process for the mobile.international GmbH products. Key messages: Good, flexible agile process for maintenance. Suitable also for teams not that experienced in agile, as it picks up the teams where they are and leads to continous improvement and maturity. Great reduction of cycle and lead time in short time frame after introduction.TRANSCRIPT
Kanban for large scale off-shored maintenance @ mobile.de
January 26 2010 - Munich
Feedback to [email protected]
feedback for all things Kanban at OOP 2010:
#oopkanban
small bugs, small and medium features
Photo by dolorix - http://flic.kr/p/5mTAvT
Photo © Nasa, visible earth
national vs. international:dedicated team
hard to manage, lots of WIP, hierarchical culture
cycle time = 28 dayslead time = 52 days
you want half of these times?
you have specialized teams?
they are distributed?
Enter Kanban!
(signal card)
10 Photo © Sune Gynthersen, bestbrains.dk
value stream mapping
Input DevelopmentDevelopment QAQA Production
Ongoing Done Ongoing Done
design of Kanban cards
tasks / stories are represented as cards
map cards to value stream on the wall
Input DeelopmentDeelopment QAQA Production
Ongoing Done Ongoing Done
definition of Work-In-Progress-limits (WIP-Limits)
& Pull
Input DevelopmentDevelopment AcceptanceAcceptance Produktion
55 55
Ongoing Done Ongoing Done
Fixed WIP-Limits in relevant phases
Pull
definition of input and output-cadence
Input DevelopmentDevelopment AcceptanceAcceptance Production
55 55
Ongoing Done Ongoing Done
Fixed WIP limits for relevant phases
Pull
e.g. weekly prioritization e.g. bi-weekly releases
definition of done per phase and / or rules on pulling
Kanban cards visualize overall process state and clearly indicate bottlenecks in the
process
---> basis for applying TOCand other bodies of production knowledge
Theory of Constraints (light) - Eliah Goldratt:
identify bottleneck
max. stress on bottleneck eliminate (or minimize) bottleneck
Eliah Goldratt - „The Goal“
definition of WIP limits
≈ reduction of batch size
≈ reduction of lead time
(Little‘s law)
Little‘s Law:
lead time = WIP / throughput
easy to change: discipline / Flow
hard to change:mid term change process
estimations
---> calculation of
cycle time and lead time
@
Maintenance - own track
why does Kanban match our requirements?
Photo by Balakov - http://flic.kr/p/6knucL
Let‘s try!my project
low visibilityChasin‘!
Photo by Dunechaser - http://flic.kr/p/JVEbT
I like it!Things
are slow
estimations not required
frequent prioritization!-> weekly
production incidents any time
Output Queue flexibly coupled to release cycle and hotfixes
how did we implement it?
Semi-dictator style
Photo by Dunechaser - http://flic.kr/p/agZnC
I wanted desperately
first process draft
Input AnalyseAnalyseAnalyse DevelopmentDevelopment QAQA Published Deployed
2 22 44 55
OngoingOngoing Done Ongoing Done Ongoing Done
feature branches ! Photo by danorbit. - http://flic.kr/p/3Lj2B9
vacation :-(
Photo by wili_hybrid - http://flic.kr/p/56VmT7
QA „doesn‘t join“ the flow
Photo by fsudaft - http://flic.kr/p/5DiUfn
not enough integration systems
Photo by bobthemtnbiker - http://flic.kr/p/5jpNpM
QA w/ limited availability -> buffer
Photo by rev - http://flic.kr/p/6HWEr3
Development QA
5 5
Ongoing Done
Development ready f. QA QA
5 10 2
Ongoing Done
Tools!
google docs spreadsheet ...
greenhopper 4.0?
enter: sucess, results
51
0
7,5
15,0
22,5
30,028
24
8
2august
septemberoctober
november
Cycle Time
52
0
15,0
30,0
45,0
60,052
28
22
augustseptember
october
Lead Time (2-3 weekly releases)
once Chaos
now controlled
good mood in the team through flow experience
great communication tool
maintenance of whole platform from Jan 2010 w/ Kanban
heavy discussion with uninvolved
great buy-in with those involved
1PO1 Technical
Lead1 process guy
7 developers
Kanban adjustments required
introduction of classes of service for production incidents required:
expedite tickets
to accomodate SLA
Thanks for your time and attention!
contact: [email protected]
twitter.com/markusandrezakslideshare.com/mandrezak
more on Kanban
5.3 - Thu 14:30 - 15:30Stefan Roock & Bernd Schiffer
„Was ist dran an Kaban“
articles by Stefan Roock &
Markus Andrezak
02/2010 - 26. Feb 2010
limitedwipsociety.org
Trainings w/ David Anderson
it-agile.de
feedback on all things kanban at #oop2010:
#oopkanban