Introduction of Kanban for large scale maintenance at mobile.international GmbH / OOP 2010

4,612 views

Published on

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. 1. Kanban for large scale off-shored maintenance @ mobile.de January 26 2010 - Munich Feedback to mandrezak@team.mobile.de
  2. 2. feedback for all things Kanban at OOP 2010: #oopkanban
  3. 3. small bugs, small and medium features Photo by dolorix - http://flic.kr/p/5mTAvT
  4. 4. national vs. international: dedicated team Photo © Nasa, visible earth
  5. 5. hard to manage, lots of WIP, hierarchical culture
  6. 6. cycle time = 28 days lead time = 52 days
  7. 7. you want half of these times? you have specialized teams? they are distributed?
  8. 8. Enter Kanban! (signal card)
  9. 9. Photo by john w - http://flic.kr/p/8JcFA
  10. 10. 10 Photo © Sune Gynthersen, bestbrains.dk
  11. 11. value stream mapping
  12. 12. Input Development QA Production Ongoing Done Ongoing Done
  13. 13. design of Kanban cards
  14. 14. tasks / stories are represented as cards
  15. 15. map cards to value stream on the wall
  16. 16. Input Deelopment QA Production Ongoing Done Ongoing Done
  17. 17. definition of Work-In-Progress-limits (WIP-Limits) & Pull
  18. 18. Input Development Acceptance Produktion 5 5 Ongoing Done Ongoing Done Pull Fixed WIP-Limits in relevant phases
  19. 19. definition of input and output-cadence
  20. 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. 21. definition of done per phase and / or rules on pulling
  22. 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. 23. Theory of Constraints (light) - Eliah Goldratt: identify bottleneck max. stress on bottleneck eliminate (or minimize) bottleneck Eliah Goldratt - „The Goal“
  24. 24. definition of WIP limits ≈ reduction of batch size ≈ reduction of lead time (Little‘s law)
  25. 25. Little‘s Law: lead time = WIP / throughput easy to change: discipline / hard to change: Flow mid term change process
  26. 26. estimations ---> calculation of cycle time and lead time
  27. 27. @
  28. 28. Maintenance - own track
  29. 29. why does Kanban match our requirements?
  30. 30. Chasin‘! low visibility my project Let‘s try! Photo by Balakov - http://flic.kr/p/6knucL
  31. 31. Things are slow I like it! Photo by Dunechaser - http://flic.kr/p/JVEbT
  32. 32. estimations not required
  33. 33. frequent prioritization! -> weekly production incidents any time
  34. 34. Output Queue flexibly coupled to release cycle and hotfixes
  35. 35. how did we implement it?
  36. 36. Photo by Dunechaser - http://flic.kr/p/agZnC Semi-dictator style
  37. 37. I wanted desperately
  38. 38. first process draft
  39. 39. Input Analyse Development QA Published Deployed 2 2 4 5 Ongoing Done Ongoing Done Ongoing Done
  40. 40. feature branches ! Photo by danorbit. - http://flic.kr/p/3Lj2B9
  41. 41. training via Photo by pt - http://flic.kr/p/VDDV
  42. 42. vacation :-( Photo by wili_hybrid - http://flic.kr/p/56VmT7
  43. 43. QA „doesn‘t join“ the flow Photo by fsudaft - http://flic.kr/p/5DiUfn
  44. 44. not enough integration systems Photo by bobthemtnbiker - http://flic.kr/p/5jpNpM
  45. 45. QA w/ limited availability -> buffer Photo by rev - http://flic.kr/p/6HWEr3
  46. 46. Development QA Development ready f. QA QA 5 5 5 10 2 Ongoing Done Ongoing Done
  47. 47. flow! Photo by ViaMoi - http://flic.kr/p/6qLxQz
  48. 48. Tools!
  49. 49. google docs spreadsheet ... greenhopper 4.0?
  50. 50. enter: sucess, results
  51. 51. Cycle Time 28 30,0 24 22,5 15,0 8 7,5 august september 2 october 0 november 51
  52. 52. Lead Time (2-3 weekly releases) 52 60,0 45,0 28 30,0 22 15,0 august september 0 october 52
  53. 53. once Chaos now controlled
  54. 54. good mood in the team through flow experience
  55. 55. great communication tool
  56. 56. maintenance of whole platform from Jan 2010 w/ Kanban
  57. 57. heavy discussion with uninvolved great buy-in with those involved
  58. 58. 1PO 1 Technical Lead 7 developers 1 process guy
  59. 59. Kanban adjustments required
  60. 60. introduction of classes of service for production incidents required: expedite tickets to accomodate SLA
  61. 61. Thanks for your time and attention! contact: mandrezak@team.mobile.de twitter.com/markusandrezak slideshare.com/mandrezak
  62. 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

×