Presentation on the challenges, approaches, and reality of DevOps in large enterprises. Given at DevOps Summit 2014. Better with voice track - contact me.

1. Enterprise DevOps: Same Medicine, Different Dose
Use As Directed

2. Hi! I’m Chris ( @HoardingInfo )
I’m a bad coder turned market analyst at
Author for DevOps.com &
A sometimes DevOps practitioner
12 years in B2D2B

3. CA Technologies @CAinc Oct 22
CA CEO: “DevOps is the future of enterprise software
dev - we're focusing our investment to drive leadership in
this space.” #earnings
Tim O'Reilly @timoreilly Jul 22
Excellent read: A promise theory perspective on DevOps
http://bit.ly/1sNvrxt DevOps is really the heart of the new
enterprise

4. The Rub:
 New front-ends need to play with really old back-ends
 We move too slow to adopt DevOps
 “We are big” – “We are special”
 Compliance…

5. The Secret Rub:
It is my budget damnit!
Stop re-inventing things I already know
I hate Hipsters

6. There are no Green Fields

7.  LOB Application Development
 Existing Application Development
 Net New Web & Mobile App Dev

8. Why?
 Better, Faster, Cheaper - Duh

9. Why?
 Make customers happier
 Know more than you ever did – God Mode
 Respond faster, improve quality
 Remove bottlenecks – have a real roadmap
 Because your competitors will

10. Misconceptions
 There are 2 DevOps: Movement and Practice
 DevOps is not an end, it is a means
 DevOps != Tooling
 ITIL & ITSM is not close or similar to DevOps

11. It is Possible




12. Approach's
 Do nothing
 Slipstream
 Silo ( Build a Lab )
 Rip off the Band-Aid

13. Watch out
 “It’s going to be hard” = “Lets do it like we always have” = Anchoring Effect
 Management has to care
 It’s mostly a people problem

14. DevOps change score
 Can you change the org structure?
 Are you leveraging public or private cloud?
 Do your application teams have budget?
 Do you wear hoodies to work?
 Are your development teams empowered?
 Does QA work? ( as apposed to steadily getting worse)
 Do you use any release automation processes?
 Does Management gets the benefits of DevOps?
 Are you in a regulated industry?
 Does development report to IT?
 Are you level 30 or higher on WoW?
 Can developers pick their own tools?
 Are you using Internet Explorer?
 Do you have net new app dev?
 Is Shadow IT met with a lockdown?
 Does your change management work?

15. DevOps change score
 Good to go: Start with analytics, and jump in head first
We’re scared: Automate something. Do experiments
 Nope, we are a fortress of slow: Quite your job

16. How?

17. Operate less on habit and more on intent.
Results are all that matter.

18. Step 1 Culture
Step 2 Process
Step 3 Tools

19. Do no misunderstand “culture”

20. Tools Solve Nothing!

21. Start with
 Analytics everything, always
 “Fail fast”
 Focus on results

22. Start with
 Be deliberate with your “culture”
 Know your pipeline(s)
 Create shared goals

23. Exciting Stuff
 The mythical DevHub
 Did you said “Containers” … again
 Evolution of Shared Services
 SDNs

24. Resources
 DevOps.com
 Twitter
 Dudes like me
 Your peers