Download - Succeeding with dev ops
Succeeding with DevOps; it's not about DevOps.John Clapham, Cotelic
It seems almost impossible to hide from extravagant claims aboutDevOps; bring operations and development together and you'realmost guaranteed improved resilience, speed of execution, andquality - all at reduced cost. In reality just starting, never mindsustaining, DevOps ways of working is challenging. One reason is thatIT seldom exists in isolation; it interfaces, and interferes, with manyparts of the business.
This talk explores why those external factors are critical to the successof DevOps, what can be done to encourage them, and howdeveloping a DevOps culture can help, or hinder, the widerorganisation.
John Clapham@JohnC_Bristol
Cotelic
www.cotelic.uk
Succeeding with DevOps; it’s not about DevOps.
Succeeding with DevOps; it's not about DevOps.
@johnC_Bristol - @KainosSoftware
When adopting, or evolving DevOps it is
tempting to focus just on tech and those
two teams…
Development and operations are part of a bigger system…
…a much bigger system…
…a complex system…
…even the ITIL person.
Benefits from adoption are helped and
hindered by the surrounding environment.
Succeeding with DevOps; it's not about DevOps.
“Some more things to worry about other than
tools, developers and operations”
@johnC_Bristol - @KainosSoftware
1. Understand your organisation’s goal
If a system is to improve it must have a
goal….
The elevator test: Can you explain the goal
in a short journey between floors?
Public goals are useful rally points…
Public goals are useful rally points…
…encouraging feedback and conversation
2. Know your impact on the system
Narrow focus on Development and Operations
has risks:
Narrow focus on Development and Operations
has risks:
- Over optimisation in one area sub-optimises
the system
Narrow focus on Development and Operations
has risks:
- Over optimisation in one area sub-optimises
the system
- Efficiency gains may be useless if other
systems don’t change.
Narrow focus on Development and Operations
has risks:
- Over optimisation in one area sub-optimises
the system
- Efficiency gains may be useless if other
systems don’t change.
- Closer connections between groups may
weaken other connections, leading to new
silos.
What do other departments expect?
This?
We give them…
Interdependent elements:
Culture,
Tools,
Architecture,
Process,
Organisation.
“[Tools] don’t work for learning about each
other, for really coming together to know
and understand each other”
-Sherry Turkle
3. Learn how to learn
Learning takes commitment…
…and time
Learn from other’s attempts…
Learn from others attempts…
… failures are full of learning.
On a personal note:
Learn how you learn
Listen, diversely…
Listen, diversely…
Exclusively seeking those who ‘get it’ denies
you a fresh perspective and a wealth of
experience.
4. Prepare for change
When encouraging change it’s easy to
loose the perspective of others.
- We take time to get used to new ideas.
Roger’s innovation & Adoption Curve.
- We take time to get used to new ideas.
- We react to change by stalling, supporting
or suppressing.
David Viney - J Curve Effect observed in change.
Appetite for risk determines comfort in this area
- We take time to get used to new ideas.
- We react to change by stalling, supporting
or suppressing.
- Our appetite for risk determines our pace
of change.
TL;DR?
- Consider people’s reaction to change,
take a community approach.
4. Prepare to change.
4. Prepare to change yourself.
“Progress is impossible without change,
and those who cannot change their minds
cannot change anything”
- George Bernard Shaw
DevOps is not just about new thinking, its
about renewal…
A little self awareness goes a long way…
Sir, are you aware your behaviours
discourage collaboration?
Reflections…
Increased collaboration between technical
teams brings real benefits.
Their potential is often governed, or
constrained, by the organisation around
them.
Focus on key areas can further adoption,
and allow collaboration to flourish.
1. Understand your organisation’s goal
2. Know your impact on the system
3. Learn how to learn
4. Prepare for change
5. Prepare to change yourself
Learn from DevOps, but don’t sweat the
definition…
Learn from DevOps, but don’t sweat the
definition…
…It’s your context, it’s your call.
John Clapham@JohnC_Bristol
Cotelic
www.cotelic.uk
Thanks!
Further reading…
My blog, Erratic Mumblings:
http://johnclapham.wordpress.com/
My Slideshare:http://www.slideshare.net/john.clapham/presentations
Bath Scrum User Group (Not just in Bath, and not just for Scrum!)
http://www.meetup.com/Bath-Scrum-User-Group/
References…Sherry Turkle, Connected But Alone.
http://www.ted.com/talks/sherry_turkle_alone_together?language=en
The Kubler-Ross Model
http://www.managetrainlearn.com/page/kubler-ross-model
Roger’s Adoption Curve
http://www.valuebasedmanagement.net/methods_rogers_innovation_adoption_curve.html
David Viney, J Curve (Book) – “The Intranet Portal Guide: How to Make the Business Case
for a Corporate Portal, Then Successfully Deliver”
Kanban (Book) “Successful Evolutionary Change for Your Technology Business”
http://www.amazon.co.uk/Kanban-David-J-Anderson/dp/0984521402
Story of DevOps and Continuous Delivery at Nokia Entertainment
http://www.infoq.com/articles/monthly-devops-01-nokia
References…The Goal
http://northriverpress.com/the-goal-25th-anniversary-edition/
Danny MacAskill
http://www.dannymacaskill.co.uk/videos/
Images…Merits of ferrets
https://www.flickr.com/photos/sovietuk/2499720301
Solar system
https://www.flickr.com/photos/turbojoe/421680689
Change
https://www.flickr.com/photos/arthurjohnpicton/4383221264/
Lego trooper
https://www.flickr.com/photos/59104528@N08/6015476029/
Contortionist
https://www.flickr.com/photos/100915417@N07/9625565178
Cogs
https://www.flickr.com/photos/aussiegall/4085532798
Images…
Fireworks
https://www.flickr.com/photos/tombricker/8641228250
Agile conference
https://www.flickr.com/photos/yourdon/7822889344
Reflections
http://www.flickr.com/photos/uk_pictures/3483034558/