Your SlideShare is downloading. ×
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
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
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
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
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
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking

979

Published on

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

No Downloads
Views
Total Views
979
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking by Zsolt Fabók@ZsoltFabok March 20, 2012
  • 2. Myth #1: “There is no place for Agile in maintenance!”
  • 3. Myth #2: “Maintenance is not a team work!”
  • 4. Myth #3: “Maintenance work cannot be improved!”
  • 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. Introducing Kanban and visualizing the workflow...
  • 7. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~
  • 8. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~
  • 9. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration
  • 10. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration Optimization
  • 11. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration Optimization Leadership
  • 12. Collaboration Tips and Tricks
  • 13. Collaboration Tips and Tricks#1: Defects arent different from user stories
  • 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. Collaboration Tips and Tricks#1: Defects arent different from user stories#2: Automatic data collection scripts
  • 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. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ #~ ~~ ~~ #~ #~ ~~ #~ #~ #~ #~ ~~ ~~ ~~ ~~## ~ ~ ~~~~ ~ # ~ ~ #~ #~ #~ #~ ~ ~ ~~ ~~ ~~ ~~ #~ ~~
  • 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. 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. 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. 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. 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. Optimization Tips and Tricks
  • 24. Optimization Tips and Tricks#1: Use continuous integration and staging environment
  • 25. Optimization Tips and Tricks#1: Use continuous integration and staging environment#2: Introduce separate swim lanes for different versions
  • 26. 3 2 Cloud Queue Reproduction Implementation Validation Live version 1.2 #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ ~~# ~~ ~ ~~ #~ version 2.1~~ #~ #~ ~~ ~~ ~~ #~ #~ ~~ #~ ~~ ~~ #~ #~ ~~ #~ ~~ version 3.3 ~~
  • 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. 3 2 Cloud Queue Reproduction Implementation Validation Live hot #~ #~ #~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ ~~ #~ #~ ~~# ~~ ~ ~~ #~ ~~~~ #~ #~ ~~ ~~ #~ ~~ #~ ~~ ~~ #~ ~~ #~ #~ ~~ ~~ #~ ~~ #~ ~~
  • 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. 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. 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. Leadership Tips and Tricks
  • 33. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large
  • 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. Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot
  • 36. 3 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ ~~ #~ #~ ~~ ~~ ~~ #~ ~~ #~ ~~ #~ ~~
  • 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. 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. 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. 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. Thank you very much for your attention!http://zsoltfabok.com zsolt.fabok@ericsson.com
  • 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

×