Your development team keeps talking about DevOps and the Cloud, but what does that really mean? Should your team be deploying to production twenty times a day or should you stick to your monthly release schedule? If you agree to make changes, what does that mean for your bottom line? The deck will take a business approach to how DevOps can impact your company, leaving out the developer-speak and debunking DevOps myths. A presentation by developers, for technology leaders and decision makers.

1. More Than A Buzzword: How
DevOps Can Impact Your Business

2. What We Offer
Looking for in‐depth guidance with DevOps? ILM
Professional Services can provide:
• On‐site Lunch & Learn at your company. The
presentation can be targeted for the audience, from a
general overview of DevOps to a more in‐depth technical
tutorial.
• Analysis of your company’s current environment to
determine your readiness for DevOps implementation,
plus assistance with tool selection.
Contact us for more info:
info@ilmservice.com or (952) 960‐2220

3. Goals
1. Discover DevOps’ business value
2. Understand what DevOps is
3. How to get started with DevOps
(Figure 1)

4. What the word DevOps is
• “software DEVelopment” + “information technology OPerationS”
• Devs: software
• Ops: infrastructure
• But wait… there’s more!
(Figure 4)

5. CAMS (DevOps Core Values)
•Culture
•Automation
•Measurement
•Sharing
(John Willis,
Chef 2010)

6. What about..?
Information Security
Quality Assurance
Market Analysis
User Experience

7. With DevOps…
…teams are able to quickly and independently develop, test, and
deploy code and (business) value quickly, safely, securely, and reliably
to customers. This allows organizations to maximize developer
productivity, enable organization learning, create high employee
satisfaction, and win in the marketplace.
(The DevOps Handbook)

8. Agile into DevOps
(Figure 7)

9. Is it Done?
•All IT groups should have similar principles
•Speed, collaboration, transparency and
customer satisfaction
•DevOps extends “done”
•Everyone gets to party at the end!

10. The Continuous Improvement Feedback Loop
(Amazon, 2017)

11. Isn’t it just about tools?

12. Don't Get Duped
(Figure 5)

13. DevOps: Not on a Shelf

14. DevOps Myths
Myths
• DevOps engineer
• “Jack of all trades, master of none”
• More interruptions
Truths
• DevOps evangelist & team
• Still specialists
• Reclaim time
(Figure 6)

15. Culture traditionally between Devs and Ops…

16. Without DevOps: Divided Culture
• But what you want is…
(Figure 9)

17. DevOps Culture: Teamwork
• How do you get there…
(Figure 10)

18. Traditionally: Features vs Stability
• Why change is needed: moving faster and scaling up
(Figure 11)

19. DevOps: Features AND Stability
• How to tear down the wall…
(John Willis, IT
Revolution 2012)

20. DevOps Culture: Increased Collaboration
• “Report It” “Fix It” (collaboration & shared responsibility)
• Ops help Devs design environment from beginning
• Devs help Ops support Prod
• Eliminate “Us vs. Them” mentality
(Figure 12)

21. The Snowflake Dilemma

22. Automation: Pets vs Cattle (Owning vs Renting)
• Indispensable
• Manually uniquely crafted
• Personal attachment
• Named
(Traditional) (DevOps)
• Expendable
• Automated & consistently built
• No nurturing
• Numbered
(Figure 13)

23. Configuration as code
•Multiple Environments –> One code base
(Secure)
•Secrets
• Encrypted and only access via automated scripts
• Are not recoverable, only replaceable
(Reliable, Repeatable, Safe)
•Environment builder code is stored in source
control

24. Why DevOps?

25. Why DevOps
Two major competing goals:
• Responding to competitive and more often
than not, a rapidly changing market landscape
• Providing useful, highly available, reliable and
secure services to the customers

26. The Bottom Line
Business Agility – (according to HRZone.com)
refers to distinct qualities that allow organisations to
respond rapidly to changes in the internal and external
environment without losing momentum or vision.
Adaptability, flexibility and balance are three qualities
essential to long‐term business agility.
(Most businesses rely heavily if not solely on IT to accomplish this)

27. DevOps’ Business Value: Backed With Hard Data
(Puppet Labs, 2016)
•Performance difference: Traditional vs DevOps
•4,600 technical professionals surveyed worldwide
•Wide variety of roles, departments, industries,
company & infrastructure sizes
•Outliers (unicorn companies) excluded

28. Key Performance Indicators (KPIs)
• Deployment Frequency
• Speed of Deployment
• Deployment Success Rate
• Time to Recovery
• Culture – Not Measured

29. Lead Time
• Lead Time: 3.5 months vs 1 hour
• Deliver more value sooner

30. Deployment Frequency
• Deployment Frequency: 1.7 months vs 4x day
• Less risk
• Feedback sooner

31. Failure Rate
• Changes that cause an outage: 23% vs 7.5%
• Get more done – and with less errors

32. Failure Recovery
• Recovery time: 1 day vs 1 hour

33. The DevOps Difference
• Ops: less pager calls at 3am
• Devs: write more code
• More fun – and deliver more value
(Figure 2)

34. 2017 Update
It was found in the 2017 survey, that low performing team are closing
the gap in terms of deployment frequency and lead times due to an
advance in tooling and adoption of some DevOps practices.
However..
These teams also showed an increase in failure rate and time to
recovery.

35. ESP
I know what you are thinking…

36. What you are thinking

