This document provides ideas for achieving maintenance stabilization using agile, Kanban and lean thinking. It discusses optimizing production and maintenance flows, collaboration ideas like treating defects like user stories, optimization ideas like using continuous integration and separate versions, and leadership ideas like keeping work in progress low and rotating staff between phases.

1. Achieving Maintenance Stabilisation with Agile,
Kanban and Lean Thinking
by
Zsolt Fabok
2012.09.27
@ZsoltFabok #agilecam
http://zsoltfabok.com/ http://www.agilecambridge.net/ac2012/

2. Flow

3. 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

4. Be careful when you are talking about
optimizing the flow...

5. ...because there may be multiple flows!

6. Production Flow
feedback loop
Maintenance Flow

7. Production Flow
feedback loop
Maintenance Flow

8. Production Flow
feedback loop
Maintenance Flow

9. Production Flow

10. Optimize on the right flow!

11. 3 4 2
Cloud Queue Reproduction Implementation Validation Live
#~ #~ #~ #~
#~ #~
~~ ~~ ~~ ~~
~~ ~~
#~
~~ #~
#~
~~ #~ #~ #~
~~
#~ ~~ ~~ ~~
# ~~ ~
#~
~~ #~
~~ #~ #~
~~ #~
#~ ~~ ~~ ~~
~~
#~
~~
Maintenance Flow

12. 3 4 2
Cloud Queue Reproduction Implementation Validation Live
#~ #~ #~ #~
#~ #~
~~ ~~ ~~ ~~
~~ ~~
#~
~~ #~
#~
~~ #~ #~ #~
~~
#~ ~~ ~~ ~~
# ~~ ~
#~
~~ #~
~~ #~ #~
~~ #~
#~ ~~ ~~ ~~
~~
#~
~~
Collaboration Optimization
Leadership

13. Collaboration Ideas

14. Collaboration Ideas
Defects aren't different from user stories

15. User story Defect
Has an owner Not always Always
Has a deadline Fuzzy, flexible Almost always
Expectations are clear Not always Always
Customer contact Seldom Too often
Will they be delivered Not always Most likely

16. Collaboration Ideas
Defects aren't different from user stories
Automatic data collection scripts

22. Collaboration Ideas
Defects aren't different from user stories
Automatic data collection scripts
Defect and future oriented daily meeting

23. 3 4 2
Cloud Queue Reproduction Implementation Validation Live
#~ #~ #~ #~
#~ #~
~~ ~~ ~~ ~~
~~
#~ ~~
~~ #~
#~
~~ #~ #~ #~
#~ ~~
~~ ~~ ~~
## ~ ~
~~
~~ ~ # ~
~
#~ #~ #~
#~ ~
~
~~ ~~ ~~
~~
#~
~~

24. Collaboration Ideas
Defects aren't different from user stories
Automatic data collection scripts
Defect and future oriented daily meeting
Prioritize by cost of delay

26. Collaboration Ideas
Defects aren't different from user stories
Automatic data collection scripts
Defect and future oriented daily meeting
Prioritize by cost of delay
Design discussion every afternoon

27. Collaboration Ideas
Defects aren't different from user stories
Automatic data collection scripts
Defect and future oriented daily meeting
Prioritize by cost of delay
Design discussion every afternoon
Write your own bug report

28. Collaboration Ideas
Defects aren't different from user stories
Automatic data collection scripts
Defect and future oriented daily meeting
Prioritize by cost of delay
Design discussion every afternoon
Write your own bug report
Use collaboration tools for communication

29. Collaboration Ideas
Defects aren't different from user stories
Automatic data collection scripts
Defect and future oriented daily meeting
Prioritize by cost of delay
Design discussion every afternoon
Write your own bug report
Use collaboration tools for communication
Throw away old defects

30. Optimization Ideas

31. Optimization Ideas
Use continuous integration and staging
environments

