This document outlines the top 10 ways to fail at DevOps. It discusses failing to include management buy-in, becoming too reliant on open source software, and failing to consider IT history. It also notes that DevOps should not mean "DevNo-Ops" and that the same automation used in development and testing environments should also be applied to production, with the production environment in mind from the beginning. Centralizing DevOps and thinking failures in production are acceptable are also outlined as ways to fail at DevOps. The document provides context and examples for each of the top 10 ways.

2. Top 10 Ways to Fail at DevOps
November 2016
Scott Willson – Mktg. Dir. – ARA / DevOps

3. AGENDA
DevOps Definition
Top Ten List

4. 4 Property of Automic Software. All rights reserved
DevOps is a…
Gartner – 2014 Cool Vendors in DevOps
DevOps is a philosophy (not a market). There are
no rules, no manuals, only guidelines.

5. 5 Property of Automic Software. All rights reserved
10. Application Release Automation Tools
Gartner – 2016 Application Release Automation MQ
ARA tools are a key part of enabling the DevOps
goal of achieving continuous delivery with large
numbers of rapid, small releases.
Forrester – 2016 Vendor Landscape: ARA Tools
ARA tools help firms release software consistently
and in an automated fashion as a key part of getting
business technology solutions to end customers.

6. 6 Property of Automic Software. All rights reserved
9. Failing To Include Management Buy-in

7. 7 Property of Automic Software. All rights reserved
8. Become Too Reliant on OSS

8. 8 Property of Automic Software. All rights reserved
7. Failing to Consider IT History

9. 9 Property of Automic Software. All rights reserved
7. Failing to Consider IT History

10. 10 Property of Automic Software. All rights reserved
7. Failing to Consider IT History

11. 11 Property of Automic Software. All rights reserved
7. Failing to Consider IT History

12. 12 Property of Automic Software. All rights reserved
7. Failing to Consider IT History

13. 13 Property of Automic Software. All rights reserved
6. Boxing Yourself In
in
Expanding DevOps and Continuous Delivery Use Case
• Mainframe & Legacy Systems/Teams
• Core Backend COTS Apps
DevOps Orchestration
• QA, SecOps, DBAs, etc…
• DevOps toolchain
Flexibility
• Tech Stack Agnosticism
• Sophisticated Controls, Calendaring & Scaling

14. 14 Property of Automic Software. All rights reserved
5. Standardizing on Unproven Languages
http://www.zdnet.com/article/which-programming-languages-are-most-popular-and-what-does-that-even-mean/

15. 15 Property of Automic Software. All rights reserved
4. Centralize DevOps

16. 16 Property of Automic Software. All rights reserved
3. Think it is OK to Fail (in PROD)

17. 17 Property of Automic Software. All rights reserved
Use Same Automation Mechanics for Every Environment
DEV is Deployed to All the Time
QA - Less Often
PRE-PROD - Even Less Often
PROD - Less Frequently Still
2. Begin With the End in Mind – PROD CD Automation
Humble, J., & Farley, D. (2011). Ch. 5. In Continuous Delivery (p. 115).

18. 18 Property of Automic Software. All rights reserved
Ops
• PROD Support
• DEV/QA Support
• Business Needs
• Release Management
• Help Desk
• COTS Install/Config.
• App Monitoring
• Outages
• Infrastructure Phys./VM
• Network Maintenance
CI QA Provision Deploy
Interrupt Driven
Project/Pipeline Driven
DEV/QA
1. DevOps = DevNo-Ops – The Case for AgileOps
DevOps = Agile Ops

19. Thank You!
e: scott.willson@automic.com
t: @rscottwillson
l: https://www.linkedin.com/in/swillson