Embed Size (px)
Citation preview
Changing the Culture of IT
Shifting to DevOps
What is DevOps?DevOps is a culture, movement or
practice that emphasizes the collaboration and communication of both software developers and other
information-technology (IT) professionals while automating the
process of software delivery and infrastructure changes. It aims at
establishing a culture and environment where building, testing, and releasing
software, can happen rapidly, frequently, and more reliably.
Why DevOps
Design
Build
Test
Deploy
From this To this
What’s your strategy to get there?
No battle plan ever survives
contact with the enemy
Culture eats strategy for breakfast
A new way to transform
Evolution to DevOps
But start with test automation
Building quality in wherever you areUAT
SIT
STUT
STUT
UATSIT
UAT
SIT
ST
UT
Shifting from the waterfall to the cascade
Engage operations personnel early on
your project, budget and plan
for it
Bring the team together daily if
possible – morning stand-ups
Engage business personnel early on
your project, budget and plan
for it
Consider Specification by
Example design / build / test
Architect for cloud infrastructure; i.e.
AWS etc
Create and automated quality
gates
Experiment forward – be open
and ready to change
Establish contracts with suppliers that support Agile and
DevOps
Wider change
DevOps “production line”
Technical story
Specified example
User story
Here are 100 changes I
want in a year
Wider change
DevOps “production line”
Technical story
Specified example
User story
Here are 3 changes I
want tomorrow
But how do I fund that? Is
it OPEX or CAPEX
How do I match spend
with outcomes?
How do I write a
business case for that?
Back to Lean Change ManagementDevOps is most successful In the culture
on the rightYou can’t simply engineer your way to a
purpose driven culture
Do thisThen that
And then this
Magic happens
Wonderful new culture
Back to Lean Change ManagementDevOps is most successful In the culture
on the rightYou need to experiment forward to
continually
Anti-patterns: A final few don’ts:Create a team and label them the “DevOps”
teamJust assign an
Ops guy to support a Dev
team
Use AWS and assume that’s the
Ops part of DevOps
Co-locate the teams and call it
DevOps
Just rename the Dev team to
DevOps and leave them isolated
from actual Ops
Retitle peoples job descriptions
to “DevOps [insert role here]”
Questions
Who I am
Organisational Transformation Provocateur
Strategy Consultant
Lean Change Manager
Agile Coach
Ex Tester
@[email protected]://www.integrationqa.comhttps://nz.linkedin.com/in/matthewmansell