33. Optimization Ideas
Use continuous integration and staging
environments
Introduce separate swim lanes for different
versions

34. 3 4 2
Cloud Queue Reproduction Implementation Validation Live
version 1.2
#~ #~ #~
#~ #~ #~
~~ ~~ ~~
~~ ~~ ~~
#~
~~ #~
~~ #~
#~ #~
~~
# ~~ ~ ~~
#~
version 2.1
~~ #~ #~
~~
~~ ~~
#~ #~
~~ #~ ~~
~~
#~ #~
~~ #~ ~~
version 3.3
~~

35. Optimization Ideas
Use continuous integration and staging
environments
Introduce separate swim lanes for different
versions
Introduce hot lane for expedite defects

36. 3 4 2
Cloud Queue Reproduction Implementation Validation Live
hot
#~
#~ #~ ~~
~~ ~~
#~
~~ #~
~~ #~ #~
#~ ~~ #~
#~ ~~
# ~~ ~ ~~
#~ ~~
~~ #~ #~
~~
~~ #~ ~~
#~ ~~
~~
#~
~~ #~
#~
~~ ~~
#~
~~
#~
~~
#~
~~

37. Optimization Ideas
Use continuous integration and staging
environments
Introduce separate swim lanes for different
versions
Introduce hot lane for expedite defects
After reproduction write a test case

41. Optimization Ideas
Use continuous integration and staging
environments
Introduce separate swim lanes for different
versions
Introduce hot lane for expedite defects
After reproduction write a test case
Always have someone test your code

42. Optimization Ideas
Use continuous integration and staging
environments
Introduce separate swim lanes for different
versions
Introduce hot lane for expedite defects
After reproduction write a test case
Always have someone test your code
Measure and improve the flow

43. Leadership Ideas

44. Leadership Ideas
Keep the Cloud small and the Live large

45. A retrospective comment:
“Zsolt, can we keep the finished defects on
the board? I feel better when I see how
much we finished, while the new ones keep
coming and coming and coming...”

46. Leadership Ideas
Keep the Cloud small and the Live large
Discuss problems right on the spot

47. 3 4 2
Cloud Queue Reproduction Implementation Validation Live
#~ #~ #~
#~ #~ #~
~~ ~~ ~~
~~ ~~ ~~
#~
~~ #~
~~ #~
#~ #~
#~ ~~
~~ ~~
# ~~ ~
#~
~~ #~
~~ #~
~~ #~
#~ ~~ ~~
~~
#~
~~ #~
~~ #~
~~

48. Leadership Ideas
Keep the Cloud small and the Live large
Discuss problems right on the spot
Provide feedback to the other teams

49. Leadership Ideas
Keep the Cloud small and the Live large
Discuss problems right on the spot
Provide feedback to the other teams
Rotate people between phases

50. Leadership Ideas
Keep the Cloud small and the Live large
Discuss problems right on the spot
Provide feedback to the other teams
Rotate people between phases
Weekly face-to-face with everybody

51. Leadership Ideas
Keep the Cloud small and the Live large
Discuss problems right on the spot
Provide feedback to the other teams
Rotate people between phases
Weekly face-to-face with everybody
Turn off notifications - email, issue tracker

52. We are not quite done yet

53. Idea

54. A good idea makes
a positive difference

55. If your idea is really good, people will follow you
sasquatch music festival 2009

56. What if your idea doesn’t fit into the big picture?

57. Then find this guy...
... and prove him that
your idea is really good!

58. Now, we are done ;-)

59. Thank you very much for your attention!
http://zsoltfabok.com/ @ZsoltFabok

60. Sources of the used images:
leaders on the field:
http://carterkellyconsulting.com/lifepoint_leadervisionspirit
factory floor:
http://www.copters.com/trips/rhc2006.html
Miners:
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-
Patterns
Cost of delay:
http://agileconsulting.blogspot.com/2011/03/using-cost-of-
delay-functions-to.html