19

DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

Embed Size (px)

Citation preview

Page 1: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps
Page 2: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

Top 10 Ways to Fail at DevOpsNovember 2016

Scott Willson – Mktg. Dir. – ARA / DevOps

Page 3: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

AGENDA DevOps DefinitionTop Ten List

Page 4: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

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.

Page 5: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

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.

Page 6: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

6 Property of Automic Software. All rights reserved

9. Failing To Include Management Buy-in

Page 7: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

7 Property of Automic Software. All rights reserved

8. Become Too Reliant on OSS

Page 8: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

8 Property of Automic Software. All rights reserved

7. Failing to Consider IT History

Page 9: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

9 Property of Automic Software. All rights reserved

7. Failing to Consider IT History

Page 10: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

10 Property of Automic Software. All rights reserved

7. Failing to Consider IT History

Page 11: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

11 Property of Automic Software. All rights reserved

7. Failing to Consider IT History

Page 12: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

12 Property of Automic Software. All rights reserved

7. Failing to Consider IT History

Page 13: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

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

Page 14: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

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/

Page 15: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

15 Property of Automic Software. All rights reserved

4. Centralize DevOps

Page 16: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

16 Property of Automic Software. All rights reserved

3. Think it is OK to Fail (in PROD)

Page 17: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

17 Property of Automic Software. All rights reserved

Use Same Automation Mechanics for Every EnvironmentDEV is Deployed to All the TimeQA - Less OftenPRE-PROD - Even Less OftenPROD - 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).

Page 18: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

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

Page 19: DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

Thank You!e: [email protected]: @rscottwillsonl: https://www.linkedin.com/in/swillson