The document discusses the transformational impact of DevOps and cloud technologies on software development and deployment practices, emphasizing the shift towards collaboration between development and operations teams. It outlines the benefits of adopting DevOps, including enhanced delivery speed, reduced deployment failures, and improved job satisfaction while advocating for a cultural shift in organizations to embrace these methodologies. Additionally, it presents ten ways to promote DevOps as a beneficial movement within teams, highlighting its importance in adapting to a rapidly changing tech landscape.

1. DevOps & the Dark Side
10 ways to convince your
team
DevOps is a force for good

3. THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.
WHILST EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION
CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED.
ALL PERFORMANCE DATA INCLUDED IN THIS PRESENTATION HAVE BEEN GATHERED IN A CONTROLLED
ENVIRONMENT. YOUR OWN TEST RESULTS MAY VARY BASED ON HARDWARE, SOFTWARE OR
INFRASTRUCTURE DIFFERENCES.
ALL DATA INCLUDED IN THIS PRESENTATION ARE MEANT TO BE USED ONLY AS A GUIDE.
IN ADDITION, THE INFORMATION CONTAINED IN THIS PRESENTATION IS BASED ON IBM’S CURRENT PRODUCT
PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM, WITHOUT NOTICE.
IBM AND ITS AFFILIATED COMPANIES SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE
USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.
NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF:
- CREATING ANY WARRANT OR REPRESENTATION FROM IBM, ITS AFFILIATED COMPANIES OR ITS OR THEIR
SUPPLIERS AND/OR LICENSORS

4. Steve Poole
IBM Developer
Making Java Real Since Version 0.9
Open Source Advocate
DevOps Practitioner (whatever that
means!)
Driving Change

5. You should be able to leave today knowing
 How to explain what DevOps is and what it is not
 How to explain the benefits of DevOps and the Cloud to developers,
‘suits’ and IT specialists’
 Your next step in promoting DevOps

6. There are some who assert
that DevOps is just a fashion
That it’s not needed and might
be counter-productive
Is that true?
Let’s start by looking at what’s
happening in our industry
https://www.flickr.com/photos/whatleydude/

7. https://www.flickr.com/photos/28581681@N04/

8. The surge of Cloud
technologies that offer
compute ‘on tap’ are
making businesses
think differently about
how to buy and use
computing power
https://www.flickr.com/photos/alexbrn/

9. https://www.flickr.com/photos/epsos/
Easier than ever before
a business can hire a
CPU
Just for how long they
need it.
No long term capital
investment.
Just expense.

10. 0
5
10
15
20
25
30
35
1/1/13 1/1/14 1/1/15 1/1/16 1/1/17
Traditional
Cloud
Does investment just
move from one place to
to the other?
Will cloud capacity just
pick up the slack?

11. 0
5
10
15
20
25
30
35
1/1/13 1/1/14 1/1/15 1/1/16 1/1/17
Traditional
Cloud
Will ‘cloud’ capacity just
pick up the slack?
If I can buy X amount of
CPU over a year…

12. 0
5
10
15
20
25
30
35
1/1/13 1/1/14 1/1/15 1/1/16 1/1/17
Traditional
Cloud
I can buy 4X over ¼ the
time…
And deliver much
earlier!

13. 0
5
10
15
20
25
30
35
1/1/13 1/1/14 1/1/15 1/1/16 1/1/17
Traditional
Cloud
Repeatedly…

14. cloud capacity is
changing the way
software needs to be
developed
https://www.flickr.com/photos/memebinge/

15. Means you can start small and
add what you need when you
need it..
and take it away when
you’re done
Like carriages on a train
https://www.flickr.com/photos/44534236@N00/

16. https://www.flickr.com/photos/derekskey/
“Software as a Service”
profoundly changes the
way software is
designed and
delivered

17. No more delivering
parts that someone else
puts together
No more handing your
code off to others to use
in production.
https://www.flickr.com/photos/pmiaki/

18. Your software could go
into production
immediately
Like changing the teeth
on a tunnel boring
machine while it’s still
cutting
Ready for that?
Your
software
https://www.flickr.com/photos/mtaphotos/

