Maintenance Stabilisation


Published on

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Maintenance Stabilisation

  1. 1. Maintenance Stabilisation kaizen WIP kaikaku flow value stream mapping visualize work flow cycle time lead time throughput TPS build failed CFDcreated byZsolt Fabó October 25, 2011 @twitter: @ZsoltFabok evoline, Cluj Napoca, RO
  2. 2. reference:
  3. 3. Two myths about maintenance andKanban:"Maintenance cannot be done with teams.""Kanban is designed for Maintenance." Fortunately, both of them are wrong!
  4. 4. A possible workflow for a maintenance team
  5. 5. Improvement approaches Collaboration Optimisation (more Agile) (more Lean)
  6. 6. Collaboration Tips and Tricks (Agile techniques)
  7. 7. Defects arent different from tasks, userstories or work items ● Easier to handle and manage teams ● Maintenance is not a punishment ● Methods/frameworks fit better
  8. 8. Data collector script ● [semi] automatic ● No more arguments over missing log files ● Collects what the team needs
  9. 9. Different daily stand-up with managers: ● task oriented ● talk about new defects ● prioritisation for each column ● transparency ● faster reaction time ● spending time on work items which really matter
  10. 10. Prioritise by ● business value ● cost of delay ● service level agreement (SLA) ● actual resource availability ● current capacity and loadphoto:
  11. 11. Design discussion every afternoon ● follow up the ideas from the stand-up ● technical help on the investigations ● two heads are better than one
  12. 12. Write your own bug reports ● easier to close them ● external findings are duplicates ● they will be filled out correctly
  13. 13. Communicate through mailing lists ● archived, searchable ● everybody can see, contribute ● no more annoying direct contact from bug reporters
  14. 14. Mentor and coach other teams ● give them feedback on their work (they may have introduced the defects) ● improve current processes in order to have less defects later
  15. 15. Keep the size of the Cloud small, and theLive large ● large Cloud is really demotivating ● takes too much time to review a large Cloud ● large Live is really motivating (+ managers like it better)
  16. 16. Throw away old defects ● dont bother with old (more than half a year) defects. If they are still necessary, someone will write you a mail. If not, it wasnt that necessary
  17. 17. Optimisation Tips and Tricks (Lean techniques)
  18. 18. Have continuous integration, staging machine and continuous delivery ● packaging and regression problems will be discovered sooner ● failed build immediately indicates a problemphoto:
  19. 19. Use swim lanes for different tracks
  20. 20. Use a hot lane for expedite items
  21. 21. After reproduction, write a test case ● reproducible -> testable ● if another fix broke this fix it will be visible immediately ● much faster integration and delivery
  22. 22. You cannot test what you code yourself,always have somebody else do it ● improves verification ● distributes knowledge (test and domain) ● less work items will be rejected at validation
  23. 23. Measure everything, really everything ● lead time -> how much time we need to fix a defect ● cycle time -> where can we improve ● capability + lead time + inflow -> helps estimation
  24. 24. Collaboration and Optimisation Tips and Tricks (Leadership techniques)photo:
  25. 25. Do not wait with the retrospective, do it onthe spot ● maintenance is continuous, regular scheduled meetings arent effective ● people forget things very fast ● empowers Lean thinking
  26. 26. Rotate people between Reproduction andother phases ● it is demotivating to do only one thing ● team members can hide ● feedback loop
  27. 27. Talk to team members face to face on aweekly basis ● maintenance is not motivating, people open up better in a face-to-face meeting than in front of the group ● prevent unnecessary fluctution
  28. 28. Turn of the issue/defect notification emails ● dont let the system interrupt your work ● implement a pull system for your own
  29. 29. Thank you very much for your attention! For more check out my website: or follow me on RSS: blog/?feed=rss2 and Twitter: @ZsoltFabok