Introduction of Kanban for large scale maintenance at mobile.international GmbH / OOP 2010
5 likes2,953 views
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.
Introduction of Kanban for large scale maintenance at mobile.international GmbH / OOP 2010
- 1. Kanban for large scale off-shored maintenance @ mobile.de January 26 2010 - Munich Feedback to mandrezak@team.mobile.de
- 2. feedback for all things Kanban at OOP 2010: #oopkanban
- 3. small bugs, small and medium features Photo by dolorix - http://鍖ic.kr/p/5mTAvT
- 4. national vs. international: dedicated team Photo 息 Nasa, visible earth
- 5. hard to manage, lots of WIP, hierarchical culture
- 6. cycle time = 28 days lead time = 52 days
- 7. you want half of these times? you have specialized teams? they are distributed?
- 9. Photo by john w - http://鍖ic.kr/p/8JcFA
- 10. 10 Photo 息 Sune Gynthersen, bestbrains.dk
- 12. Input Development QA Production Ongoing Done Ongoing Done
- 13. design of Kanban cards
- 14. tasks / stories are represented as cards
- 15. map cards to value stream on the wall
- 16. Input Deelopment QA Production Ongoing Done Ongoing Done
- 17. de鍖nition of Work-In-Progress-limits (WIP-Limits) & Pull
- 18. Input Development Acceptance Produktion 5 5 Ongoing Done Ongoing Done Pull Fixed WIP-Limits in relevant phases
- 19. de鍖nition of input and output-cadence
- 20. e.g. weekly prioritization e.g. bi-weekly releases Input Development Acceptance Production 5 5 Ongoing Done Ongoing Done Pull Fixed WIP limits for relevant phases
- 21. de鍖nition of done per phase and / or rules on pulling
- 22. Kanban cards visualize overall process state and clearly indicate bottlenecks in the process ---> basis for applying TOC and other bodies of production knowledge
- 23. Theory of Constraints (light) - Eliah Goldratt: identify bottleneck max. stress on bottleneck eliminate (or minimize) bottleneck Eliah Goldratt - The Goal
- 24. de鍖nition of WIP limits reduction of batch size reduction of lead time (Littles law)
- 25. Littles Law: lead time = WIP / throughput easy to change: discipline / hard to change: Flow mid term change process
- 26. estimations ---> calculation of cycle time and lead time
- 27. @
- 28. Maintenance - own track
- 29. why does Kanban match our requirements?
- 30. 遺鞄温壊庄稼! low visibility my project Lets try! Photo by Balakov - http://鍖ic.kr/p/6knucL
- 31. Things are slow I like it! Photo by Dunechaser - http://鍖ic.kr/p/JVEbT
- 33. frequent prioritization! -> weekly production incidents any time
- 34. Output Queue 鍖exibly coupled to release cycle and hot鍖xes
- 35. how did we implement it?
- 36. Photo by Dunechaser - http://鍖ic.kr/p/agZnC Semi-dictator style
- 39. Input Analyse Development QA Published Deployed 2 2 4 5 Ongoing Done Ongoing Done Ongoing Done
- 40. feature branches ! Photo by danorbit. - http://鍖ic.kr/p/3Lj2B9
- 41. training via Photo by pt - http://鍖ic.kr/p/VDDV
- 42. vacation :-( Photo by wili_hybrid - http://鍖ic.kr/p/56VmT7
- 43. QA doesnt join the 鍖ow Photo by fsudaft - http://鍖ic.kr/p/5DiUfn
- 44. not enough integration systems Photo by bobthemtnbiker - http://鍖ic.kr/p/5jpNpM
- 45. QA w/ limited availability -> buffer Photo by rev - http://鍖ic.kr/p/6HWEr3
- 46. Development QA Development ready f. QA QA 5 5 5 10 2 Ongoing Done Ongoing Done
- 47. 鍖ow! Photo by ViaMoi - http://鍖ic.kr/p/6qLxQz
- 48. Tools!
- 49. google docs spreadsheet ... greenhopper 4.0?
- 51. Cycle Time 28 30,0 24 22,5 15,0 8 7,5 august september 2 october 0 november 51
- 52. Lead Time (2-3 weekly releases) 52 60,0 45,0 28 30,0 22 15,0 august september 0 october 52
- 53. once Chaos now controlled
- 54. good mood in the team through 鍖ow experience
- 56. maintenance of whole platform from Jan 2010 w/ Kanban
- 57. heavy discussion with uninvolved great buy-in with those involved
- 58. 1PO 1 Technical Lead 7 developers 1 process guy
- 60. introduction of classes of service for production incidents required: expedite tickets to accomodate SLA
- 61. Thanks for your time and attention! contact: mandrezak@team.mobile.de twitter.com/markusandrezak slideshare.com/mandrezak
- 62. more on Kanban limitedwipsociety.org 02/2010 - 26. Feb 2010 5.3 - Thu 14:30 - 15:30 articles by Stefan Roock & Bernd Schiffer Stefan Roock & Was ist dran an Kaban Markus Andrezak Trainings w/ David Anderson it-agile.de feedback on all things kanban at #oop2010: #oopkanban