DevOps - Ten tips for developers
by evanbottcher on Sep 14, 2010
- 2,217 views
Presented at ThoughtWorks Australia 2010 'Team Hug' (Away day). Ten tips for developers who want to make closer friendships with the IT operations team.
Presented at ThoughtWorks Australia 2010 'Team Hug' (Away day). Ten tips for developers who want to make closer friendships with the IT operations team.
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 0
- Downloads
- 0
- Comments
- 0
- Embed Views
- Views on SlideShare
- 971
- Total Views
- 2,217
That’s the enterprise architect in the background - he’s arguing for fully redundant light sabers.
This is accentuated by physical separation, reliance on ticketing systems and approval bureacracy
Sometimes no matter what we do, it seems to be wrong. We get told what we *should* have done, and always when it’s too late.
traditional thinking: ops task is to keep systems stable and fast. dev’s task is to deliver features quickly. This pushes down from CIOs to operations managers and app development managers, down into KRAs.
According to the itSMF (IT Service Management Forum), 80% of incidents are caused by changes made to the IT environment.
Ops are almost always understaffed, and under constant interuption - everybody’s problem is the biggest problem in the world. Defensive measures are put in place to help the ops team deal with this problem.
Important to understand - until you can understand from their perspective, you can’t influence.
may not be able to change (yet) but don’t presume people are ignorant or evil.
retros, problem analysis (5 whys)
Use ‘we’. Invite ops to standups and retros - every time. Invite ops to lunch, functions etc.
take the time to follow up with ops to explain the outcomes of things
forgive eccentricity
pairing? work on things together. That means you helping, too!
promote your ops team members within their own organisation
don’t accept manual work - help automate if you can
However - follow up with tickets if required.
Make sure Ops is represented with ‘stories’ “As a sysadmin”. Logging is a user interface. Make sure the right things are monitored - and monitorable! Stop building systems that are black box and require magic incantations and sacrifices.
shared metrics and monitoring. can you mine the service desk’s ticketing reports?
- no hollow promises
- covey's emotional bank account - invest!
- fix things! follow through with root cause analysis
don’t be afraid to ask for help, or to ‘pair’ on a problem.