19. Businesses see the opportunities here
Improved value for money, decreased
time-to-market, shorter time to value
“I can now get my ideas into
production in hours,days or weeks. I
can get immediate feedback AND then
I can improve the idea and repeat”

20. Money changes everything
With a measureable and direct
relationship between $ and CPU/RAM
The financial success or failure of a
project is even easier to see
And that means…
Even more focus on value for money.

21. “Everything fails all the
time [in the cloud]”
Werner Volgels, CTO, Amazon
Your application has to work in a
new way, in a new place.
Where strange behaviors
happen all the time
It needs to be ‘anti-fragile’
https://www.flickr.com/photos/fireflythegreat/

22. Whatever you do – your
world is changing.
Old ways of developing and
delivering software are
being replaced with new,
faster, easier and more
powerful ,
alternatives

23. https://www.flickr.com/photos/stawarz/
https://www.flickr.com/photos/dominicspics/

26. is it really that
bad?
https://www.flickr.com/photos/tm-tm/

27. 1 5 10
20
50
150
0
20
40
60
80
100
120
140
160
Bug fix cost
You’ve all seen this sort
of chart
Think about it differently..
It’s “time” & “delay” but
also “fitness for purpose”
&
“hard to rectify”

28. 1 5 10
20
50
150
0
20
40
60
80
100
120
140
160
Bug fix cost
You’ve all seen this sort
of chart
Think about it differently..
It’s “time” & “delay” but
also “fitness for purpose”
&
“hard to rectify”
Ops problems can kill your
business. How much do
you know about Ops?

29. Too often we hear about
failures in systems that come
about due a simple bug or
vulnerability occurring in a
complex situation or in a
more organic environment
than expected

30. Case Study: A large bank uses agile techniques to create ‘complete’
solutions in < 3 weeks.
But It takes the Ops team about 15 months elapsed before the
deployment process starts and It take about 3 months to complete
deployment
why?
3 weeks to develop vs 3 months to make deployable = continuous
backlog
Continuous backlog = some projects never see the light of day
AND Ops talk to Dev 15 months after completion -> you can guess how
that turns out….

32. Our Dev teams and Ops teams
do not communicate properly
but we know what to do…
It’s a problem
baked into our
processes
http://www.comicvine.com/images/1300-3387749

34. Design, Code
Unit test
Functional Test
System test
Stage
Configure
Fix bugs
Fix bugs
Helpline
Monitor, backup
upgrade, support, repair
security, compliance
Uses
reality
chasm

35. Reinforced team separation
Long feedback cycles
Long time-to-market
Tended to increase
‘Release Panic’
BIG
Reality
ChasmDEV OPS

36. Time
#ofbugs
Start to panic
here
Really panic
here
DEV
OPS
QA
Client
£
Value here

37. Time
#ofbugs
Start to panic
here
Really panic
here
DEV
OPS
QA
Client
No
Value here

38. Time
#ofbugs
Feedback
here
OPS
Client
DEV
Feedback
here
Feedback
here
QA
$
Value here

39. Time
#ofbugs
OPS
Client
DEV
QA
$
I want value
here
And here

40. Time
#ofbugs
OPS
Client
DEV
QA
$
Move Left

41. Time
#ofbugs
OPS
DEV
QA
$ $ $
Client

42. Continuous Integration
JUnit
SCM BuildBuild
Orchestration
Unit
Test
Continuous Feedback

43. Continuous Integration
JUnit
Continuous Delivery
Repositor
y
Performance & QA
Deployment tools
Continuous Feedback

44. Continuous Integration
JUnit
Continuous Delivery
HostingContinuous Feedback

45. Continuous Integration
JUnit
Continuous Delivery
Continuous Feedback
Continuous Deployment
Continuous Feedback
Hosting

46. Continuous Integration
JUnit
Continuous Delivery
Continuous Feedback Hosting
Days? Weeks?
Months?

47. Would you believe < 1hr?
Case Study: A fashion retailer can show measureable increase in sales if
a item similar to that seen in the media can be placed on their on-line
store landing page within 1 hr of it appearing in public.
Each product placement is different so they need a fast, agile, approach
that does not jeopardize their on-line stores availability and quality.
We know how to do this..

48. Open Stack
Continuous Deployment Pipeline
External CloudOn premises cloud
Cloud
Deployment
Orchestrator
JUnit

