maintenance stabilisation
DESCRIPTION
TRANSCRIPT
Maintenance Stabilisation
created byZsolt Fabó[email protected]: @ZsoltFabok
October 25, 2011 @evoline, Cluj Napoca, RO
kaizen WIP kaikaku flow value
stream mapping visualize work flow cycle time lead time throughput TPS build failed CFD
reference: http://alistair.cockburn.us/Oath+of+Non-Allegiance
Two myths about maintenance and Kanban:
"Maintenance cannot be done with teams."
"Kanban is designed for Maintenance."
Fortunately, both of them are wrong!
A possible workflow for a maintenance team
Collaboration(more Agile)
Optimisation(more Lean)
Improvement approaches
Collaboration Tips and Tricks(Agile techniques)
Defects aren't different from tasks, user stories or work items
● Easier to handle and manage teams● Maintenance is not a punishment● Methods/frameworks fit better
Data collector script
● [semi] automatic● No more arguments over missing log files● Collects what the team needs
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
Prioritise by
● business value● cost of delay
● service level agreement (SLA)● actual resource availability● current capacity and load
photo: http://agileconsulting.blogspot.com/2011/03/using-cost-of-delay-functions-to.html
Design discussion every afternoon
● follow up the ideas from the stand-up● technical help on the investigations● two heads are better than one
Write your own bug reports
● easier to close them● external findings are duplicates● they will be filled out correctly
Communicate through mailing lists
● archived, searchable● everybody can see, contribute● no more annoying direct contact from bug
reporters
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
Keep the size of the Cloud small, and the Live large
● large Cloud is really demotivating● takes too much time to review a large Cloud● large Live is really motivating (+ managers like it
better)
Throw away old defects
● don't bother with old (more than half a year) defects. If they are still necessary, someone will write you a mail. If not, it wasn't that necessary
Optimisation Tips and Tricks(Lean techniques)
Have continuous integration, staging machine and continuous delivery
● packaging and regression problems will be discovered sooner
● failed build immediately indicates a problem
photo: http://www.infoq.com/articles/Continous-Delivery-Patterns
Use swim lanes for different tracks
Use a hot lane for expedite items
After reproduction, write a test case
● reproducible -> testable● if another fix broke this fix it will be visible immediately● much faster integration and delivery
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
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
Collaboration and Optimisation Tips and Tricks
(Leadership techniques)
photo: http://carterkellyconsulting.com/lifepoint_leadervisionspirit
Do not wait with the retrospective, do it on the spot
● maintenance is continuous, regular scheduled meetings aren't effective
● people forget things very fast● empowers Lean thinking
Rotate people between Reproduction and other phases
● it is demotivating to do only one thing● team members can hide● feedback loop
Talk to team members face to face on a weekly basis
● maintenance is not motivating, people open up better in a face-to-face meeting than in front of the group
● prevent unnecessary fluctution
Turn of the issue/defect notification emails
● don't let the system interrupt your work● implement a pull system for your own
Thank you very much for your attention!
For more check out my website:http://zsoltfabok.com/
or follow me on RSS:http://www.zsoltfabok.com/blog/?feed=rss2
and Twitter:@ZsoltFabok