Is DevOps dead? Have we seen the end of the original intent of the movement that set a path to re-energize the engineering community? With the emergence of a pointed focus on tools and now massive organizations selling 2-day DevOps certifications, have we lost our way? This talk re-centers the focus of the engineering community to why we started this journey originally; to focus on learning, culture and feedback loops within complex systems and organizations. We will use data and stories from the trenches to weave a message about the anti-patterns that are emerging, but shine a focus on the stories of success and what good outcomes look like.

1. @_LockardRIP DevOps
RIP DevOps
Ryan Lockard
VP, Contino
@_Lockard

2. @_LockardRIP DevOps
whoami
Ryan Lockard
@continoHQ person, Lean/Agile practitioner
Philadelphia Native | Coffee-Beer Nerd
Head of Tech Support for my Mom

3. @_LockardRIP DevOps
WHyIsItDead
1. Over-Indexing on technology
2. No shared understanding
3. Certifications, FFS

4. @_LockardRIP DevOps
DevOps, WTF?
Concept
Plan
Build
Integrate
Test
Deploy
Learn
Time

5. @_LockardRIP DevOps
DevOps, WTF?
Concept
Plan
Build
Integrate
Test
Deploy
Learn
Time
Business VALUE

6. @_LockardRIP DevOps
Bad systems are
pigs.

7. @_LockardRIP DevOps
Can we agree that a base principal of DevOps is the integration
of Development, infrastructure and Operations?
What percentage of IT professionals would you say feel DevOps
has not yet been adopted at their work?
78%
SRC: 2nd Watch https://bit.ly/2KPpDnq

8. @_LockardRIP DevOps
That was a survey of 1000 IT professionals!
Of that same population, guess what percentage said they do
Infrastructure as code instead of manual
configuration/provisioning?
60%

9. @_LockardRIP DevOps

10. @_LockardRIP DevOps
78%
DevOps not
adopted
60%
IAC
Including Terraform, Containers
COnfig Mgmt

11. @_LockardRIP DevOps
Remember...

12. @_LockardRIP DevOps
Bad systems are
pigs.

13. @_LockardRIP DevOps
DevOps-yTools

14. @_LockardRIP DevOps
Yup. Still a pig
Failure 1: No shared
Understanding of
DevOps

15. @_LockardRIP DevOps
Pipeline all the things!

16. @_LockardRIP DevOps
Manual handoffs
Discoverability
Security Concerns
Silos
Business
Outcomes

17. @_LockardRIP DevOps
So, can you embrace DevOps without tools?
No. Don’t be stupid.

18. @_LockardRIP DevOps
“At its heart, though—when you dig down underneath the rhetoric and
positions, the software architecture decisions and design patterns,
down below the software-development lifecycle and your agile
practice—DevOps is about bringing together all the people you need to
build and run your business effectively, and empowering them to move
as quickly as possible towards their goals. “
Adam Jacob
Co-Founder and CTO of Chef
Failure 2: Widespread
misconceptions of
DevOps

19. @_LockardRIP DevOps
Enterprise Process

20. @_LockardRIP DevOps

21. @_LockardRIP DevOps

22. @_LockardRIP DevOps

23. @_LockardRIP DevOps

24. @_LockardRIP DevOps

25. @_LockardRIP DevOps

26. @_LockardRIP DevOps
Failure 3:
Conflicting
interests of DevOps

27. @_LockardRIP DevOps
Certification

28. @_LockardRIP DevOps DevOps Certified

29. @_LockardRIP DevOps
How do we actually transform to a DevOps culture?
Two Stances

30. @_LockardRIP DevOps
inspirational
communication
How do we actually transform to a DevOps culture?
Leadership
Vision
intellectual
stimulation
supportive
leadership
Personal
Recognition

31. @_LockardRIP DevOps
Low Deployment
Frequency
How do we actually transform to a DevOps culture?
Teams
Low Lead Time
for Changes
High Lead Time
for Changes
High Deployment
Frequency
High Performing Teams
Low Performing Teams

32. @_LockardRIP DevOps
How do we actually transform to a DevOps culture?
Src: State of DevOps 2017
Focus on Capabilities:
-

33. @_LockardRIP DevOps
FSI Case Study - January 2019
Feature Development
~8-10 weeks
Merge, Issue
Resolution
~2 weeks
Functional
Testing
~4 weeks
(mostly manual)
Performance
Testing
~2 weeks
Integration /
Regression testing
~4 weeks
(led by QA)
Time to business testing ~16 weeks
Time to go-live ~22 weeks
UAT 8 weeks

34. @_LockardRIP DevOps
Active pairing across Dev/QA & BA team
- Architecture definition
- Story definition
- Testing definition
- Paired-programming
- Pipeline development and management
- Interaction with other groups (Data, Security,
QA)
FSI Case Study - January 2019
DBA, other
SME’s
Contino
Dev/QA
BA / Scrum
master Contino
BAProduct
Owner
1:1 pairing for the Client dev resources to enable upskilling and embedding best practice software
craftsmanship into the team
Client
Dev/QA

35. @_LockardRIP DevOps
FSI Case Study - January 2019 Team Productivity Increased
216%+
Lead time for change
Reduced from 22 weeks
To 4 weeks
Annualized operational
Efficiency gains expected to be
Over $4.3M
* Adopted DevOps
Principles
* TDD/BDD
*Decoupled Monolith
(4 mos)

36. @_LockardRIP DevOps
Thats a wrap
So are you saying DevOps is dead? No
DevOps <> Tools
You cannot certify a culture, especially if you do not
understand a culture

37. @_LockardRIP DevOps
¯_(ツ)_/¯