49. JUn
it
Continuous Deployment
Continuous Feedback

50. Startups through to big businesses are
demanding the value that DevOps & Cloud
Technologies can offer
1. Production deployment pipeline up and
running in days
2. Updates published in hours or minutes
– continuously
DevOps helps transition an organization
into this new world…

51. The cost?
1. Standardized pipelines
2. Dev and Ops teams working together
3. Greatly expanding your horizons and your technical skills
4. Leaving your comfort zone

52. 10 Ways to convince
your team DevOps is
a force for good

53. #1 DevOps is not a technology it’s a
movement
It’s about the next stage in working
together to deliver software
It’s about reducing delivery friction through
knowledge sharing
It’s about applying Agile ideas to Ops
It’s about collaboration and sharing
It’s about changing the culture
Manifesto for Agile Software
Development
Individuals and interactions over
processes and tools
Working software over comprehensive
documentation
Customer collaboration over contract
negotiation
Responding to change over following a
plan

54. #2 Working together and exploiting “Infrastructure as Code’
approaches and technologies such as Docker, PaaS’s etc enable Ops
teams to bake in their requirements and Dev & QA teams to run in
modes much more like production
#3 Using virtualisation solutions like IaaS and PaaS makes
deployment easier and more ‘self-service’. This reduces the overhead
on the Ops team and hence improves delivery time
#4 It works the other way too – getting Dev team monitoring and
diagnostics baked-in means less back and forth and no need to
access that production server..

55. The demonstrable benefits of using DevOps and
Cloud tech are self evident enough now that
everyone wants to do it
Bringing Development & IT together to solve
deployment problems through sharing and
learning creates an organization with
“Strong IT performance”
This is becoming a major competitive
advantage
#5 - 30x deliveries
#6 - 50% reduction in
deployment failures
#7 2x likely to exceed
important business
goals
Source:puppetlabs2014

56. “Using version control for scripts”
“Automating testing”
“Using TDD or BDD”
“we need to adopt Micro-services
design”
Why can’t we get our systems
proactively monitored?”
“How about Pair-programming – even
for ops
“Lets be honest – developers are lazy. If you have
to do it twice you’ll write a script. Ops teams
worry about everything the lazy developer didn’t
do. - like security,”
“low-friction organizations are good at recognizing
and removing obstacles – got an HR system that
gets in the way. Hate that corporate expense
tool? Wish you had a corporate expense tool
instead of the paperwork?”
“Since DevOps (and Agile) is about failing early and failing fast that approach
can spill over into the day to day culture – let it happen! Make it safe to fail..
And what about security – how about getting security ‘baked-in’ right at the
design time?”

57. #9 – DevOps increases Job Satisfaction
IT Companies with high levels of job satisfaction are mostly likely to be
able to deliver consistently and with high quality. (Hint – who get
chosen 1st?)
#10 Adopting DevOps & the Cloud successfully make your
organisation well positioned for exploiting new capabilities – like
Analystics, BigData or even something like IBM’s Watson

58. Businesses need to be able to react faster…
…DevOps and the Cloud are key enablers
DevOps is as much a game changer as Agile was…
…this is a Developer, QA and Ops “renaissance”
Don’t be afraid to learn and experiment…
…you’ll benefit even if the tech doesn’t survive
Agile moved you closer to the customer…
…DevOps moves you closer to the IT team

59. 1 – Lean and present Docker and PaaS style options to your peers.
Whether Ops or Dev you’ll see the value
2 – Find a buddy in the other camp.
3 – Get ‘real’ monitoring going across your infrastructure and applications
what ever you can monitor do so. And graph it, put up dashboards.
Look for and learn the warning signs of a failing system and get your peers
and detractors to see the value
(BTW – don’t monitor a system when you need to monitor the app!)
4 – Start to tackle automation
look for the places where others are challenged. And fix it for them.
Introduce Chef, Puppet, Bash, Groovy – the goal is automation 1st – cool tech 2nd

60. Ask your organisation some difficult questions:
Deployment frequency?
Speed of deployment?
Deployment success rate?
How quickly service can be restored after a failed deployment?
Time from 1 line of code until in hands of the customer?

61. Thank
You!
https://www.flickr.com/photos/lens-cap/