37. “Show Me the Money!”
• Silverpop/IBM: Automating Deployments yields Savings
• Etsy: DevOps Increased Revenue
Year Initiative Sales Increase Visitors Increase
2009 Automated deployments
$90M(by 103% to $177M)
96% (to 320M)
2010 Standardized infrastructure & configurations
$130M(by 73% to $307M)
66% (to 534M)
2011 Eliminating non‐standard technologies
$219M(by 71% to $526M)
67% (to 895M)
Before DevOps
• 12‐18 people for 8+ hours
• 400 manual steps
• Inconsistent error‐prone
process
With DevOps
• 5 minute deployments
• Zero downtime
• $1M annual savings
(IBM, 2015)
(IT Revolution,
2012)

38. DevOps ROI: Data From LPS (client of ILM)
• Decrease in daily costs after implementing DevOps in January 2017
to March 12

39. Increasing Value of DevOps
• Compounding (e.g. 7.3x more deployments in year)
Get started this year

40. Getting Started With DevOps
• Organizational definition of DevOps
• ROI Analysis
• Value: more specific than time & $
• Cost: training, staff augmentation, tools
• Time (“it depends”):
• Automate deployments: e.g. 3 weeks (Pearson VUE, 2014)
• DevOps/Containers: ~1 year
• Each iteration gets easier: 1, 2, 10, 100, 1K
• Get top‐down buy‐in
(Figure 17)

41. Walking the path
1. Start small – DevOps is not all‐or‐nothing
2. Have a plan – create feedback loops
3. Try many tools – don’t (necessarily) buy the hammer
4. Explore different combinations of tools – look for patterns and
learn from others’ successes and failures
5. Examine your organizational workflows ‐ find bottlenecks and
constraints and identify types of work and value streams
6. Evaluate expertise that exists within the organization, and tools
and processes already in place
Remember – work in cycles and use your data to drive your choices.

42. Automation: The 3 C's (CI/CD)
• Need automated testing
• Which CD is best?
• “It depends” ‐ do what’s best for your organization
• Both minimize time spent not delivering value
(Figure 14)

43. Automation: Infrastructure as Code
• Versioning environments
• Consistent & repeatable
(Figure 15)

44. Better Together
• Fantastic Four
• DevOps
• The Cloud
• Microservices (modularity)
• Containers (virtualization)
• 1 OS to rule them all – unlike VMs
• Infrastructure as code – e.g. Dockerfile
• Eliminate WOMM (Works on My Machine)
• No wrong recipe
• Any number of them
• No pre‐requisites
• Implement each incrementally
(Figure 16)

45. Reasonable expectations
The J effect on adopting a new mindset and toolbox
Low speed
Low stability
Low innovation
Low retention
High speed
High stability
High innovation
High retention
Early wins
The hard road
Real success
Borrowed from Puppet Labs presentation on the State of DevOps 2017

46. Summary
1. DevOps CAN definitely bring business value
2. DevOps IS
• A Collaborative culture
• Cross‐disciplinary engineering practices
• Efficient & integrated tools
• Continuous learning from feedback loops
3. Get started with DevOps!
(Figure 18)

47. www.ilmservice.com
Sean Epping
Principal Consultant
• Thank you!
• Q&A (Figure 19)
sean.epping@ilmservice.com
seanepping
@seanepping

48. Resources
• Feedback Loop: (Amazon, 2015): DevOps: A Look at Our Tools and Processes
• (Puppet Labs, 2016): 2016 State of DevOps Report
• And other great DevOps resources from Puppet Labs:
• Six DevOps myths, busted
• Get Started with DevOps: A Guide for IT Managers
• How to Build a High‐Performing IT Team: Five essential steps to mapping your DevOps journey
• DevOps Business Value: Case Studies
• (IBM, 2015) Silverpop/IBM: Automating Deployments yields Savings
• (IT Revolution, 2012) Etsy: DevOps Increased Revenue
• CAMS acronym description: (John Willis, Chef 2010), What Devops Means to Me
• CAMS image: DEVOPS: HOW A CULTURE OF EMPATHY CREATES MASSIVE PRODUCTIVITY, Telehouse
• Wall of Confusion: (John Willis, IT Revolution 2012): DevOps Culture, IT Revolution

49. Figures/Images
• Figure 1: goal bridge.jpg
• Figure 2: I‐Love‐My‐Job.jpg
• Figure 3 (Princess Bride ‐ what DevOps means): Microsoft Virtual Academy: DevOps
• Figure 4 (Venn diagram DevOps): DevOps Journey Part II ‐ Version Control
• Figure 5 (sold them tools… ‐ Dr. Evil's allies): Agile Memes, Part 1
• Figure 6: myth‐busted.jpg
• Figure 7: logos: Agile (loops.png) & DevOps (cog wheels gears.png)
• Figure 8 (roles included in Agile & DevOps): What Is Continuous Delivery: The Last Mile
• Figure 9 (worked in Dev…): DevOps: Tear Down that Wall!
• Figure 10: Avengers ‐ Together.jpg
• Figure 11 (wall between Devs & Ops): VMware DevOps Blogs: What Is DevOps, and Why Should I Care? — The IT Leadership Perspective
• Figure 12: removing walls & silos
• Figure 13: Pets (puss‐in‐boots.png) vs Cattle (Pets vs. Cattle: The Elastic Cloud Story ‐ slide 8)
• Figure 14 (CI/CD): Continuous Integration, Delivery and Deployment Explained
• Figure 15 (versioning code & infrastructure): DevSecOps (slide 11)
• Figure 16 (better together ‐ fantastic four): cookies & milk and donut & coffee
• Figure 17: Logic – Spok.gif
• Figure 18: questions ‐ raised_hands.jpeg

50. PERIODIC TABLE OF DEVOPS TOOLS (V2)
• Just as an e.g., I circled the tools used in an app I (Josh) created.

51. VMs vs Containers
• (Virtual machines vs. Docker containers)