devops counselling
TRANSCRIPT
TOM SULSTON
http://thoughtworks.com@tomsulston
DevOps CounsellingOr: How to help your developers and sysadmins
learn to love each other (again)
Counselling?
Most problems are
non-technical
Helpfulness
Common purpose
Sharing
Rich communication
Technical rigour
Values
Top Ten Tips
Continuous Integration then Continuous Delivery
Good analysis & stories.
Iterative development + deployment
Bigger fish to fry
Automated testing
Agile development
Have open channels
Communication as a factor of distance
Make time to talk
Talk to individuals
Sit together
‘irrelevant’ learning
Don’t create knowledge silos
Build special interest groups
Exploit Conway’s Law
Knowledge-sharing
Don’t have big central services teams
Give individuals time to work in their area
Reduce silo’d work
Don’t tear down the silos (yet!)
Reduce hand-offs
Similar reporting for whole team
Small number of hops
Value-stream mapping
Management structure
Reward everyone fairly
Are your incentives helping or hurting?
Focus on delivery
Don’t get gamed
Incentives
Be thoughtful
Come on!
Include everyone
Celebrate failure
Celebrate good times!
laughingsquid.com
Use tests rather than restricting access
Everyone has RW to Puppet/Chef
Share the pain when breakages happen
Pair to overcome mistrust
Share access to systems
You are not in the sudoers file. This incident will be reported.
Big visible displays
Developers should see into production
SAs should see new features
Go to each other’s meetings
Information-sharing systems
Evidence-based decision making.
What happens at release time?
How can we measure the system?
Share the data!
Gather metrics
Break existing organisational boundaries
Go and make friends
Stir things up
Internal or external?
Change Agents
How about you?
TOM SULSTON
http://thoughtworks.com@tomsulston