• Save
Bp Meetup - Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking
Upcoming SlideShare
Loading in...5
×
 

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

on

  • 734 views

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

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

Statistics

Views

Total Views
734
Slideshare-icon Views on SlideShare
702
Embed Views
32

Actions

Likes
2
Downloads
0
Comments
0

4 Embeds 32

http://feeds2.feedburner.com 19
http://www.zsoltfabok.com 8
http://zsoltfabok.com 4
http://feeds.feedburner.com 1

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

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

    • Achieving Maintenance Stabilisation with Agile, Kanban and Lean Thinking by Zsolt Fabók@ZsoltFabok June 14th, 2012
    • The plan Talk Discussions Euro 2012
    • Flow
    • 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
    • Be careful when you are talking about optimizing the flow...
    • ...because there may be multiple flows!
    • Production Flow
    • Production Flow Maintenance Flow
    • Production Flowfeedback loop Maintenance Flow
    • Production Flow feedback loop Maintenance Flow
    • Production Flowfeedback loop Maintenance Flow
    • Production Flow
    • Optimize on the right flow!
    • 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~
    • 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Maintenance Flow
    • 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~
    • 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration
    • 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration Optimization
    • 3 4 2 Cloud Queue Reproduction Implementation Validation Live #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ #~ ~~ #~ #~ #~ ~~ #~ ~~ ~~ ~~# ~~ ~ #~~~ #~ ~~ #~ #~ ~~ #~ #~ ~~ ~~ ~~ ~~ #~ ~~ Collaboration Optimization Leadership
    • 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 Almost alwaysExpectations are clear Not always AlwaysCustomer contact Seldom Too oftenWill they be delivered Not always Most likely
    • 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 and future oriented daily meeting
    • 3 4 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 and future oriented daily meeting#4: Prioritize by cost of delay
    • 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
    • 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
    • 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
    • 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
    • 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 different versions
    • 3 4 2 Cloud Queue Reproduction Implementation Validation Live version 1.2 #~ #~ #~ #~ #~ #~ ~~ ~~ ~~ ~~ ~~ ~~#~~~ #~ ~~ #~ #~ #~ ~~# ~~ ~ ~~ #~ version 2.1~~ #~ #~ ~~ ~~ ~~ #~ #~ ~~ #~ ~~ ~~ #~ #~ ~~ #~ ~~ version 3.3 ~~
    • 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
    • 3 4 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 different versions#3: Introduce hot lane for expedite defects#4: After reproduction write a test case
    • 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
    • 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
    • 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, while thenew ones keep coming and coming and coming...”
    • Leadership Tips and Tricks#1: Keep the Cloud small and the Live large#2: Discuss problems right on the spot
    • 3 4 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 feedback to the other teams
    • 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
    • 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
    • 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
    • We are not quite done yet
    • Idea
    • A good idea makesa positive difference
    • If the idea is really good, people will follow you for sure Sasquatch music festival 2009
    • If the idea is really good, people will follow you for sure Sasquatch music festival 2009
    • If the idea is really good, people will follow you for sure Sasquatch music festival 2009
    • If the idea is really good, people will follow you for sure Sasquatch music festival 2009
    • If the idea is really good, people will follow you for sure Sasquatch music festival 2009
    • What if your idea doesn’tfit into the big picture?
    • Find this guy...... and prove him that your idea is really good!
    • Now, we are done ;-)
    • Thank you very much for your attention!http://zsoltfabok.com me@zsoltfabok.com
    • 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