Bp Meetup - Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking

799 views
714 views

Published on

My slides from the 12th event of the Budapest Lean Kanban Meetup Group.

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
799
On SlideShare
0
From Embeds
0
Number of Embeds
32
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Bp Meetup - Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking

  1. 1. Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking by Zsolt Fabók@ZsoltFabok June 14th, 2012
  2. 2. The plan Talk Discussions Euro 2012
  3. 3. Flow
  4. 4. Production Flow: “The movement of the products within the shop during each stage of the parts manufacturing process”http://www.toolingu.com/definition-900130-12169-product-flow.html
  5. 5. Be careful when you are talking about optimizing the flow...
  6. 6. ...because there may be multiple flows!
  7. 7. Production Flow
  8. 8. Production Flow Maintenance Flow
  9. 9. Production Flowfeedback loop Maintenance Flow
  10. 10. Production Flow feedback loop Maintenance Flow
  11. 11. Production Flowfeedback loop Maintenance Flow
  12. 12. Production Flow
  13. 13. Optimize on the right flow!
  14. 14. 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~
  15. 15. 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Maintenance Flow
  16. 16. 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~
  17. 17. 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration
  18. 18. 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration Optimization
  19. 19. 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration Optimization Leadership
  20. 20. Collaboration Tips and Tricks
  21. 21. Collaboration Tips and Tricks#1: Defects arent different from user stories
  22. 22. User story DefectHas an owner Not always AlwaysHas a deadline Fuzzy, flexible Almost alwaysExpectations are clear Not always AlwaysCustomer contact Seldom Too oftenWill they be delivered Not always Most likely
  23. 23. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts
  24. 24. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect and future oriented daily meeting
  25. 25. 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ #~ ~~ ~~ #~ #~ ~~ #~ #~ #~ #~ ~~ ~~ ~~ ~~## ~ ~ ~~~~ ~ # ~ ~ #~ #~ #~ #~ ~ ~ ~~ ~~ ~~ ~~ #~ ~~
  26. 26. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect and future oriented daily meeting#4: Prioritize by cost of delay
  27. 27. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect and future oriented daily meeting#4: Prioritize by cost of delay#5: Design discussion every afternoon
  28. 28. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect and future oriented daily meeting#4: Prioritize by cost of delay#5: Design discussion every afternoon#6: Write your own bug report
  29. 29. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect and future oriented daily meeting#4: Prioritize by cost of delay#5: Design discussion every afternoon#6: Write your own bug report#7: Use collaboration tools for communication
  30. 30. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect and future oriented daily meeting#4: Prioritize by cost of delay#5: Design discussion every afternoon#6: Write your own bug report#7: Use collaboration tools for communication#8: Throw away old defects
  31. 31. Optimization Tips and Tricks
  32. 32. Optimization Tips and Tricks#1: Use continuous integration and staging environment
  33. 33. Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for different versions
  34. 34. 3 4 2 Cloud Queue Reproduction Implementation Validation Live version 1.2 #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ ~~# ~~ ~ ~~ #~ version 2.1~~ #~ #~ ~~ ~~ ~~ #~ #~ ~~ #~ ~~ ~~ #~ #~ ~~ #~ ~~ version 3.3 ~~
  35. 35. Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for different versions#3: Introduce hot lane for expedite defects
  36. 36. 3 4 2 Cloud Queue Reproduction Implementation Validation Live hot #~ #~ #~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ ~~ #~ #~ ~~# ~~ ~ ~~ #~ ~~~~ #~ #~ ~~ ~~ #~ ~~ #~ ~~ ~~ #~ ~~ #~ #~ ~~ ~~ #~ ~~ #~ ~~ #~ ~~
  37. 37. Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for different versions#3: Introduce hot lane for expedite defects#4: After reproduction write a test case
  38. 38. Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for different versions#3: Introduce hot lane for expedite defects#4: After reproduction write a test case#5: Always have someone test your code
  39. 39. Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for different versions#3: Introduce hot lane for expedite defects#4: After reproduction write a test case#5: Always have someone test your code#6: Measure and improve the flow
  40. 40. Leadership Tips and Tricks
  41. 41. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large
  42. 42. A retrospective comment:“Zsolt, can we keep the finished defects on the board? Ifeel better when I see how much we finished, while thenew ones keep coming and coming and coming...”
  43. 43. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot
  44. 44. 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ ~~ #~ #~ ~~ ~~ ~~ #~ ~~ #~ ~~ #~ ~~
  45. 45. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot#3: Provide feedback to the other teams
  46. 46. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot#3: Provide feedback to the other teams#4: Rotate people between phases
  47. 47. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot#3: Provide feedback to the other teams#4: Rotate people between phases#5: Weekly face-to-face with everybody
  48. 48. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot#3: Provide feedback to the other teams#4: Rotate people between phases#5: Weekly face-to-face with everybody#6: Turn off notifications - email, issue tracker
  49. 49. We are not quite done yet
  50. 50. Idea
  51. 51. A good idea makesa positive difference
  52. 52. If the idea is really good, people will follow you for sure Sasquatch music festival 2009
  53. 53. If the idea is really good, people will follow you for sure Sasquatch music festival 2009
  54. 54. If the idea is really good, people will follow you for sure Sasquatch music festival 2009
  55. 55. If the idea is really good, people will follow you for sure Sasquatch music festival 2009
  56. 56. If the idea is really good, people will follow you for sure Sasquatch music festival 2009
  57. 57. What if your idea doesn’tfit into the big picture?
  58. 58. Find this guy...... and prove him that your idea is really good!
  59. 59. Now, we are done ;-)
  60. 60. Thank you very much for your attention!http://zsoltfabok.com me@zsoltfabok.com
  61. 61. Sources of the used images:leaders on the field: http://carterkellyconsulting.com/lifepoint_leadervisionspirit factory floor: http://www.copters.com/trips/rhc2006.htmlMiners: http://www.foreignpolicy.com/articles/2010/05/18/ the_coal_miners_burden?page=ful hipchat: http://blogs.atlassian.com/2012/03/meet-hipchat-the-newest- member-of-the-atlassian-family/Continuous delivery: http://www.infoq.com/articles/Continous-Delivery- PatternsCost of delay: http://agileconsulting.blogspot.com/2011/03/using-cost- of-delay-functions-to.html

×