2. 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.
7. Building quality in wherever you are
UAT
SIT
ST
UT
ST
UT
UAT
SIT
UAT
SIT
ST
UT
8. 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
10. 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?
11. Back to Lean Change Management
DevOps is most successful In the culture
on the right
You can’t simply engineer your way to a
purpose driven culture
Do this
Then that
And then
this
Magic
happens
Wonderful
new
culture
12. Back to Lean Change Management
DevOps is most successful In the culture
on the right
You need to experiment forward to
continually
13. Anti-patterns: A final few don’ts:
Create a team
and label them
the “DevOps”
team
Just 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]”
15. Who I am
Organisational Transformation Provocateur
Strategy Consultant
Lean Change Manager
Agile Coach
Ex Tester
@mjmansell
Matt.Mansell@integrationqa.com
http://www.integrationqa.com
https://nz.linkedin.com/in/matthewmansell
Notes de l'éditeur
ABS example
Shifting towards a DevOps world is about changing the culture by building trust.
This is not a you / them journey. It’s a we journey. The definition is misleading because to truly change to DevOps means changing the way work is requested, funded, managed and governed, domains which are often, even usually, outside the domain of IT.
I asked a colleague what he would say was the first step in moving to DevOps. He said: ‘Ask the business if they really, truly want deployments multiple times a day to their customers; are they prepared to accept that risk?”
To think this is just an IT transformation, or a building better relationships between Development and Operations misses the boat.
Yes you start there. But if you get your DevOps team working perfectly and it takes 3 to 6 months to get a business case signed off to then fund the team your transformation isn’t of much value.
Traditional Delivery methods operate sequentially. Feedback loops are long. I’ve worked on projects where requirements were signed off a year before development began, let alone testing. I’d like to say this is rare, but it’s depressingly common. One of the dreadfully ironic things I see is large transformation
It depends where you are
Candidate for spec by example.
Include Ops in planning, allow them to include examples
Build trust with operations by building OAT
This is about being agile without doing agile. All of these patterns can, and I’d argue, should occur on classic waterfall projects.