Achieving Maintenance Stabilisation with Agile, Kanban and Lean                           Thinking                        ...
Myth #1: “There is no place for Agile in           maintenance!”
Myth #2: “Maintenance is not a team              work!”
Myth #3: “Maintenance work cannot be             improved!”
The proof that these myths are wrong:                             Before*                                                 ...
Introducing Kanban and visualizing the workflow...
3               2 Cloud         Queue Reproduction Implementation   Validation   Live                          #~         ...
3               2 Cloud         Queue Reproduction Implementation   Validation   Live                          #~         ...
3               2 Cloud         Queue Reproduction Implementation   Validation   Live                          #~         ...
3               2 Cloud         Queue Reproduction Implementation   Validation   Live                          #~         ...
3               2 Cloud         Queue Reproduction Implementation   Validation   Live                          #~         ...
Collaboration Tips and Tricks
Collaboration Tips and Tricks#1: Defects arent different from user stories
User story         DefectHas an owner              Not always         AlwaysHas a deadline           Fuzzy, flexible   Almo...
Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts
Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect ...
3               2  Cloud       Queue   Reproduction   Implementation   Validation   Live                         #~       ...
Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect ...
Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect ...
Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect ...
Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect ...
Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect ...
Optimization Tips and Tricks
Optimization Tips and Tricks#1: Use continuous integration and staging environment
Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for di...
3                    2 Cloud         Queue Reproduction Implementation        Validation   Live                     versio...
Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for di...
3               2 Cloud         Queue Reproduction Implementation   Validation   Live                      hot            ...
Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for di...
Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for di...
Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for di...
Leadership Tips and Tricks
Leadership Tips and Tricks#1: Keep the Cloud small and the Live large
A retrospective comment:“Zsolt, can we keep the finished defects on the board? Ifeel better when I see how much we finished,...
Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot
3                2 Cloud         Queue Reproduction Implementation    Validation   Live                                   ...
Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot#3: Provide fee...
Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot#3: Provide fee...
Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot#3: Provide fee...
Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot#3: Provide fee...
Thank you very much for your attention!http://zsoltfabok.com      zsolt.fabok@ericsson.com
Sources of ussd images:leaders on the field:   http://carterkellyconsulting.com/lifepoint_leadervisionspirit factory floor: ...
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Upcoming SlideShare
Loading in …5
×

Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking

1,309 views

Published on

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

No Downloads
Views
Total views
1,309
On SlideShare
0
From Embeds
0
Number of Embeds
160
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

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 March 20, 2012
  2. 2. Myth #1: “There is no place for Agile in maintenance!”
  3. 3. Myth #2: “Maintenance is not a team work!”
  4. 4. Myth #3: “Maintenance work cannot be improved!”
  5. 5. The proof that these myths are wrong: Before* After* # ID description Defects received in 9 21 a week Number of days to fix a defect 11 6 (avg. lead time)* due to confidentiality reasons the numbers have been altered, but the ratio is still valid
  6. 6. Introducing Kanban and visualizing the workflow...
  7. 7. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~
  8. 8. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~
  9. 9. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration
  10. 10. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration Optimization
  11. 11. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration Optimization Leadership
  12. 12. Collaboration Tips and Tricks
  13. 13. Collaboration Tips and Tricks#1: Defects arent different from user stories
  14. 14. 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
  15. 15. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts
  16. 16. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts#3: Defect and future oriented daily meeting
  17. 17. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ #~ ~~ ~~ #~ #~ ~~ #~ #~ #~ #~ ~~ ~~ ~~ ~~## ~ ~ ~~~~ ~ # ~ ~ #~ #~ #~ #~ ~ ~ ~~ ~~ ~~ ~~ #~ ~~
  18. 18. 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
  19. 19. 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
  20. 20. 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
  21. 21. 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
  22. 22. 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
  23. 23. Optimization Tips and Tricks
  24. 24. Optimization Tips and Tricks#1: Use continuous integration and staging environment
  25. 25. Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for different versions
  26. 26. 3 2 Cloud Queue Reproduction Implementation Validation Live version 1.2 #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ ~~# ~~ ~ ~~ #~ version 2.1~~ #~ #~ ~~ ~~ ~~ #~ #~ ~~ #~ ~~ ~~ #~ #~ ~~ #~ ~~ version 3.3 ~~
  27. 27. 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
  28. 28. 3 2 Cloud Queue Reproduction Implementation Validation Live hot #~ #~ #~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ ~~ #~ #~ ~~# ~~ ~ ~~ #~ ~~~~ #~ #~ ~~ ~~ #~ ~~ #~ ~~ ~~ #~ ~~ #~ #~ ~~ ~~ #~ ~~ #~ ~~
  29. 29. 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
  30. 30. 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: Never test your own code
  31. 31. 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: Never test your own code#6: Measure everything, and improve everywhere
  32. 32. Leadership Tips and Tricks
  33. 33. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large
  34. 34. 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...”
  35. 35. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot
  36. 36. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ ~~ #~ #~ ~~ ~~ ~~ #~ ~~ #~ ~~ #~ ~~
  37. 37. 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
  38. 38. 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
  39. 39. 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
  40. 40. 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
  41. 41. Thank you very much for your attention!http://zsoltfabok.com zsolt.fabok@ericsson.com
  42. 42. Sources of ussd 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

×