Most DevOps transformations are “non-linear” jumps and are at odds with the organization’s existing objectives. This tension needs to be managed and requires an effective execution model to succeed. Presented is a model that significantly increases the chance of transformation success.

1. © 2018
An Execution Framework
for Successful DevOps
Transformation
John Esser, CEO, Veracity Solutions
john.esser@veracitysolutions.com
Twitter: @johndesser

2. © 2018
about veracity solutions
Veracity Solutions is a strategic
consulting firm guiding and assisting
Senior IT leaders formulate and execute
their strategic business initiatives,
transforming IT from a cost-center to a
strategic asset.
Our solutions include product
development, agile solutions, DevOps,
data and analytics, AI, and cloud
adoption.

3. © 2018
Congrats Houston!

4. © 2018
[Some of] my DevOps journey…

5. © 2018
trans·for·ma·tion
/ˌtran(t)sfərˈmāSH(ə)n/
noun
a thorough or dramatic change in form or appearance.
"its landscape has undergone a radical transformation"
synonyms: change, alteration, modification, variation, conversion,
revision, amendment, metamorphosis, transfiguration, evolution, mutation,
sea change; remodelling, reshaping, remolding, redoing, reconstruction,
rebuilding, recasting, reorganization, rearrangement, reordering,
reshuffling, restyling, rejigging, reworking, renewal, renewing, revamping,
renovation, overhaul, remaking; revolutionizing, revolution, transmutation;
humoroustransmogrification
"the food-manufacturing industry underwent a transformation”

6. © 2018
“Through 2022, 75% of DevOps
transformations will fail to fully meet the
expectations of the business…”
-Gartner, Oct. 18, 2018
This is an execution problem!

7. © 2018
How is the value of an Executive IT leader manifest?
ALIGN MANAGE
the ASSETS
EXECUTE!

8. © 2018
A transformation

9. © 2018
Principles of Transformation
1. Meaningful transformation contains both linear and non-linear
change elements.
2. Transformational elements, even if well-known, are sufficiently
foreign and radical from the perspective of the organization that
they can be considered new and uncertain, or innovation.
3. The process of transformation can be managed and executed via
an innovation execution framework.

10. © 2018

11. © 2018

12. © 2018

13. © 2018
The Innovation Model Spectrum
Easier Harder
Small: Anything one
person can tackle on their
own initiative and in their
free time.
(INCREMENTAL/LINEAR)
Custom/Complex: A high-
risk, high-growth potential.
New venture, process,
technology, etc.
(DISTRUPTIVE/NON-LINEAR)
Model
S
Model
R
Model
C

14. © 2018
Model S Model C
Performance Engine (Core) Dedicated (Innovation) Team

15. © 2018
Model C (Custom) Model S (Small)
CI/CD - Deployment Pipeline (Platform) GIT / Incremental branching and check-
ins
Public Cloud Migration – Foundational
Work
Operational Readiness/ Handback
Process
Monitoring/Logging Platform Incident and Problem Management
End-User Monitoring Instrumentation Infrastructure as Code
Dedicated Core NOC Cloud Migration (service-by-service)
Disaster Recovery Daily / On-demand deployments
Dynamic Data Platform adoption Service monitoring by team
Containerization / Kubernetes SRE – Toil reduction
Execute by creating a dedicated team Execute directly in existing teams/org

16. © 2018
Executing Model S Innovations
Make sure there is slack time
(teams) to absorb new way of
working. Don’t do too many
at once!
Provide motivation (rewards,
recognition, structure).
Allow sufficient time for
change adoption!

17. © 2018
Executing Model C Innovations
Build a dedicated team with a
special plan.
Manage the ongoing
partnership.
Merge work artifacts back into
performance engine!

18. © 2018
Common Execution Errors
Failing to Create a Dedicated Team
Breaking the Performance Engine
Asking too much from the Performance Engine
Dedicated “innovation” team is
a “mini” Performance Engine
Poorly Managed Partnership
Isolating the Innovation

19. © 2018
Final Recommendations
Execute cultural & behavioral changes as “type S”
innovations/changes.
Restrict type C changes to new capabilities or
technologies.
Create dedicated teams for new services and
platforms, especially to allow for scaling.
Allow a type C change to reasonably mature before
scaling.

20. © 2018
Contact me:
john.esser@veracitysolutions.com
Thank you.